Re: Indexing architecture

Hi, Any better architecture ideas for my below mentioned use case? Regards, Suriya On Wed, 28 Dec 2016 at 11:27 PM, suriya prakash wrote: > Hi, > > I have 100 thousand indexes in Hadoop grid because 90% of my indexes will > be inactive and I can distribute the other active inde

Indexing architecture

Hi, I have 100 thousand indexes in Hadoop grid because 90% of my indexes will be inactive and I can distribute the other active indexes based on load. Scoring will work better for each index but I don't worry about it now. What are the optimisations I need to do to Scale better? I do commit ever

All Fields Search

Hi, I have 500 fields in a document to index. I append all the values and index it as separate field to support all fields search. I will also have 500 separate fields for field level search. Is there any other better way for all fields search? Regards, Suriya

Re: Email id tokenizer (actual email id & multiple terms)

costly for content field. Is there any way to do it efficiently? will TeeSinkTokenFilter help for my case? On Tue, Dec 20, 2016 at 7:45 PM, suriya prakash wrote: > Hi, > > I am using standard analyzer and want to split token for email_id " > luc...@gmail.com" as "

Email id tokenizer (actual email id & multiple terms)

Hi, I am using standard analyzer and want to split token for email_id " luc...@gmail.com" as "lucene", "gmail","com","luc...@gmail.com" in a single pass. I have already changed jflex to split email id as separate words(lucene, gmail, com). But we need to do phrase search which will not be efficie

fieldsNotToLoad option in searcher api

Hi, I'm using Lucene 4.10.4 and I want fieldsNotToLoad option( like fieldsToLoad ) in searcher.doc api. Because I need not retrieve few fields from the index to improve io performance. I think we can achieve it by modifying Lucene40StoredFieldsReader, but is there any alternatives? Thanks, Sur