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

Remove the feature flag allow.table.name.with.database #12402

Merged
merged 2 commits into from
Feb 13, 2024

Conversation

shounakmk219
Copy link
Collaborator

@shounakmk219 shounakmk219 commented Feb 12, 2024

Description

Removing the feature flag introduced in #8713 and allowing table name with . throughout in favour of supporting database concept in Pinot (discussed in issue #12333 ).

Release Notes

allow.table.name.with.database cluster config is removed

@shounakmk219 shounakmk219 changed the title Request filters to translate table name to fully qualified name Remove the feature flag in favour of supporting database concept Feb 12, 2024
@shounakmk219 shounakmk219 changed the title Remove the feature flag in favour of supporting database concept Remove the feature flag allow.table.name.with.database Feb 12, 2024
@codecov-commenter
Copy link

codecov-commenter commented Feb 12, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (43dadbf) 61.73% compared to head (cd64067) 61.71%.

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     
Flag Coverage Δ
custom-integration1 <0.01% <0.00%> (ø)
integration <0.01% <0.00%> (ø)
integration1 <0.01% <0.00%> (ø)
integration2 0.00% <0.00%> (ø)
java-11 61.66% <100.00%> (-0.01%) ⬇️
java-21 61.60% <100.00%> (-0.02%) ⬇️
skip-bytebuffers-false 61.69% <100.00%> (-0.02%) ⬇️
skip-bytebuffers-true 61.56% <100.00%> (-0.02%) ⬇️
temurin 61.71% <100.00%> (-0.02%) ⬇️
unittests 61.71% <100.00%> (-0.02%) ⬇️
unittests1 46.91% <0.00%> (-0.01%) ⬇️
unittests2 27.70% <100.00%> (-0.02%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@Jackie-Jiang Jackie-Jiang added the release-notes Referenced by PRs that need attention when compiling the next release notes label Feb 12, 2024
@@ -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;
Copy link
Contributor

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

Copy link
Collaborator Author

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?

Copy link
Contributor

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;
Copy link
Contributor

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

@Jackie-Jiang Jackie-Jiang merged commit 04b279e into apache:master Feb 13, 2024
19 checks passed
@gortiz gortiz added the backward-incompat Referenced by PRs that introduce or fix backward compat issues label Mar 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backward-incompat Referenced by PRs that introduce or fix backward compat issues release-notes Referenced by PRs that need attention when compiling the next release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants