Hi, sorry for thee delay in replying.
After some more digging, I noticed the following in the schema (which I
didn't originally created and which works without apparent issues in Solr
7.5):
I think that was intended as a catchall field for fields in the input data
not found in the schema.
Rem
No no. The schema still has ONE a uniqueId field.
The _root_ field is used as a parent pointer for child documents, it will hold
the ID of the parent.
Thus you should not need _root_ if you don't use parent/child. But this thread
suggests that _root_ may be needed in some other code paths as well
So it was a decision to remove the unique field id and replace it with root?
This seems, bad. You can’t have two documents with the same id/unique field.
> On Dec 9, 2022, at 7:57 AM, Jan Høydahl wrote:
>
> Hi,
>
> So to be clear - you have a working fix by adding the _root_ field to your
Hi,
So to be clear - you have a working fix by adding the _root_ field to your
schema?
I suppose most 8.x users already have a _root_ field, so the thing you are
seeing could very well be some bug related to atomic update.
Can I propose that you create a minimal reproduction of this issue and
The default managed_schema in solr 8.11 says:
On Thu, Dec 8, 2022 at 2:40 PM David Hastings
wrote:
> Interesting, this is kind of bizarre behavior.
> is:
>
> defaulted in the schema for 8.x?
>
> On Thu, Dec 8, 2022 at 9:31 AM Eduardo Gomez
> wrote:
>
> > > At first
Interesting, this is kind of bizarre behavior.
is:
defaulted in the schema for 8.x?
On Thu, Dec 8, 2022 at 9:31 AM Eduardo Gomez
wrote:
> > At first it wasn't clear to me what the problem you're having actually
> > is. Then I glanced back at the message subject ... it is the only place
> > you
> At first it wasn't clear to me what the problem you're having actually
> is. Then I glanced back at the message subject ... it is the only place
> you mention it.
Sorry Shawn, you are right, I didn't explain very clearly. So basically, in
Solr 8.11.1, I can see that updating an existing docume
Right, Shawn. That's how it works
https://lucene.apache.org/core/7_4_0/core/org/apache/lucene/index/IndexWriter.html#updateDocuments-org.apache.lucene.index.Term-java.lang.Iterable-
And it's really fast in query time.
On Thu, Dec 8, 2022 at 4:06 PM Shawn Heisey wrote:
> On 12/8/22 05:58, Shawn H
On 12/8/22 05:58, Shawn Heisey wrote:
So you can't just update a child document, you have to update all the
children and all the parents at the same time, so the new documents
are all in the same segment.
That's a little unclear and sounds like a draconian requirement. :) I
meant that all ch
On 12/8/22 02:43, Eduardo Gomez wrote:
I have seen there have been some changes introduced to how child docs are
updated (
https://solr.apache.org/guide/8_0/major-changes-in-solr-8.html#nested-documents).
From the docs:
*" ... an attempt to update a child document by providing a new document
wi
10 matches
Mail list logo
