Nested Documents: ToChildBlockJoinQuery, TopGroups


(Lukáš Vlček) #1

Hi,

would it be possible to expose query on top of ToChildBlockJoinQuery?
Also the TopGroups from ToParentBlockJoinQueryCollector sounds very
interesting and I am sure this would be nice addition.

It would probably require change in response format, is there any other
reason why it would be not good idea to expose it? (Performance?)

Regards,
Lukas

--


(Martijn Van Groningen) #2

would it be possible to expose query on top of ToChildBlockJoinQuery?
At the moment the nested query is using the BlockJoinQuery (a 95% copy
of the ToChildBlockJoinQuery)

Also the TopGroups from ToParentBlockJoinQueryCollector sounds very
interesting and I am sure this would be nice addition.
Agree, this would be a very nice addition.

It would probably require change in response format, is there any other
reason why it would be not good idea to expose it? (Performance?)
I don't see any performance reasons why something like this couldn't
be added. Block joins are cheap. Representing this in the api and the
response needs some careful thinking. I think it is similar to result
grouping.

--


(Lukáš Vlček) #3

Ah, I see. I thought it was using directly what is in Lucene 3.1.6 now.
Out of curiosity, what is the reason Lucene classes can not be used
directly?

Lukas

On Mon, Sep 10, 2012 at 3:01 PM, Martijn v Groningen <
martijn.v.groningen@gmail.com> wrote:

would it be possible to expose query on top of ToChildBlockJoinQuery?
At the moment the nested query is using the BlockJoinQuery (a 95% copy
of the ToChildBlockJoinQuery)

Also the TopGroups from ToParentBlockJoinQueryCollector sounds very
interesting and I am sure this would be nice addition.
Agree, this would be a very nice addition.

It would probably require change in response format, is there any other
reason why it would be not good idea to expose it? (Performance?)
I don't see any performance reasons why something like this couldn't
be added. Block joins are cheap. Representing this in the api and the
response needs some careful thinking. I think it is similar to result
grouping.

--

--


(Martijn Van Groningen) #4

Out of curiosity, what is the reason Lucene classes can not be used
directly?
The BlockJoinQuery has been modified to support facets in the nested
queries scope.

Martijn

--


(Lukáš Vlček) #5

Ah! Good to know.

The reason why I am asking is primarily because when explaining Nested
Documents to users one could point them to Lucene documentation which is
very useful. So in this case it is good to know what is the difference.

Thanks,
Lukas

On Thu, Sep 13, 2012 at 2:33 PM, Martijn v Groningen <
martijn.v.groningen@gmail.com> wrote:

Out of curiosity, what is the reason Lucene classes can not be used
directly?
The BlockJoinQuery has been modified to support facets in the nested
queries scope.

Martijn

--

--


(system) #6