Thank you so much for the information Erick.
On Wed, Jun 1, 2016 at 9:47 PM, Erick Erickson <[email protected]> wrote: > You can tell very little about performance with 50 documents, > so I wouldn't trust these results at all. In particular I'm pretty > sure that your search speed will suffer _greatly_ as you get > more and more documents in your corpus if you use only > DocValues but don't have indexed="true" set. > > > Best, > Erick > > On Tue, May 31, 2016 at 10:51 PM, Chitra R <[email protected]> wrote: > > Hi, > > I have one doubt. Actually I have indexed 50 documents for both > > SortedNumericDocValuesField and IntField separately . Each document > > consists of 49 fields. After that, i performed indexing & searching ( > with > > & without sorting) . > > > > It seems DocValuesField indexes and searches the documents faster > than > > normal FieldType (eg: IntField) and also it retrieves the values more > > efficent than normal field. Is their any drawbacks to > > use SortedNumericDocValuesField over IntField? > > > > Also It seems like we can use Docvalues Field(String or Numeric) > > efficiently for any functionality(Searching and sorting). So generally, > do > > we have any drawbacks of using DocValues Field(String and Numeric)? > > > > > > Known Drawbacks(on StringFields): > > -->docvalues don't work on analyzed fields > > -->search_analyzer cannot be specified on non-analyzed fields. > > > > is there any specific drawback on numeric docvalue fields? is range query > > not possible?? or anyother? > > > > > > Thanks, > > Chitra > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
