I used the field naming to 'ownerid'. Strictly 'ownerid', not 'ownerId', 'ownerId', 'OwnerID' things..
These are processed well. But only 'ownerid' is not working when I map first time. I never had defined 'ownerid'. NEVER!
Here is example.
{
"error": {
"root_cause": [
{
"type": "illegal_argument_exception",
"reason": "mapper [ownerid] cannot be changed from type [int] to [long]"
}
],
"type": "illegal_argument_exception",
"reason": "mapper [ownerid] cannot be changed from type [int] to [long]"
},
"status": 400
}
So I guessed It's reserved thing. but I can't know where exist. And no guides, issues...
Anybody has same issue? or please reproduce this issue and check out.
oh. elasticsearch version is 2.4.1. this is important.
The error indicates that you already have a field called ownerid that is mapped as int. You may not have explicitly mapped this; if you have dynamic mapping enabled then Elasticsearch would have dynamically mapped this field from an indexed document, inferring the type from the field value.
@dadoonet I checked that your test from first app install repeatedly. First, I'm so sorry. The cause of my issue was fail of restoring snapshot. I once did fail restoring of snapshot. So I guess that issue occured since garbage thing. I reinstalled app and mapped, It worked well. Thanks for your patient about such a idiot question. I'm really sorry.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.