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

(v1.3.11) (v1.6.9) [types removal] Specifying types in bulk requests is deprecated. (with Elasticsearch 7.10.0) #2869

Closed
Theoooooo opened this issue Dec 16, 2020 · 5 comments · Fixed by #3140

Comments

@Theoooooo
Copy link

Theoooooo commented Dec 16, 2020

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

  • Install the latest version for the OS CentOS through the official repo available at the official documentation (v1.3.11)
  • Configure a output toward the service Elasticsearch (v7.10.0 in my case)
  • Check inside the log file "depreciation.log" tons of warning message " [types removal] Specifying types in bulk requests is deprecated."

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 :

[OUTPUT]
    Name es
    Match tronce_syslog_*
    Host ES_HOST
    Port 9200
    HTTP_User USERNAME
    HTTP_Passwd PASSWORD
    Logstash_Format True
    Logstash_Prefix tronce_syslog
    Logstash_DateFormat %Y-%m-%d

Warning logs :

[2020-12-16T17:14:57,034][DEPRECATION][o.e.d.a.b.BulkRequestParser] [HOSTNAME] [types removal] Specifying types in bulk requests is deprecated.
[2020-12-16T17:14:57,035][DEPRECATION][o.e.d.a.b.BulkRequestParser] [HOSTNAME] [types removal] Specifying types in bulk requests is deprecated.
[2020-12-16T17:14:57,039][DEPRECATION][o.e.d.a.b.BulkRequestParser] [HOSTNAME] [types removal] Specifying types in bulk requests is deprecated.
[2020-12-16T17:14:57,040][DEPRECATION][o.e.d.a.b.BulkRequestParser] [HOSTNAME] [types removal] Specifying types in bulk requests is deprecated.
[2020-12-16T17:14:57,042][DEPRECATION][o.e.d.a.b.BulkRequestParser] [HOSTNAME] [types removal] Specifying types in bulk requests is deprecated.

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 :/

@Theoooooo Theoooooo changed the title (v1.3.11) [types removal] Specifying types in bulk requests is deprecated. (with Elasticsearch 7.10.0) (v1.3.11) (v1.6.9) [types removal] Specifying types in bulk requests is deprecated. (with Elasticsearch 7.10.0) Dec 23, 2020
@Platou
Copy link

Platou commented Jan 27, 2021

Any updates on this? @Theoooooo @edsiper

@Theoooooo
Copy link
Author

Theoooooo commented Jan 29, 2021

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)
From this point, this issue is preventing me to update to the lastest because this routine wildcard issue is sending data at every output i've configured.

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.

@nokute78
Copy link
Collaborator

nokute78 commented Mar 1, 2021

nokute78 added a commit to nokute78/fluent-bit that referenced this issue Mar 1, 2021
Signed-off-by: Takahiro Yamashita <nokute78@gmail.com>
@nokute78
Copy link
Collaborator

nokute78 commented Mar 1, 2021

Thank you for reporting issue.
I sent a patch #3140. Could you check it ?

@Theoooooo
Copy link
Author

Thank you for reporting issue.
I sent a patch #3140. Could you check it ?

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.
(This issue is quiet lengthy, if you need informations about it, i'm free to gave you what you need)

edsiper pushed a commit that referenced this issue Mar 2, 2021
Signed-off-by: Takahiro Yamashita <nokute78@gmail.com>
edsiper pushed a commit that referenced this issue Mar 4, 2021
Signed-off-by: Takahiro Yamashita <nokute78@gmail.com>
DrewZhang13 pushed a commit to DrewZhang13/fluent-bit that referenced this issue May 3, 2021
fluent#3140)

Signed-off-by: Takahiro Yamashita <nokute78@gmail.com>
DrewZhang13 pushed a commit to DrewZhang13/fluent-bit that referenced this issue May 3, 2021
fluent#3140)

Signed-off-by: Takahiro Yamashita <nokute78@gmail.com>
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

Successfully merging a pull request may close this issue.

3 participants