Searching in multiple indexes with more than 2147483519 documents

Hi all, A Lucene index can't contain more than 2147483519 documents, so we want to split a larger dataset in multiple indexes. However, it is not possible to create a MultiReader to search in all the index partitions at a time: Too many documents: composite IndexReaders cannot exceed 2147483519 b

Re: LUCENE-6766 index sorting and custom SortField

uld then > make its own SegmentInfoFormat that knew how to serialize the custom sort > field you had set on IndexWriterConfig. > > Mike McCandless > > http://blog.mikemccandless.com > > On Tue, Aug 16, 2016 at 2:51 PM, Andres de la Peña > wrote: > >> Do you mean

Re: LUCENE-6766 index sorting and custom SortField

ature, don't you think so? >> > > >> > > Thanks, >> > > >> > > 2016-08-14 23:09 GMT+01:00 Michael McCandless < >> luc...@mikemccandless.com >> > >: >> > > >> > >> Unfortunately, as of LUCE

Re: LUCENE-6766 index sorting and custom SortField

compute your sort criteria and index it as a doc values field and > then sort by that? > > Or, patches welcome too ;) > > Mike McCandless > > http://blog.mikemccandless.com > > On Sun, Aug 14, 2016 at 7:19 AM, Andres de la Peña > wrote: > >> Hi, >> >

LUCENE-6766 index sorting and custom SortField

Hi, LUCENE-6766 allows to define index sorting on IndexWriterConfig instead of defining a SortingMergePolicy. However, the new index sorting only supports some types of sort fields, and the old SortingMergePolicy, which didn't have this limitation, has been removed. What should do projects depend

Re: Filter strategy in Lucene 6.0

t; > Both approximations and confirmations have an API that allows them to > expose a "cost" and the least costly components are always evaluated before > the most costly ones. So the filter strategy is not useful anymore, every > decision is made based on these cost APIs. >

Filter strategy in Lucene 6.0

Hi all, Suppose that we have a boolean query composed by two filtering queries, where one of them is fast and the other is slow: BooleanQuery.Builder builder = new BooleanQuery.Builder(); builder.add(fastQuery, FILTER); builder.add(slowQuery, FILTER); Query query = builder.build(); How is the i

Re: Storing numeric fields in Apache 6

If I'm right, you should use a StoredField to save the value, you can give it the same name as the used for the DoublePoint field. El jueves, 28 de abril de 2016, j.Pardos escribió: > Hello all, > > I need to index some numeric fields, search with numeric range queries, > and store the data to r

Re: Evaluate if a document satisfies a query

stic.co/guide/en/elasticsearch/reference/current/search-percolate.html > > > http://lucene.apache.org/core/6_0_0/memory/index.html?org/apache/lucene/index/memory/MemoryIndex.html > Ahmet > > > > > On Monday, April 25, 2016 5:04 PM, Andres de la Peña < > adelap...@st

Evaluate if a document satisfies a query

Hi all, Is it possible to evaluate if a document satisfies a query? Of course it can be done indexing the document in a RAMIndex and querying it, but I wonder if it is possible to do it in a more efficient way. Thanks, -- Andrés de la Peña Vía de las dos Castillas, 33, Ática 4, 3ª Planta 28224

Re: Cannot comment on Jira issues

Yes, it works now. Thanks a lot for the quick help! 2016-04-23 15:48 GMT+01:00 Robert Muir : > OK should really work now! > > On Sat, Apr 23, 2016 at 10:37 AM, Andres de la Peña > wrote: > > I'm still not able to comment, although I have tried to logout and login > &

Re: Cannot comment on Jira issues

I'm still not able to comment, although I have tried to logout and login again. 2016-04-23 15:31 GMT+01:00 Robert Muir : > Can you try now? I added you to contributors groups. > > On Sat, Apr 23, 2016 at 10:26 AM, Andres de la Peña > wrote: > > Hi, > > > > I w

Re: Cannot comment on Jira issues

Hi, I would like to reply to the answer to my comment on LUCENE-7086 . Could I be temporary added to a group with more permissions? My username is adelapena. Thanks in advance, 2016-04-22 14:21 GMT+01:00 Steve Rowe : > Mạnh, > > I’ve added you

Paging with EarlyTerminatingSortingCollector

Hi all, Is it possible to page over results when using an EarlyTerminatingSortingCollector? I'm using the following code with Lucene 5.5.0 to read results in pages of 10 documents each: /** The Lucene field name */ private static final String FIELD_NAME = "id"; /** The Lucene field type */ priv