-
Notifications
You must be signed in to change notification settings - Fork 74
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
Dataset to data stream #24
Dataset to data stream #24
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One additional conversation we can have here is about our recommendation on the names of these data stream template directories. So far what we used is the second part of the dataset name that combined with the package it results in the dataset part. This applies in most cases but not all of them, that is why we allow to overwrite it.
I personally still like the naming we have as it makes browsing easy but I thought worth bringing up. In the end I don't expect this to change the spec, only our recommendation on naming.
versions/1/data_stream/spec.yml
Outdated
@@ -1,10 +1,10 @@ | |||
spec: | |||
- description: Folder containing a single dataset definition | |||
- description: Folder containing a single data stream definition |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Stumbled over this as it is not fully current. This a template for all data streams created for a specific type + dataset
combination. All logs-nginx.access-*
will use this template, independent of the namespace.
In my head, these are data stream templates.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm afraid I'm lost here. @ruflin, could you please elaborate more about this? data streams, templates, namespaces
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I'm lost too. I think it might be useful to add a definitions.md
or just a README.md
file in the versions/1
folder defining all these terms and concepts and how they relate to each other. The spec (so far) describes the syntactic relationships but I also have to admit that I don't fully understand all the semantic relationships between these concepts.
@ruflin can you please make a new PR to add such a file? I think you are the only(?) one who understands all these terms (old and new), the corresponding concepts, and the relationships between them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mtojek @ycombinator Before we get this change in, I would like to answer all the questions around dataset / data_stream to make sure we don't introduce breaking changes to the spec before we are 100% confident these are the right changes. I'll set up a call.
c48677d
to
72503d2
Compare
Ok, so once you push this change to master, we'll block introducing next changes to this repository until the package-registry and all integrations are adjusted? |
Yes. But to make the transition quick, I would say we should try to get the PRs ready in |
I think we can safely push this to master. Then:
Points 1. and 2. can go in parallel. I'm not sure about the package-storage, but I bet this one should go as the last one? |
Actually the same question goes to Kibana. Are we safe to introduce such renaming or is it better to schedule it? @ruflin |
We should schedule this change together with Kibana. For my two recent breaking changes to the registry @jfsiii has worked some magic that both version work which is also a best case scenario here. If we can do that, it means Kibana merges + Backports this first, then we get it in and roll it out to all of the parts mentioned above. Can you sync up with @jfsiii on this? If it becomes complicated on the Kibana side to have it backward compatible, we do a coordinated merge which might break some things for 24h which depend on snapshots. |
I'm unclear as to why this PR needs to be scheduled with a Kibana PR. This PR just changes the spec. It does not change any packages. So I'm not understanding the impact of this PR on Kibana. What am I missing? |
@ycombinator If we get this PR in without the changes ready on the Kibana side, it means if we have other changes to the package-spec and want to roll it out, we can't as it will break things. So just merging it will not have a direct impact on Kibana but it will hold development back on other things in the spec. |
@ruflin I'm not totally clear on the how the spec changes map to Registry & Kibana code/type changes but am happy to sync up with @mtojek. @jen-huang did a lot of We do reference |
@jfsiii @ycombinator Could you sync up to push this forward? Please pull me in if needed. Please directly also discuss #19 to make sure everyone is aware of all the changes coming. |
@ycombinator I'm not sure why the CI didn't report problems with test directories: https://github.com/ycombinator/package-spec/tree/dataset-to-data_stream/code/go/internal/validator/test/packages/bad_deploy_variants There are still "dataset" folders and it failed for me in the local environment. EDIT: You can also rebase the PR. |
72503d2
to
f706b65
Compare
… property renaming
@mtojek Looks like CI just failed as expected: https://beats-ci.elastic.co/blue/organizations/jenkins/Beats%2Fpackage-spec/detail/PR-24/6/pipeline. Yay! Fixing... |
…fig_templates`->`policy_templates` renaming (#78699) * Match elastic/package-spec#24 `datasets`->`data_streams` property renaming * Match elastic/package-spec#24 `datasets.name`->`data_streams.dataset` property renaming * Match elastic/package-spec#24 `/dataset`->`/data_stream` directory renaming * Match elastic/package-spec#50 `config_templates`->`policy_templates` property renaming * Update API integration test fixtures (test packages) * Temporarily skip API integration tests * Temporarily skip more API integration tests * Pin to custom docker image, unskip test suites, clean up broken icon paths in test package manifests * Skip the only (yay!) failing test suite * Revert "Skip the only (yay!) failing test suite" This reverts commit 3db32e2. * Re-skip tests and revert docker image Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
…fig_templates`->`policy_templates` renaming (elastic#78699) * Match elastic/package-spec#24 `datasets`->`data_streams` property renaming * Match elastic/package-spec#24 `datasets.name`->`data_streams.dataset` property renaming * Match elastic/package-spec#24 `/dataset`->`/data_stream` directory renaming * Match elastic/package-spec#50 `config_templates`->`policy_templates` property renaming * Update API integration test fixtures (test packages) * Temporarily skip API integration tests * Temporarily skip more API integration tests * Pin to custom docker image, unskip test suites, clean up broken icon paths in test package manifests * Skip the only (yay!) failing test suite * Revert "Skip the only (yay!) failing test suite" This reverts commit 3db32e2. * Re-skip tests and revert docker image Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
…fig_templates`->`policy_templates` renaming (#78699) (#79183) * Match elastic/package-spec#24 `datasets`->`data_streams` property renaming * Match elastic/package-spec#24 `datasets.name`->`data_streams.dataset` property renaming * Match elastic/package-spec#24 `/dataset`->`/data_stream` directory renaming * Match elastic/package-spec#50 `config_templates`->`policy_templates` property renaming * Update API integration test fixtures (test packages) * Temporarily skip API integration tests * Temporarily skip more API integration tests * Pin to custom docker image, unskip test suites, clean up broken icon paths in test package manifests * Skip the only (yay!) failing test suite * Revert "Skip the only (yay!) failing test suite" This reverts commit 3db32e2. * Re-skip tests and revert docker image Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
This PR updates the spec to rename
dataset
references in packages todata_stream
.Concretely, the following elements of packages are changed:
manifest.yml
file, thedatasets
property must now be calleddata_streams
instead.dataset
folder must now be calleddata_stream
instead.Resolves #18.