New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failing for Amazon Elasticsearch 6.3 #100

ivkos opened this Issue Nov 23, 2018 · 1 comment


None yet
2 participants

ivkos commented Nov 23, 2018

The library fails when the following conditions are met:


  • Amazon Elasticsearch 6.3
  • spring-boot-starter-data-jest - 3.1.5.RELEASE
  • spring-boot-starter-parent - 2.0.5.RELEASE
  • aws-signing-request-interceptor - 0.0.22
  • org.elasticsearch:elasticsearch - 5.6.13
@Document(indexName = "some_entities", type = "some_entity")
@Setting(settingPath = "/elasticsearch/analyzers.json")
public class SomeEntity
    @Field(type = Keyword)
    private Integer id;

com.github.vanroy.springdata.jest.exception.JestElasticsearchException: Cannot execute jest action , response code : 400 , error : {"root_cause":[{"type":"illegal_argument_exception","reason":"Could not convert [id.index] to boolean"}],"type":"illegal_argument_exception","reason":"Could not convert [id.index] to boolean","caused_by":{"type":"illegal_argument_exception","reason":"Failed to parse value [not_analyzed] as only [true] or [false] are allowed."}} , message : null
	at com.github.vanroy.springdata.jest.mapper.DefaultErrorMapper.mapError(
	at com.github.vanroy.springdata.jest.JestElasticsearchTemplate.execute(
	at com.github.vanroy.springdata.jest.JestElasticsearchTemplate.executeWithAcknowledge(
	at com.github.vanroy.springdata.jest.JestElasticsearchTemplate.putMapping(
	... 98 more

The only workaround I've found so far is using an older Amazon Elasticsearch cluster version (i.e. 5.6).


This comment has been minimized.


VanRoy commented Nov 26, 2018

Hi @ivkos . The new version if 3.2.0.RELEASE released tonight is now compatible with ES 6.x.
Please feel free to feedback if you detect some issues.

@VanRoy VanRoy closed this Nov 26, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment