We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If you index a document like this:
POST /test/test { "foo": "bar", "_id": 2 }
it will throw an exception saying:
Provided id [upGeHLkQQv-aclC7mF6EWQ] does not match the content one [2]
In other words, it is using a path for the _id field, even though we haven't specified one, and there is no way to disable this.
path
_id
I think that we should only do this check if the path parameter on the _id mapping is explicitly set.
The text was updated successfully, but these errors were encountered:
Related, in 1.1.1.
If you index a document like:
POST test/test { "_id": { "$oid": "5303daa1c36b445138605a0c" }, "event_id": { "$oid": "537c2a0ebb20c7336f5e4aca" }, "start_date": "2014-05-24T20:00:00-04:00", "country": "Canada" }
The auto-generated mapping will be:
{ "test": { "mappings": { "test": { "properties": { "$oid": { "type": "string" } } } } } }
It will normalize the _id field and will ignore the other fields.
Sorry, something went wrong.
Closing in favour of #6730 and #9059
No branches or pull requests
If you index a document like this:
it will throw an exception saying:
In other words, it is using a
path
for the_id
field, even though we haven't specified one, and there is no way to disable this.I think that we should only do this check if the
path
parameter on the_id
mapping is explicitly set.The text was updated successfully, but these errors were encountered: