>>You could add a "level2_comment_id" field to the level 2 commends and
>>it's children, and then use unique() on that.
OK, I see, I missed the children... Thank you for pointing out.
I have introduced that "unique sub-branch identifying" field and propagated it
down the subbranch (the data is
On Fri, Apr 22, 2016 at 12:26 PM, Alisa Z. wrote:
> Hi Yonik,
>
> Thanks a lot for your response.
>
> I have discussed this with Mikhail Khludnev already and tried this
> suggestion. Here's what I've got:
>
>
>
> sentiment: positive
> author: Bob
> text: Great post about Solr
> 2.blog-posts.comm
Hi Yonik,
Thanks a lot for your response.
I have discussed this with Mikhail Khludnev already and tried this suggestion.
Here's what I've got:
sentiment: positive
author: Bob
text: Great post about Solr
2.blog-posts.comments-id: 10735-23004 //this is a new
fie
Hi Alisa,
This was a bit too hard for me to grok on a first pass... then I saw
your related blog post which includes the actual sample data and makes
it more clear.
More comments inline:
On Wed, Apr 20, 2016 at 2:29 PM, Alisa Z. wrote:
> Hi all,
>
> I have been stretching some SOLR's capabilit
Hi all,
I have been stretching some SOLR's capabilities for nested documents handling
and I've come up with the following issue...
Let's say I have the following structure:
{
"blog-posts":{ //level 1
"leaf-fields":[
"date",
"author"],
"title":{
Hi Yonik,
Well, no one replied to this yet, so I thought I'd chime in with some of
the use cases that I am working with. Please note that I am lagging a big
behind the last few releases, so I haven't had time to experiment with Solr
5.3+, I am sure that some of this is included in there already an
Hey folks, we're at the point of figuring out the API for block join
child rollups for the JSON Facet API.
We already have simple block join faceting:
http://yonik.com/solr-nested-objects/
So now we need an API to carry over more information from children to
parents (say rolling up average rating o
