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

chore: update KSQL_PULL_QUERIES_ENABLE_CONFIG name (MINOR) #4042

Closed
wants to merge 1 commit into from

Conversation

vcrfxia
Copy link
Contributor

@vcrfxia vcrfxia commented Dec 5, 2019

Description

#3778 introduced a config named ksql.pull.queries.enable for enabling/disabling pull queries. The config was renamed to ksql.query.pull.enable in #3856 after the 5.4.x branch was cut, and has therefore introduced a breaking change between 5.4 and master. This PR updates the config name in 5.4 to match the new name on master.

Testing done

Verified there are no docs or examples using the old config name that need to be updated. No additional code changes are needed since only the variable KSQL_PULL_QUERIES_ENABLE_CONFIG is used throughout the code.

Reviewer checklist

  • Ensure docs are updated if necessary. (eg. if a user visible feature is being added or changed).
  • Ensure relevant issues are linked (description should include text like "Fixes #")

@vcrfxia vcrfxia requested a review from a team as a code owner December 5, 2019 00:17
@@ -204,7 +204,7 @@
+ " which are secured with ACLs. Please enable only after careful consideration."
+ " If \"false\", KSQL pull queries will fail against a secure Kafka cluster";

public static final String KSQL_PULL_QUERIES_ENABLE_CONFIG = "ksql.pull.queries.enable";
public static final String KSQL_PULL_QUERIES_ENABLE_CONFIG = "ksql.query.pull.enable";
Copy link
Member

Choose a reason for hiding this comment

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

Does it matter that the variable names are non consistent with the config name? ("KSQL_PULL_QUERIES_ENABLE_CONFIG").

I assume not, since we don't publish these branches, do we?

Copy link
Contributor

Choose a reason for hiding this comment

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

I think it's ok. The config names are supposed to be hierarchical, but a variable named that way is less readable.

@AlanConfluent
Copy link
Member

LGTM from me.

@vcrfxia
Copy link
Contributor Author

vcrfxia commented Dec 6, 2019

Closing in favor of #4059

@vcrfxia vcrfxia closed this Dec 6, 2019
@vcrfxia vcrfxia deleted the disable-pull-config branch May 18, 2020 16:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants