On Sun, 2012-03-04 at 23:01 -0800, Mark Waddle wrote:
I agree, all of those changes are great. I am especially excited about
the potential for grouping!
@Clinton: I am not sure how the sorting on a nested document field
would work. If you have multiple nested documents, then it could hit
on multiple nested documents, and then it would not be clear as to
which to sort on. If there is only one nested document per root
document, then you could have a copy of the sort field on the root
You could choose to sort on the best matching nested doc, for instance.
On Sunday, March 4, 2012 12:15:30 AM UTC-8, Clinton Gormley wrote:
> - Better shard allocation, initially trying to even out
> allocation also based on which index they belong to, to get
> distribution also within an index across a cluster.
> - Refactor the field data support, allowing for different
> implementations, which can allow for ones that are more
> memory usage for example. It will tie in with the mapping
> decide which one to use on which field, though the aim is to
> sensible auto detected defaults.
> - Refactor the search execution code, to allow for more
> search executions, like one that does grouping. Once its
done, try and
> see if we can tackle grouping.
All the above sound excellent.
I think you probably have this planned for another version,
feature I'd love to see is: more visibility of nested docs.
- which of my 10 nested Comments caused this Blog to match my
- with highlighting per nested doc
- sorting by a field in a matching nested doc