News for hackers. Stuff that matters.
Re:Lucene: The Good Parts by ddorian43 on Friday June 05, 2015 @04:13PM (#9667824)
I still don't understand why lucene can't use the original document for aggregations ? I undestand that it will be slower if the field isn't indexed, but it should be doable like rdbms do.
Re:Lucene: The Good Parts by boomzilla on Friday June 05, 2015 @04:41PM (#9668005)
It can, as long as you store all the fields that will be needed for aggregation. Stored, non-indexed field retrieval can be slow as it might involve a lot of random seeks, so it might be slower than relation dbs.

What use case do you have in mind?

Re:Lucene: The Good Parts by ddorian43 on Friday June 05, 2015 @04:54PM (#9668102)
I mean in the case of _source field that elasticsearc uses. But seems that is separate. My usecase is I want to do querying+filtering on all fields of the document. In this case you have to:

1.store the field or document so you can get back the value (ex: when querying the document)

2.index the field for filtering

3.separately index the field for aggregation(doc_values)

While in rdbms you only need(1).