-
Notifications
You must be signed in to change notification settings - Fork 46
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
Support OpenSearch 2.x and Elasticsearch 8.x #81
Comments
Option to remove As it may require comprehensive changes, it will most likely NOT be back-ported to 1.5. |
Hi. First of all thanks for this great project. Can you already weigh up when you have time to fix this issue? Best, |
Thank you for the good word. I'm glad that you found it useful. I have the code working. Just wrapping up testing. I can actually push it today. |
* HCBatchOperations constructor deprecated * HCHttp.mappingType deprecated and moved to ElasticsearchBulkApi * ApiRequestFactory added to allow custom client API builders * ElasticsearchBulkApi added to handle Elasticsearch builders * ElasticsearchBulkApiPlugin added to handle Log4j2 config
I'll try to release it later this month |
Thank you very much ;) I really appreciate that :) |
Released in 1.6.0. OpenSearch 2.0 support is limited to legacy Index Template API (no composable templates). ISM is out-of-scope of this project - it will be a part of
|
Thanks for adding OpenSearch 2.0 support. It is very much appreciated! PS: We are using OpenSearch 2.3 with composable templates and this version of library. I'm not aware of anything broken. Could you elaborate? |
@turesheim Great news! 👍 I'm glad you got it working. I tested it only against 2.0 tbh. I had trouble with the API - I don't remember why anymore. I need to revisit it then. I'll happily make slight adjustments and accept PR for OpenSearch. However, given that it's forked from ES 7.10, API compatibility will unfortunately be only a side-effect rather than the goal of this project. This will obviously change once |
Hi. Thank you for releasing this issue. Best, |
Description
OpenSearch 2.0 and Elasticsearch 8.0 har removed the option to specify types in requests and any call from log4j2-elasticsearch to mentioned instances will return something like this and fail:
2022-05-13 08:07:36,304 [I/O dispatcher 1] DEBUG - - http-outgoing-4 << "{"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"Action/metadata line [1] contains an unknown parameter [_type]"}],"type":"illegal_argument_exception","reason":"Action/metadata line [1] contains an unknown parameter [_type]"},"status":400}"
Configuration
I don't think we need a particular configuration to recreate this.
Runtime (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: