-
Notifications
You must be signed in to change notification settings - Fork 3.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
Move note to section about the type option #8604
Conversation
@andrewvc On a related note, I'm not sure how the removal of types in ES affects the |
It's still valid because we are still compatible with ES 5.x.
Also, ES 6.0 does support types, just with the limitation of one type per
index
We should possibly warn when we detect types being used with ES6.
…On Nov 7, 2017 9:16 PM, "DeDe Morton" ***@***.***> wrote:
@andrewvc <https://github.com/andrewvc> On a related note, I'm not sure
how the removal of types in ES affects the type option for LS input
plugins. Will the option be deprecated, or still valid for 6.0?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#8604 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAIBY0hQNcLAzrvFNu1RgCLm_sOy7Ip7ks5s0RzxgaJpZM4QVwwv>
.
|
@dedemorton should we close this out? Is this change still something we want to do? |
Yes. For now, I'll just merge this PR to move the note. It basically moves the content to live under the |
(no need for approval because this PR simply moves existing content...doesn't add anything new). |
Takes the note that was removed in logstash-plugins/logstash-input-beats#267 and moves it to the doc about the
type
option. Now this content will appear in the correct place, but it's conditionally coded in the shared file so that it only shows up in the doc about the beats input plugin.Note that the statement will appear in two places until the plugin docs for 6.0 are re-published because I didn't get the change into the plugin branch in time for 6.0.