Search exceptions, is value really an INT (field names/type)


#1

I am getting the following errors. I suspect it to be because I have some documents that have fields of the same name and a different type. I am struggling through the reference guide to get curl statement to get/delete documents with this specific field name.

Error: Request to Elasticsearch failed: {"error":"SearchPhaseExecutionException[Failed to execute phase [query], all shards failed; shardFailures {[uHsaFjj_RvmpYMnAZWVLKw][m1aps][0]: ElasticsearchException[java.lang.NumberFormatException: Invalid shift value in prefixCoded bytes (is encoded value really an INT?)]; nested: UncheckedExecutionException[java.lang.NumberFormatException: Invalid shift value in prefixCoded bytes (is encoded value really an INT?)]; nested: NumberFormatException[Invalid shift value in prefixCoded bytes (is encoded value really an INT?)]; }{[uHsaFjj_RvmpYMnAZWVLKw][m1aps][1]: ElasticsearchException[java.lang.NumberFormatException: Invalid shift value in prefixCoded bytes (is encoded value really an INT?)]; nested: UncheckedExecutionException[java.lang.NumberFormatException: Invalid shift value in prefixCoded bytes (is encoded value really an INT?)]; nested: NumberFormatException[Invalid shift value in prefixCoded bytes (is encoded value really an INT?)]; }{[uHsaFjj_RvmpYMnAZWVLKw][m1aps][2]: ElasticsearchException[java.lang.NumberFormatException: Invalid shift value in prefixCoded bytes (is encoded value really an INT?)]; nested: UncheckedExecutionException[java.lang.NumberFormatException: Invalid shift value in prefixCoded bytes (is encoded value really an INT?)]; nested: NumberFormatException[Invalid shift value in prefixCoded bytes (is encoded value really an INT?)]; }{[uHsaFjj_RvmpYMnAZWVLKw][m1aps][3]: ElasticsearchException[java.lang.NumberFormatException: Invalid shift value in prefixCoded bytes (is encoded value really an INT?)]; nested: UncheckedExecutionException[java.lang.NumberFormatException: Invalid shift value in prefixCoded bytes (is encoded value really an INT?)]; nested: NumberFormatException[Invalid shift value in prefixCoded bytes (is encoded value really an INT?)]; }{[uHsaFjj_RvmpYMnAZWVLKw][m1aps][4]: ElasticsearchException[java.lang.NumberFormatException: Invalid shift value in prefixCoded bytes (is encoded value really an INT?)]; nested: UncheckedExecutionException[java.lang.NumberFormatException: Invalid shift value in prefixCoded bytes (is encoded value really an INT?)]; nested: NumberFormatException[Invalid shift value in prefixCoded bytes (is encoded value really an INT?)]; }]"}
at


#2

If I could just get some help with the curl statement to delete all documents and indexes with a specific field name.

The reference guide is not doing it for me.

Thanks,
Jason


(Adrien Grand) #3

Exactly, this is something that Elasticsearch 1.x is lenient about and which will not be allowed anymore in Elasticsearch 2.0. I think the best advise here would be to reindex your content while avoiding to have the same field name being mapped differently across types.


(system) #4