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: split key format feature flag #6695

Merged
merged 3 commits into from
Dec 2, 2020

Conversation

vcrfxia
Copy link
Contributor

@vcrfxia vcrfxia commented Dec 1, 2020

Description

This PR is stacked on #6694. Only the last commit needs to be reviewed.

This PR separates the current key format feature flag (ksql.key.format.enabled) into three:

  • ksql.key.format.enabled : controls the addition of new key formats. I've kept the old name in order to avoid clashes with feat: support PROTOBUF keys #6692
  • ksql.complex.key.format.enabled : controls support for array and struct keys
  • ksql.multicol.key.format.enabled : controls support for multi-column keys

Testing done

QTT

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 1, 2020 05:30
Copy link
Contributor

@agavra agavra left a comment

Choose a reason for hiding this comment

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

LGTM! Thanks @vcrfxia

@@ -138,7 +138,17 @@
public static final String KSQL_KEY_FORMAT_ENABLED = "ksql.key.format.enabled";
Copy link
Contributor

Choose a reason for hiding this comment

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

i've merged the other PR, so if you want to we can rename this (or just leave it as is, i'm OK with that too)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'll leave it for now since the old name is already embedded in some historic plans (with value false), no need to introduce yet another config to clutter the history. Plus this flag is going away soon ;D

@vcrfxia vcrfxia merged commit ad87d0c into confluentinc:master Dec 2, 2020
@vcrfxia vcrfxia deleted the key-fmt-flag branch December 2, 2020 19:09
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.

2 participants