See also http://wiki.apache.org/lucene-java/ImproveIndexingSpeed
Also double check that it's Lucene that you should be concentrating
on. In my experience it's often the reading of the data from a
database, if that's what you are doing, that is the bottleneck.
--
Ian.
On Wed, Sep 9, 2015 at
The link that I sent,
http://wiki.apache.org/lucene-java/ImproveIndexingSpeed is for Lucene,
not Solr. The second item on the list is to make sure you are using
the latest version of lucene so that would be a good starting point.
--
Ian.
On Wed, Sep 9, 2015 at 3:10 PM, Humberto Rocha
Thanks a lot !
But do you know some links that helps implement these optimization options
without the Solr (using only lucene) ?
I am using lucene 4.9.
More thanks.
Humberto
On Wed, Sep 9, 2015 at 5:23 AM, Ian Lea wrote:
> See also
Great! I will upgrade Lucene then.
I'm not using database.
Are there some java samples code ?
Samples with:
1. indexing documents in batches.
2. Multi-threaded indexing
Thanks a lot.
On Wed, Sep 9, 2015 at 11:23 AM, Ian Lea wrote:
> The link that I sent,
>
Hi Uwe,
Can you please share some details about that design decision "Whenever
Lucene updates something in the index, it creates a new file". Is it right
understanding that while IndexOutput is open, Lucene continues to use the
same output/file. But after it closed (for instance application was
I think its a bug: https://issues.apache.org/jira/browse/LUCENE-6792
On Tue, Sep 8, 2015 at 10:35 AM, Ruslan Muzhikov wrote:
> Hi!
> Sometimes TermsQuery.toString() method falls with exception:
>
> *Exception in thread "main" java.lang.AssertionError*
> * at
> Great! I will upgrade Lucene then.
Good start.
> I'm not using database.
Fine, but you must be getting your data from somewhere. Maybe that is
blazingly fast, maybe it isn't.
> Are there some java samples code ?
>
> Samples with:
>
> 1. indexing documents in batches.
I think this means