On Fri, Nov 11, 2016 at 5:21 AM, Chitra R wrote:
> i)Hope, when opening SortedSetDocValuesReaderState , we are
> calculating ordinals( this will be used to calculate facet count ) for doc
> values field and this only made the state instance somewhat costly.
> Am I ri
Hi,
Match all docs query minus Promotion.endDate:[* TO *]
+*:* -Promotion.endDate:[* TO *]
Ahmet
On Friday, November 11, 2016 5:59 PM, voidmind wrote:
Hi,
I have indexed content about Promotions with effectiveDate and endDate
fields for when the promotions start and end.
I want to query for
Hi Alexey,
The behavior you mention is an intentional change from the behavior in Lucene
4.9.0 and earlier, when tokens longer than maxTokenLenth were silently ignored:
see LUCENE-5897[1] and LUCENE-5400[2].
The new behavior is as follows: Token matching rules are no longer allowed to
match ag
Hi,
I have indexed content about Promotions with effectiveDate and endDate
fields for when the promotions start and end.
I want to query for expired promotions so I do have this criteria, which
works fine:
+Promotion.endDate:[210100TOvariable containing yesterday's date]
The issue I hav
Hello,
I'm using lucene 6.2.0 and expecting the following test to pass:
import org.apache.lucene.analysis.BaseTokenStreamTestCase;
import org.apache.lucene.analysis.standard.StandardTokenizer;
import java.io.IOException;
import java.io.StringReader;
public class TestStandardTokenizer extends Ba
Hi lukes,
First, IW never "auto commits". The maxBufferedDocs/RAMBufferSizeMB
settings control when IW moves the recently indexed documents from RAM
to disk, but that moving, which writes new segments files, does not
commit them. It just writes them to disk, not visible yet to an
external reader
Hi Shai,
i)Hope, when opening SortedSetDocValuesReaderState , we are
calculating ordinals( this will be used to calculate facet count ) for doc
values field and this only made the state instance somewhat costly.
Am I right or any other reason behind that?
