Skip to content
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

error on php bin/console ongr:es:index:create apparently conflict with the Elastic Search Version #297

Closed
alejandrofloresm opened this issue Jan 22, 2018 · 5 comments

Comments

@alejandrofloresm
Copy link

| Bug? | yes
| SuluArticleBundle Version | 0.7.1
| Sulu Version | 1.6.13
| Elastic Search Version| 6.1.2

Actual Behavior

Throws the following error when running php bin/console ongr:es:index:create

{"error":{"root_cause":[{"type":"mapper_parsing_exception","reason":"No handler for type [string] declared on field [changer_contact_id]"}],"type": "mapper_parsing_exception","reason":"Failed to parse mapping [article]: No handler for type [string] declared on field [changer_contact_id]","cause d_by":{"type":"mapper_parsing_exception","reason":"No handler for type [string] declared on field [changer_contact_id]"}},"status":400}

Expected Behavior

Shouldn't be throwing the error and set correctly the index

Possible Solutions

If you have already ideas how to solve the issue, add them here.
(remove this section if not needed)

@wachterjohannes
Copy link
Member

@alejandrofloresm the current implementation of article-bundle seems not to be ready for elasticsearch ^6.0 and won't be with 1.0 on the first look. the problem is the ONGRElasticsearchBundle which is not able to handle ^2.4, ^5.0 and ^6.0 - maybe we find a way to introduce this in one of the minor releases of 1.x. if this is not possible we can only update with the 2.0 version of the article-bundle when we drop the 2.4 compatibility.

@EssamKhaled
Copy link

unfortunately same here :(

@wachterjohannes
Copy link
Member

@EssamKhaled you have to downgrade your elasticsearch to 5.* which works quite well.

@wachterjohannes
Copy link
Member

there is a related ticket for this #304

@niklasnatter
Copy link
Contributor

Thanks for reporting - this was fixed with #433

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants