I guess this gets into the point of whether "children" or whatever
field is used for child documents actually needs to be in the schema.
Schemaless mode creates one, but that's not a defining factor. Because
if it needs to be in the schema, then the code should reflect its
cardinality. But if it do
>
> Interestingly, I was forced to add children as an array even when the
> child was alone and the field was already marked multivalued. It seems
> the code does not do conversation to multi-value type, which means the
> query code has to be a lot more careful about checking field return
> type an
Thank you Nunedra,
That was very helpful. I am looking forward to that documentation Jira
to be merged into the next release.
I was able to get the example working by switching away from anonymous
children to the field approach. Which means hasChildren() call also
did not work. It seems the addCh
Hi Alex,
Currently, Fixing the documentation for nested docs is under progress. More
context is available in this JIRA -
https://issues.apache.org/jira/browse/SOLR-14383.
https://github.com/arafalov/SolrJTest/blob/master/src/com/solrstart/solrj/Main.java
The child doc transformer needs to be spe
Hello,
I am trying to get up to date with both SolrJ and Nested Document
implementation and not sure where I am failing with a basic test
(https://github.com/arafalov/SolrJTest/blob/master/src/com/solrstart/solrj/Main.java).
I am using Solr 8.6.1 with a core created with bin/solr create -c
solrj
