-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Elastic Agent] Revert logic in place to add the prefer_v2_template #18428
Labels
Comments
botelastic
bot
added
the
needs_team
Indicates that the issue/PR needs a Team:* label
label
May 11, 2020
ph
added
blocker
elastic-agent
Ingest Management:alpha1
Group issues for ingest management alpha1
and removed
needs_team
Indicates that the issue/PR needs a Team:* label
labels
May 11, 2020
Pinging @elastic/ingest-management (Team:Ingest Management) |
@BlakeRous can you take a look at this need to go in with the Elasticsearch PR, I think we can have the PR ready and we can synchronize the merge. |
What is that
El lun., 11 may. 2020 21:36, Pier-Hugues Pellerin <[email protected]>
escribió:
… @BlakeRous <https://github.com/BlakeRous> can you take a look at this
need to go in with the Elasticsearch PR, I think we can have the PR ready
and we can synchronize the merge.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#18428 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALBMFLJRYT5MIOZOL43UXYTRRBHSXANCNFSM4M6F7CUQ>
.
|
@BlakeRous oh typo, I've missed the e. sorry about that, I was faster than the autocomplete. I've meant @blakerouse |
The Elasticsearch PR is up at elastic/elasticsearch#56546 |
2 tasks
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Elasticsearch team will remove the requirement to send the prefer_v2_templates on every bulk request to enforce the use of v2 templates.
Because of this we have to revert in part the code in #18318 that inject the parameter option to the elasticsearch output but we should keep the change for the parameters since it does fix a bug in ES output.
The text was updated successfully, but these errors were encountered: