On Sat, Oct 27, 2012 at 1:53 PM, Tom wrote:
> Hello,
>
> using Lucene 4.0.0b, I am trying to get a superset of all stop words (for
> an international app).
> I have looked around, and not found anything specific. Is this the way to go?
>
> CharArraySet internationalSet = new CharArraySet(Version.L
How about DirectoryReader.html#openIfChanged?
See:
http://lucene.apache.org/core/4_0_0/core/org/apache/lucene/index/DirectoryReader.html#openIfChanged(org.apache.lucene.index.DirectoryReader)
-- Jack Krupansky
-Original Message-
From: Scott Smith
Sent: Friday, October 26, 2012 7:54 PM
How do I determine if the index has been modified in 4.0? The ifchanged() and
isChanged() appear to have been removed.
Lucene document IDs are not stable. You could add a field with an ID that
you maintain. Your query would then be just a TermQuery on the ID.
Regards,
Mossaab
2012/10/26 Scott Smith
> I'm currently converting some lucene code to 4.0. It appears that you are
> no longer allowed to delete a docu
I'm currently converting some lucene code to 4.0. It appears that you are no
longer allowed to delete a document by its ID. Is that correct? Is my only
option to figure some kind of query (which obviously isn't based on ID) and do
the delete from there?
We recently switched from QueryParser to ComplexPhraseQueryParser
(from lucene-queryparser-3.6.0.jar), and we've come across two
separate problems.
The first is that because it parses quoted expressions twice, it is
necessary to double-escape any escaped characters. So if I do not want
to allow us
Hi Vitaly,
Your hunch is correct, yes there are unmerged segments leftover. However to get
indexing throughput, we use multiple threads on the writer flushing to disk
periodically, but the writer can stay open for some time (until the last thread
terminates). However, after an optimize, the ind
One thing to keep in mind is that the default merge policy has changed in
3.6 from 2.3.2 (I'm almost certain of that). So it's just a hunch but you
may have some unmerged segments left over at the end. Try calling
IndexWriter.close(true) after you're done indexing.
On Fri, Oct 26, 2012 at 10:50 AM
Hello.
We have an index that when creted using lucene2.3.2, has a size of about 4G.
Creating the same index (with the same parameters) with lucene 3.6.0 results in
an 11G index.
Could someone shed some light into why the index is so much larger, given the
same data and the same parameters?
I
Thanks Robert
On 26.10.2012 г. 18:49, Robert Muir wrote:
On Fri, Oct 26, 2012 at 11:47 AM, Ivan Vasilev wrote:
if you want to not use jars, then its not enough to add the
/src/java directories. you also need /src/resources
directories in the classpath
-
On Fri, Oct 26, 2012 at 11:47 AM, Ivan Vasilev wrote:
if you want to not use jars, then its not enough to add the
/src/java directories. you also need /src/resources
directories in the classpath
-
To unsubscribe, e-mail: java-us
Hi Guys,
When executing:
ndexWriterConfig iwc = new IndexWriterConfig(Version.LUCENE_40, new
MyAnalyzer());
I have the following exception:
Exception in thread "main" java.lang.ExceptionInInitializerError
at
org.apache.lucene.index.LiveIndexWriterConfig.(LiveIndexWriterConfig.java:118)
Hello Jack,
you are right, there is no reason that this possibility is only in Solr, what
could use it from the Lucene-API.
I just got the old source code from Jan, the author of the old post.
When our current change is release I will have a look to the Solr solution and
I will try to bring this
hi ian
yes, i read this.
i only wonder, if there are maybe new thoughts or possibilities available since
January 2008 ;-)
thank you for your email : )
cheers
willi
Von: Ian Lea
An: java-user@lucene.apache.org; Willi Haase
Gesendet: 14:50 Donnerstag, 25.
14 matches
Mail list logo
