Hi,
I don't know if it's a feature or a bug but I spent a lot of time to understand what happens.
It's simple, when documents include a field "id", the console use this field as identifier in view line and not real document id.
In my usage I generate a specific ID for documents to get them quickly and "id" field in my document store other information.
So, as I said, I don't know if it's a bug or a feature, but I lost time to find solution and it's when I used directly API that I saw that ID was ok after my imports.
Expected Behavior
See view line of documents with good document _id
Current Behavior
We saw field "id" in document and not reald document _id
Possible Solution
To "fix" this I rename field id and reimport documents
When we did it we thought "It's OK, noone will ever add an id field within the body of the document, there's already the _id provided by Elasticsearch."
Lesson learned.
Context
Hi, I don't know if it's a feature or a bug but I spent a lot of time to understand what happens.
It's simple, when documents include a field "id", the console use this field as identifier in view line and not real document id. In my usage I generate a specific ID for documents to get them quickly and "id" field in my document store other information.
So, as I said, I don't know if it's a bug or a feature, but I lost time to find solution and it's when I used directly API that I saw that ID was ok after my imports.
Expected Behavior
See view line of documents with good document _id
Current Behavior
We saw field "id" in document and not reald document _id
Possible Solution
To "fix" this I rename field id and reimport documents
Steps to Reproduce
Context (Environment)
Kuzzle version: 2.6.0 Node.js version: v12.13.1 Admin Console Version: 4-dev (http://next-console.kuzzle.io/)