Mapping conflict (without any existing mappings)


#1

Hi,

I'm using the elasticsearch's python client, trying to index new data into a non-existing index (there are NO indices in the cluster at all)
when indexing the first document, the following exception is thrown:

RequestError: TransportError(400, u'illegal_argument_exception', u'mapper [ip.ip.checksum] of different type, current_type [text], merged_type [ObjectMapper]')

I have no idea what causes this exception since I have 0 documents in the cluster (also 0 indices, Counting on the index to be generated automatically when I index the first doc)

I've searched for solutions but I couldn't find any which match my case (mapping conflict without any existing mapping..)


(Christian Dahlqvist) #2

What does your document look like? Are you using field names with dots in them that can potentially cause mapping conflicts with the document? Which version of Elasticsearch are you using?


#3

The dots were the problem. I tottally forgot about the conflict that might occur with nested types.

Thanks :slight_smile:


(system) #4

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.