Hi
Apologies for bringing this mail up again. But I have resolved some of the
issues that I originally started with including composite queries. However
I just have 1 remaining question which I would be grateful if someone could
assist me with.
I have a class whcih performs the creation of the s
I am also noticing the same behavior. Does anyone know any solutions?
AlexElba wrote:
>
> Hello,
> I was working with lucene snowball 2.3.2 and I switch to 2.4.0.
> After switch I came by to some case where lucene doesn't do lemmatization
> correctly. So far I found only one case spa - spas. sp
you can store binary value?
e.g. with:
Field(String name, byte[] value, Field.Store store)
You could store all your fields as byte[], so you get them back as byte[]. How
you index them is just another problem, but you are having no problems with
speed in your case, leave it as it is.
try simp
: dir is a local variable inside a method, so it's not getting reused.
: Should I synchronise the whole method? I think that would slow things down in
: a concurrent environment.
i don't really have any new advice beyond my previous comment...
: > if you have a fully exeuctable test case (instea
Hi,
It is not a good idea to extract each document. You can be more efficient
by only looking at the fields you are interested in. Depending on the size
of your index, you can try:
String[] codes = FieldCache.DEFAULT.getStrings(indexReader, fieldName);
This returns a string [] with the length
Hi, was recently looking to incorporate Lucene for a simple
"parametric"/"faceted" type search. The documents are very small,
roughly 15 fields of short length (5-15 characters, generally strings
and padded integers). When profiling query performance of our
application, which inserts 1 million doc
Bit late joining in but since this is the first Google hit for
"site:www.nabble.com joins lucene" thought it was reasonable place to add
this note:
In my application "joins" also start to seem appealing. Almost all my use
cases fit very nicely within what Lucene does apart from a "nice to have" a
LuSql 0.9 comes with Lucene 2.3.1 bundled in the jar (along with
commons-cli-1.1, commons-dbcp-1.2.2, commons-pool-1.4,
mysql-connector-java-5.0.7).
It can run with Lucene 2.4:
If you want to run using Lucene 2.4, put all the above jars in your
classpath, along with the 2.4 jar, run LuSql not usin
hi all,
Can somebody help me to figure out how can I use "jama svd package" to
apply LSA to the "term document vector" produced by lucene?
Yours Sincerely,
Nitin
This could be very useful. I see you include Lucene v2.3 in your
code...does it work correctly with indexes created on v2.4 as well?
- Greg
On Mon, Apr 13, 2009 at 6:49 PM, Glen Newton wrote:
> As the creator of LuSql
> [http://lab.cisti-icist.nrc-cnrc.gc.ca/cistilabswiki/index.php/LuSql]
> I
> On Unix, one can "kill -SIGQUIT" to get a thread stack trace dump for
> all threads; do you know how to do this on Windows? If so, can you do
> that at the end when IW starts doing this infinite merging? That
> would be very helpful towards understanding why this recursion is
> happening (thoug
Hmmm, very very odd.
First off, your "1 deleted docID" is because one document hit an
exception during indexing, likely in enumerating tokens from the
TokenStream; I see this line:
IW 0 [CrawlThread]: hit exception adding document
But I think that's fine (certainly should not cause what you ar
but the javadoc is not yet working locally (in the eclipse editor)
==
org.apache.lucene.store.RAMDirectory
Note: An exception occurred while getting the Javadoc. See log for details.
==
but it works on the browser (SHIFT +F2)
Thanks
Seid M.
Hello all,
I have a very peculiar problem that is driving me crazy: on some of our
datasets and at some point in time during indexing, the merge operation
runs into a (semi-)infinite loop and keeps adding files to the index
until it runs out of free disk space.
The situation: I have an index
thanks simon
seid M
On 4/14/09, Simon Willnauer wrote:
> Quite off-topic but anyway:
>
> 1. Right click on the JAR (must be in build path)
> 2. Click on Properties
> 3. Click on JavaDoc Location
> 4. Add the location
>
>
> simon
>
> On Tue, Apr 14, 2009 at 9:38 AM, Seid Mohammed wrote:
>> Sorr
Quite off-topic but anyway:
1. Right click on the JAR (must be in build path)
2. Click on Properties
3. Click on JavaDoc Location
4. Add the location
simon
On Tue, Apr 14, 2009 at 9:38 AM, Seid Mohammed wrote:
> Sorry for my little java knowledge and disturbing you.
> how can I attach the jav
Sorry for my little java knowledge and disturbing you.
how can I attach the java doc of lucene in my eclipse application.
it gives a message
=
org.apache.lucene.search.TopDocs
Note: This element neither has attached source nor attached Javadoc
and hence no Ja
17 matches
Mail list logo
