-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
(v1.3.11) (v1.6.9) [types removal] Specifying types in bulk requests is deprecated. (with Elasticsearch 7.10.0) #2869
Comments
Any updates on this? @Theoooooo @edsiper |
Welp, i've been struggling to test if this was fixed in the latest version because of the issue i've posted a few weeks ago #2886 (sorry this issue is quiet lengthy) I didn't have the time to properly do testing procedure to see what's going on regarding this wildcard routine issue. But if someone can walk into this issue and check if my statements on this issue are correct, that would be awesome. I can give you more precisions about this issue if it's not clear enough for you or someone else. |
Note: The elasticsearch documentation Same Issue of fluentd The patch of fluentd |
Signed-off-by: Takahiro Yamashita <nokute78@gmail.com>
Thank you for reporting issue. |
Thanks for the update on this issue, As i said above in my last comment, i can't upgrade because of the issue #2886. Without this getting fixed, i can't test any changes made. |
fluent#3140) Signed-off-by: Takahiro Yamashita <nokute78@gmail.com>
fluent#3140) Signed-off-by: Takahiro Yamashita <nokute78@gmail.com>
Bug Report
Describe the bug
I've used Fluentbit for a couple of months now and Elasticsearch keep changing there methods to insert data inside the service.
In future updates, the "Type" value inside the sended JSON will be removed but there is no option to remove this field with the default Elasticsearch output plugin.
To Reproduce
Expected behavior
I've wanted to have an option to remove the type field inside the plugin with an option like "use_type False". Overwise i need to configure a "MODIFY" block to remove this field for every messages that goes through the service to Elasticsearch.
Screenshots
Your Environment
CentOS7 1804
Fluentbit v1.3.11
Elasticsearch 7.10.0
Additional context
Exemple output configuration :
Warning logs :
And this is just a small exemple. I've got this error for every request Fluentbit does to Elasticsearch. As you guess, the log file grow up in size pretty quickly and i haven't find any option inside the official documentation about this issue
I saw this issue was fixed to fluend but not for fluentbit :/
The text was updated successfully, but these errors were encountered: