Multiple core type mappings for the same field in elasticsearch (e.g. string and object)

Is it possible to create multiple core type mappings for a single
field e.g. a field 'qty' which allows both long/string values or a
field 'action' which allows both object/string values?

I'm using the mongodb river and once the field is indexed as an
object, it throws a MapperParsingException tried to parse as object,
but got EOF, has a concrete value been provided to it?]","status":400
for all other data that contain this field as a string. As a result
all the documents that I've stored in mongodb aren't searchable
through my search interface which searches elasticsearch

I read here https://github.com/elasticsearch/elasticsearch/issues/1166
that this is not possible? Also, here
https://groups.google.com/group/elasticsearch/browse_thread/thread/eac7b8c74516f75b/71cada0c2215275a?lnk=gst&q=multiple+core+type+mappings#71cada0c2215275a.
I'm using v 0.19.8.

I've also tried setting ignore_conflicts : true in my mapping as per
the example shown http://grokbase.com/t/gg/elasticsearch/128ath8kh1/some-mapping-confusions-to-resolve,
but the data I was looking for was not pulled into elasticsearch from
mongodb.

How can I map this so that I can see all documents (both ones with
action field as an object and ones with action as a string (each
document can have multiple action fields)) in elasticsearch? Thanks!

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Hey,

The 'ignore_conflicts' parameter is only applied when you put a new mapping.
Maybe the 'ignore_malformed' parameter helps you a bit more, see

This really means that field is ignored. So the document gets indexed, but
is not searchable at that field. Keep that in mind.

--Alex

On Wed, May 29, 2013 at 6:35 AM, coys gautam719@gmail.com wrote:

Is it possible to create multiple core type mappings for a single
field e.g. a field 'qty' which allows both long/string values or a
field 'action' which allows both object/string values?

I'm using the mongodb river and once the field is indexed as an
object, it throws a MapperParsingException tried to parse as object,
but got EOF, has a concrete value been provided to it?]","status":400
for all other data that contain this field as a string. As a result
all the documents that I've stored in mongodb aren't searchable
through my search interface which searches elasticsearch

I read here Document what mapping updates are allowed · Issue #1166 · elastic/elasticsearch · GitHub
that this is not possible? Also, here

https://groups.google.com/group/elasticsearch/browse_thread/thread/eac7b8c74516f75b/71cada0c2215275a?lnk=gst&q=multiple+core+type+mappings#71cada0c2215275a
.
I'm using v 0.19.8.

I've also tried setting ignore_conflicts : true in my mapping as per
the example shown
http://grokbase.com/t/gg/elasticsearch/128ath8kh1/some-mapping-confusions-to-resolve
,
but the data I was looking for was not pulled into elasticsearch from
mongodb.

How can I map this so that I can see all documents (both ones with
action field as an object and ones with action as a string (each
document can have multiple action fields)) in elasticsearch? Thanks!

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.