> 14. mar. 2018 kl. 15:45 skrev Anshum Gupta :
>
> Hi Jan,
>
> The way I remember it was done (or at least we did it) is by storing the
> depth information as a field in the document using an update request
> processor and using a custom transformer to reconstruct the
I tried to index a 3-level nested Block and expected the "1.2.1" document to
have _root_=1.2 but it had the top-document as root. If each doc in addition
would have a _parent_= field pointing to its nearest parent, then it would
be possible to extend the [child] doc transformer to reconstruct
Hi Jan,
The way I remember it was done (or at least we did it) is by storing the
depth information as a field in the document using an update request
processor and using a custom transformer to reconstruct the original
multi-level document from it.
Also, this was a reasonably long time ago, so
I understand that the [subquery] transformer can help build a nested response
when you know the structure in advance, but what if you have some BlockJoin
indexed structure with grand children (as the original question in this
thread), and you want to reconstruct the full document based on what
Hi Alisa,
The issue here is still open so it seems highly unlikely that it would even
get to 6.0, which is around the corner. I think this would only be out with
6.1 at the earliest.
On Fri, Mar 25, 2016 at 11:12 AM, Alisa Z. wrote:
> Mikhail,
> Thank you for the answer.
>
Mikhail,
Thank you for the answer.
I'd be happy to contribute tons of test cases on nested structures and their
querying and faceting...
I am working on a case of moving very nested data structures to Solr (and the
other option is ES...) but so far Solr seems to be quite behind... It's
I think you cal already kick tires and contribute a test case into
https://issues.apache.org/jira/browse/SOLR-8208 that's already reachable
there I believe, but I still working on core design.
On Thu, Mar 24, 2016 at 10:02 PM, Alisa Z. wrote:
> Hi all,
>
> I apologize for
Hi all,
I apologize for duplicating my previous message:
Solr 5.3: anything similar to ChildDocTransformerFactory that does not
flatten the hierarchical structure?
However, it is still an open and interesting question:
Following the example from