You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| 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)
The text was updated successfully, but these errors were encountered:
@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.
| 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)
The text was updated successfully, but these errors were encountered: