-
Notifications
You must be signed in to change notification settings - Fork 1.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
Remove the feature flag allow.table.name.with.database
#12402
Conversation
allow.table.name.with.database
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #12402 +/- ##
============================================
- Coverage 61.73% 61.71% -0.02%
Complexity 207 207
============================================
Files 2428 2428
Lines 132828 132823 -5
Branches 20545 20544 -1
============================================
- Hits 82007 81978 -29
- Misses 44811 44838 +27
+ Partials 6010 6007 -3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
@@ -91,8 +91,6 @@ public static class Helix { | |||
|
|||
public static final String ENABLE_CASE_INSENSITIVE_KEY = "enable.case.insensitive"; | |||
public static final boolean DEFAULT_ENABLE_CASE_INSENSITIVE = true; | |||
public static final String ALLOW_TABLE_NAME_WITH_DATABASE = "allow.table.name.with.database"; | |||
public static final boolean DEFAULT_ALLOW_TABLE_NAME_WITH_DATABASE = false; |
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.
Should we consider keeping this config but only change the default to true? It might be useful for certain cases
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.
Yeah even I thought about that but as part of introducing database we will have lot of things like APIs, access control that's database aware so toggling the behaviour everywhere based on the feature flag will be complicated.
Do you have a strong use-case in mind which needs banning dot in table 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.
Going through the code again, seems we only looses the table name check by always allowing one dot. I think it should be fine
@@ -91,8 +91,6 @@ public static class Helix { | |||
|
|||
public static final String ENABLE_CASE_INSENSITIVE_KEY = "enable.case.insensitive"; | |||
public static final boolean DEFAULT_ENABLE_CASE_INSENSITIVE = true; | |||
public static final String ALLOW_TABLE_NAME_WITH_DATABASE = "allow.table.name.with.database"; | |||
public static final boolean DEFAULT_ALLOW_TABLE_NAME_WITH_DATABASE = false; |
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.
Going through the code again, seems we only looses the table name check by always allowing one dot. I think it should be fine
Description
Removing the feature flag introduced in #8713 and allowing table name with
.
throughout in favour of supportingdatabase
concept in Pinot (discussed in issue #12333 ).Release Notes
allow.table.name.with.database
cluster config is removed