If you are referring to
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-id-field.html#mapping-id-field
It describes what I wrote.
The _id mapping can also be associated with a path that will be used to extract
the id from a different location in the source document. For example, having
the following mapping:
{
"tweet" : {
"_id" : {
"path" : "post_id"
}
}
}
Will cause 1 to be used as the id for:
{
"message" : "You know, for Search",
"post_id" : "1"
}
^^^^ This means that if you send the above document, elasticsearch will extract
the _id from the _source.post_id field.
Elasticsearch never modifies your _source document (unless you use scripts or
include/exclude features).
--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr
Le 18 juillet 2014 à 15:21:24, Giuseppe Longo ([email protected]) a écrit:
I'm not sure to understand you.
I've followed step by step the tutorial, it's strange that setting path to
`_id` do the opposite currently, or not?
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/4ead76cd-13e3-49e3-a217-852c3f865c9a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/etPan.53c92033.628c895d.38f%40MacBook-Air-de-David.local.
For more options, visit https://groups.google.com/d/optout.
