-
Notifications
You must be signed in to change notification settings - Fork 3k
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
fix(kafka-setup): Make topic name consistent with other images #7103
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.
Are these changes backward compatible? Will they break folks with custom topic names?
They are not. Folks with custom topic names will have to change the environment variable names they are using to set names. This PR makes that name consistent for all components. Kafka-setup job was the outlier using inconsistent env var names compared to GMS & standalone consumers. I have made a note about this in updating-datahub.md |
docs/how/updating-datahub.md
Outdated
@@ -6,6 +6,9 @@ This file documents any backwards-incompatible changes in DataHub and assists pe | |||
|
|||
### Breaking Changes | |||
|
|||
- #7103 This should only impact users who have configured explicit non-default names for DataHub's Kafka topics. The environment variables used to configure Kafka topics for DataHub used in the `kafka-setup` docker image have been updated to be in-line with other DataHub components, for more info see our docs on [Configuring Kafka in DataHub | |||
](https://datahubproject.io/docs/how/kafka-config). They have been suffixed with `_TOPIC`. This change should not affect any user who is using default Kafka names. |
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.
they have been suffixed with _TOPIC_NAME right?
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.
Before they were suffixed with _TOPIC, now it's _TOPIC_NAME
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.
Updated the doc.
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.
Once the doc is updated LGTM
Checklist