-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Ingest Manager] Migrate from using stream.* fields to dataset.* fields #67672
Labels
Team:Fleet
Team label for Observability Data Collection Fleet team
Comments
ph
added
Team:Fleet
Team label for Observability Data Collection Fleet team
Ingest Management:beta1
labels
May 28, 2020
Pinging @elastic/ingest-management (Team:Ingest Management) |
@ph You have |
Yes, good catch. |
ruflin
pushed a commit
that referenced
this issue
Jun 9, 2020
Resolves #67672 Part of elastic/package-registry#491 See elastic/package-registry#492 for package registry changes. Updates existing queries to use `dataset.*` fields. from `stream.*` fields. I looked at the EPM code paths for asset installation, and did not find anything that would need to be changed based on the above package registry changes. We don't hardcode anything specific for field names. The package information (i.e. [nginx package info](https://epr.elastic.co/package/nginx/0.1.2/)) is not affected by the current package registry changes.
jen-huang
added a commit
to jen-huang/kibana
that referenced
this issue
Jun 9, 2020
…ic#68322) Resolves elastic#67672 Part of elastic/package-registry#491 See elastic/package-registry#492 for package registry changes. Updates existing queries to use `dataset.*` fields. from `stream.*` fields. I looked at the EPM code paths for asset installation, and did not find anything that would need to be changed based on the above package registry changes. We don't hardcode anything specific for field names. The package information (i.e. [nginx package info](https://epr.elastic.co/package/nginx/0.1.2/)) is not affected by the current package registry changes.
jen-huang
added a commit
that referenced
this issue
Jun 9, 2020
… (#68667) Resolves #67672 Part of elastic/package-registry#491 See elastic/package-registry#492 for package registry changes. Updates existing queries to use `dataset.*` fields. from `stream.*` fields. I looked at the EPM code paths for asset installation, and did not find anything that would need to be changed based on the above package registry changes. We don't hardcode anything specific for field names. The package information (i.e. [nginx package info](https://epr.elastic.co/package/nginx/0.1.2/)) is not affected by the current package registry changes.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are planning to move the fields from using
stream.*
todataset.*
in elastic/package-registry#482We will need to adjust our internal query to the new dataset prefix.
part of elastic/package-registry#491
The text was updated successfully, but these errors were encountered: