Hi Tom, Thanks for your suggestion and the information.
I will try this out to test and will share the results. On Sep 14, 2017 2:32 PM, "Sreenivas.T" <sree...@gmail.com> wrote: > I agree with Tom. Doc values and stored fields are present for different > reasons. Doc values is another index that gets build for faster > sorting/faceting. > > On Wed, Sep 13, 2017 at 11:30 PM Tom Evans <tevans...@googlemail.com> > wrote: > > > On Tue, Sep 12, 2017 at 4:06 AM, Aman Tandon <amantandon...@gmail.com> > > wrote: > > > Hi, > > > > > > We want to know about the indexing performance in the below mentioned > > > scenarios, consider the total number of 10 string fields and total > number > > > of documents are 10 million. > > > > > > 1) indexed=true, stored=true > > > 2) indexed=true, docValues=true > > > > > > Which one should we prefer in terms of indexing performance, please > share > > > your experience. > > > > > > With regards, > > > Aman Tandon > > > > Your question doesn't make much sense. You turn on stored when you > > need to retrieve the original contents of the fields after searching, > > and you use docvalues to speed up faceting, sorting and grouping. > > Using docvalues to retrieve values during search is more expensive > > than simply using stored values, so if your primary aim is retrieving > > stored values, use stored=true. > > > > Secondly, the only way to answer performance questions for your schema > > and data is to try it out. Generate 10 million docs, store them in a > > doc (eg as CSV), and then use the post tool to try different schema > > and query options. > > > > Cheers > > > > Tom > > >
