Re: Faceting : what are the limitations of Taxonomy (Separate index and hierarchical facets) and SortedSetDocValuesFacetField ( flat facets and no sidecar index) ?

Thank you so much, mike... Hope, gained a lot of stuff on Doc Values faceting and also clarified all my doubts. Thanks..!! *Another use case:* After getting matching documents for the given query, Is there any way to calculate mix and max values on NumericDocValuesField ( say date field)? I

Re: how do lucene read large index files?

Thanks Mike. We are planning to move MMapDirectory in both indexing and searching.Regarding ulimit change and read during merging, i just tried to know the impact of mmapdir during indexing. - Kumaran R On Nov 30, 2016 4:18 AM, "Michael McCandless" wrote: > >

Re: Query expansion

This is likely tricky to do correctly. E.g., MultiFieldQueryParser.getFieldQuery is invoked on whole chunks of text. If you search for: apple orange I suspect it won't do what you want, since the whole string "apple orange" is passed to getFieldQuery. How do you want to handle e.g. a phrase

Re: how do lucene read large index files?

It's OK to use NIOFSDirectory for indexing only in that nothing will break. But, MMapDirectory already uses normal IO for writing (java.io.FileOutputStream), and indexing does sometimes need to to read (for merging segments) though that's largely sequential reading so perhaps NIOFSDirectory won't

Re: Understanding Query Parser Behavior

Can you try escaping the / character to the query parser? E.g. pass this string instead: String value = "http\\:\\/\\/www.google.com"; Mike McCandless http://blog.mikemccandless.com On Tue, Nov 29, 2016 at 11:38 AM, Peru Redmi wrote: > Hello , > > It would be

Re: Faceting : what are the limitations of Taxonomy (Separate index and hierarchical facets) and SortedSetDocValuesFacetField ( flat facets and no sidecar index) ?

Doc values fields are never loaded into memory; at most some small index structures are. When you use those fields, the bytes (for just the one doc values field you are using) are pulled from disk, and the OS will cache them in memory if available. Mike McCandless http://blog.mikemccandless.com

Re: Understanding Query Parser Behavior

Hello , It would be great , if someone could help on this. *Note : I am using Lucene 4.10.4 version* On Mon, Nov 28, 2016 at 5:37 PM, Peru Redmi wrote: > Any help on this would be greatly appreciated. > > Thanks. > > On Thu, Nov 24, 2016 at 8:14 PM, Peru Redmi

Re: BlockJoin with RAM Directory

Use the specially proposed https://lucene.apache.org/core/6_0_1/core/org/apache/lucene/index/IndexWriter.html#addDocuments-java.lang.Iterable- which prevents flush from the cutting block in the middle. On Tue, Nov 29, 2016 at 12:27 PM, ASKozitsin wrote: > Hi everyone! > >

BlockJoin with RAM Directory

Hi everyone! I'm trying to fill RAMDirectory with documents according to BlockJoin structure: * child1_1 * child1_2 * child1_3 - parent1 * child2_1 * child2_2 - parent2 and so on. If I have small number of documents (less than 10.000) everything is okay. I can search among