Re: Which Lucene 8.5.X is recommended?

2020-11-12 Thread baris . kazar
Thanks, i will use 8.5.2. i think saw some minor release switch on (z) without any issues but i will double check this. However, i will use 8.5.2 since the bug fixes in that release may result in better performance for Lucene index. Best regards > On Nov 12, 2020, at 11:09 PM, Erick Erickson

Re: Which Lucene 8.5.X is recommended?

2020-11-12 Thread baris . kazar
Thanks, i will use 8.5.2. i think saw some minor release (z) without any issues but i will double check this. However, i will use 8.5.2. The bug fixes in that release may result in better performance. Best regards > On Nov 12, 2020, at 11:09 PM, Erick Erickson wrote: > Always use the most r

Re: https://issues.apache.org/jira/browse/LUCENE-8448

2020-11-12 Thread baris . kazar
Hi,- Thanks. These are final finished sizes in both cases. Best regards > On Nov 12, 2020, at 11:12 PM, Erick Erickson wrote: > > Yes, that issue is fixed. The “Resolution” tag is the key, it’s marked > “fixed” and the version is 8.0 > > As for your other question, index size is a very impre

Re: https://issues.apache.org/jira/browse/LUCENE-8448

2020-11-12 Thread Erick Erickson
Yes, that issue is fixed. The “Resolution” tag is the key, it’s marked “fixed” and the version is 8.0 As for your other question, index size is a very imprecise number. How many deleted documents are there in each case? Deleted documents take up disk space until the segments containing them are

Re: Which Lucene 8.5.X is recommended?

2020-11-12 Thread Erick Erickson
Always use the most recent point release. The only time we go from x.y.z to x.y.z+1 is if there are _significant_ problems. This is much different than going from x.y to x.y+1... > On Nov 12, 2020, at 5:49 PM, baris.ka...@oracle.com wrote: > > Hi,- > > is it best to use 8.5.2? > > Best regar

Which Lucene 8.5.X is recommended?

2020-11-12 Thread baris . kazar
Hi,-  is it best to use 8.5.2? Best regards Release 8.5.2 Bug Fixes   (1) LUCENE-9350: Partial reversion of LUCENE-9068; holding levenshtein automata on FuzzyQuery can end up blowing up query caches which use query objects as cache keys, so building the automata is now delayed to search ti

Re: https://issues.apache.org/jira/browse/LUCENE-8448

2020-11-12 Thread baris . kazar
On a related issue: i experience that with Version 7.7.2 i experienced this: data is all lower case (same amount of docs as next case though) vs data is camel case except last word always in capital letters but i used in indexer the lowercase filter in both cases so indexing is done with al

https://issues.apache.org/jira/browse/LUCENE-8448

2020-11-12 Thread baris . kazar
https://issues.apache.org/jira/browse/LUCENE-8448 Hi,-  is this issue fixed please? Could You please help me figure it out? Best regards - To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional comma