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

Doctype deprecation #691

Closed

Conversation

andrewvc
Copy link
Contributor

@andrewvc andrewvc commented Sep 29, 2017

Resolves #669 by deprecating the doc_type option and moving the default type name from logs to doc.

We want to get this in before 6.0.0 GA otherwise it will have to wait for LS 7.0.0

The really nice thing about moving from logs to doc, aside from beats integration, is that it better reflects the generic nature of Logstash.

We will also need to add this to breaking changes in Logstash core.

@andrewvc
Copy link
Contributor Author

@dedemorton this potentially has a lot of implications for docs on the site. Would you be able to investigate the impact there?

@andrewvc
Copy link
Contributor Author

After this is merged we'll need to make sure to update the 6.0.0-rc2 lockfile with the latest version.

@elasticsearch-bot elasticsearch-bot self-assigned this Sep 29, 2017
Copy link
Contributor

@ph ph left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jordansissel
Copy link
Contributor

This is kind of tricky because document_type is not deprecated in Elasticsearch 5.x and Logstash 6.0 will talk to ES 5.x clusters.

I know there is urgency to land this, but please pause and evaluate how we can make this work and not annoy users who are using LS 6 to talk to ES 5 clusters.

@andrewvc
Copy link
Contributor Author

@jordansissel that's a good point. I'm open to not deprecating document type given that point.

@ph WDYT?

@jordansissel
Copy link
Contributor

LGTM with your revised :deprecated warning.

@elasticsearch-bot
Copy link

Andrew Cholakian merged this into the following branches!

Branch Commits
master 8e68170, 039e6e2, a08917a, fc2dfd5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants