-
Notifications
You must be signed in to change notification settings - Fork 67
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
[Indexing Strategy] Change stream.* to dataset.* fields #491
Labels
Ingest Management:beta1
Group issues for ingest management beta1
Comments
ruflin
added a commit
to ruflin/package-registry
that referenced
this issue
Jun 3, 2020
Now the dataset intsead of the stream fields are added and validated. Part of elastic#491
ruflin
added a commit
to ruflin/package-registry
that referenced
this issue
Jun 3, 2020
Now the dataset intsead of the stream fields are added and validated. Updating also the base package. This will have to be pushed to the package-storage. Part of elastic#491
ruflin
added a commit
to ruflin/package-registry
that referenced
this issue
Jun 3, 2020
Now the dataset intsead of the stream fields are added and validated. Updating also the base package. This will have to be pushed to the package-storage. Part of elastic#491
This was referenced Jun 3, 2020
ruflin
added a commit
to elastic/kibana
that referenced
this issue
Jun 3, 2020
Indexing strategy now uses dataset.* instead of stream.* fields. For this the indexing strategy docs are updated. Part of elastic/package-registry#491
6 tasks
ruflin
added a commit
to ruflin/package-registry
that referenced
this issue
Jun 8, 2020
Now the dataset intsead of the stream fields are added and validated. Updating also the base package. This will have to be pushed to the package-storage. Part of elastic#491
ruflin
added a commit
to ruflin/package-storage
that referenced
this issue
Jun 8, 2020
This is part of elastic/package-registry#491 This PR adds the new dataset fields to each package. As soon as all PRs in the registry, Kibana and Agent are merged, the old stream fields can be removed.
ruflin
added a commit
to elastic/package-storage
that referenced
this issue
Jun 8, 2020
This is part of elastic/package-registry#491 This PR adds the new dataset fields to each package. As soon as all PRs in the registry, Kibana and Agent are merged, the old stream fields can be removed.
ruflin
added a commit
that referenced
this issue
Jun 8, 2020
Now the dataset intsead of the stream fields are added and validated. Updating also the base package. This will have to be pushed to the package-storage. Part of #491
ruflin
pushed a commit
to elastic/kibana
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
to elastic/kibana
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.
6 tasks
Closing, as this was completed and we even followed up renaming things to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In #482 it was discussed and decided to move from
stream.*
fields todataset.*
fields. This issue is to track the changes across all the different affected parts across the stack.* [ ] Update package format to use the correct terms in the manifest (@ruflin )stream.*
todataset.*
kibana#68322* [ ] Update code in Endpoint agent to enrich correct fields (@ferullo )(not used yet)It might be that some of the above changes will be breaking and a sync is needed between teams to get them merged at the same time.
The text was updated successfully, but these errors were encountered: