I was just adding through pysolr. I'm not sure which path that uses sorry.
From: users@solr.apache.org At: 10/17/24 16:52:01 UTC-4:00To:
users@solr.apache.org
Subject: Re: Solr9 Nested Document Unknown Field
9.5 is fresh enough. Which update path you send request to?
On Thu, Oct 17, 2024 at 9:21 PM Joseph Goodman (BLOOMBERG/ 919 3RD A) <
jgoodman...@bloomberg.net> wrote:
> We are currently using 9.5 and it would be hard to switch to a more recent
> version than that
>
> From: users@solr.apache.org At: 10/17/24 11:36:31 UTC-4:00To:
> users@solr.apache.org
> Subject: Re: Solr9 Nested Document Unknown Field
>
> Hello
> It's not clear which of 9th you use. Can you try with the recent one ie 9.7
> ?
>
> On Thu, Oct 17, 2024 at 12:32 AM Joseph Goodman (BLOOMBERG/ 919 3RD A) <
> jgoodman...@bloomberg.net> wrote:
>
> > Hi,
> >
> > I am trying to work with nested documents on solr9, but when I use the
> > ChildDocTransformerFactory (fl=*, [child]), none of the child documents
> > come through the result. Our nested documents use the anonymous
> > _childDocuments_ key and the schema includes the _nest_path_ field which
> is
> > likely the issue.
> >
> > When I try and ingest nested documents without the anonymous key like
> > [
> > {
> > "id": "doc_1",
> > "title_s": "A test document",
> > "parent_s": "true"
> > },
> > {
> > "id": "doc_2",
> > "parent_s": "true",
> > "title_s": "The Banana: Tasty or Dangerous?",
> > "children" : [
> > { "id": "child_doc_1", "title_s": "peel",
> > "parent_s": "False" },
> > { "id": "child_doc_2", "title_s": "seed", "parent_s": "False"
> > },
> > ]
> > },
> > ]
> >
> > I get the error response pysolr[407]: Solr responded with an error (HTTP
> > 400): [Reason: ERROR: [doc=doc_2] unknown field 'children']
> >
> > When, I remove the `_nest_path_` field from the solr schema and use the
> > anonymous `_childDocuments_` this works but that is not the recommended
> > solution.
> >
> > Any help would be greatly appreciated!
> >
> >
> >
>
> --
> Sincerely yours
> Mikhail Khludnev
>
>
>
--
Sincerely yours
Mikhail Khludnev
