You need to specify the id of the document you want to update somehow. Since in es-hadoop things are batch focused, each
doc needs its own id specified somehow hence the use of 'es.mapping.id' to indicate its value.
Is there a reason why this approach does not work for you - any alternatives
that you thought of?
Cheers,
On 7/7/14 10:48 PM, Brian Thomas wrote:
I am trying to update an elasticsearch index using elasticsearch-hadoop. I am
aware of the *es.mapping.id*
configuration where you can specify that field in the document to use as an id,
but in my case the source document does
not have the id (I used elasticsearch's autogenerated id when indexing the
document). Is it possible to specify the id
to update without having the add a new field to the MapWritable object?
--
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
elasticsearch+unsubscr...@googlegroups.com
<mailto:elasticsearch+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/ce6161ad-d442-4ffb-9162-114cb8cd76dd%40googlegroups.com
<https://groups.google.com/d/msgid/elasticsearch/ce6161ad-d442-4ffb-9162-114cb8cd76dd%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
Costin
--
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 elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/53BF0A45.7000403%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
