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
[FLINK-14216][table] introduce temp system functions to FunctionCatalog #9822
Conversation
Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community Automated ChecksLast check on commit ad05fac (Wed Oct 16 08:44:32 UTC 2019) Warnings:
Mention the bot in a comment to re-run the automated checks. Review Progress
Please see the Pull Request Review Guide for a full explanation of the review process. The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commandsThe @flinkbot bot supports the following commands:
|
@xuefuz can you take a look? |
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.
Looks good. Had a couple of minor comments/questions. For the newly added methods, should we have tests covering them?
oi.getCatalogName(), | ||
oi.getDatabaseName(), |
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.
Don't we need to normalize the cat/db names as well, if they are case insensitive.
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.
currently catalog/db names are case sensitive in Flink. We haven't any normalization so far yet. I imagine we will be relying on the case sensitivity flag that should be introduced in Flink planner in the future.
For function name, it's a bit different as the existing code always normalize function 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.
Ok. sounds good.
ObjectIdentifier oi, | ||
TableFunction<T> function, | ||
TypeInformation<T> resultType) { |
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.
One more tab indention?
UserDefinedAggregateFunction<T, ACC> function, | ||
TypeInformation<T> resultType, | ||
TypeInformation<ACC> accType) { |
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.
Same as above.
@xuefuz thanks for your review! Tests will be added in the next PRs that introduce ambiguous/precise function reference |
oi.getCatalogName(), | ||
oi.getDatabaseName(), |
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.
Ok. sounds good.
@flinkbot run travis |
1 similar comment
@flinkbot run travis |
…ns to FunctionCatalog adapt existing APIs to the introduction of temporary system and temp functions according to FLIP-57. This closes apache#9822.
What is the purpose of the change
adapt existing APIs to the introduction of temporary system and temp functions according to FLIP-57
611ecde - introduce temp system functions and adapt existing APIs
cc357e4 - introduce temp functions and corresponding APIs
Brief change log
registerXxxFunction()
toregisterTemporarySystemXxxFunction()
userFunctions
in FunctionCatalog totempSystemFuncitons
registerTemporaryXxxFunction()
APIsVerifying this change
This change is already covered by existing tests
Does this pull request potentially affect one of the following parts:
@Public(Evolving)
: (no)Documentation
docs will be added separately