Hi, If I go with copy field than will it increase I/O load considering I have RAM less than one third of total index size?
Thanks Abhishek Original Message From: Erick Erickson Sent: Monday, 10 March 2014 01:37 To: solr-user@lucene.apache.org Reply To: solr-user@lucene.apache.org Subject: Re: Optimizing RAM I'd go for a copyField, keep the stemmed and unstemmed version in the same index. An alternative (and I think there's a JIRA for this if not an outright patch) is implement a "special" filter that, say, puts the original tken in with a special character, say $ at the end, i.e. if indexing "running", you'd index both "running$" and "run". Then when you want exact match, you search for "running$". Best, Erick On Sun, Mar 9, 2014 at 2:55 PM, abhishek jain <abhishek.netj...@gmail.com> wrote: > hi friends, > I want to index some good amount of data, i want to keep both stemmed and > unstemmed versions , > I am confused should i keep two separate indexes or keep one index with two > versions or column , i mean col1_stemmed and col2_unstemmed. > > I have multicore with multi shard configuration. > My server have 32 GB RAM and stemmed index size (without content) i > calculated as 60 GB . > I want to not put too much load and I/O load on a decent server with some 5 > other replicated servers and want to use servers for other purposes also. > > > Also is it advised to server queries from master server or only from slaves? > -- > Thanks, > Abhishek
