You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use antlr4 to complete parse statements. The generated statement must follow the original data structure, and should be compatible with the old statement.
In the original syntax file sql_parser.cup, the new syntax needs to be compatible with the syntax of the old version, using the syntax file sql_parser.cup of the old version as the reference standard.
Remove the logic of analytic functions in the statement and move the relevant logic to the new Analyzer framework. The new Analyzer is in the SQL/Analyzer directory.
If the code related to Privilege Check exists in the original analyzer, move the code related to privilege control into PrivilegeChecker.
When submitting the PR, please make sure there is unit test coverage for related changes.
Tasks
CreateFunctionStmt
DropFunctionStmt
ShowFunctionsStmt
How to participate?
Pick an issue you are interested in, click the issue link and leave a comment under the issue to sign up. One person can only choose one issue and the first person who picks the issue will be assigned.
After the issue is assigned, you should complete the task in 14 days. If you are unable to complete it within the specified time, the task will be withdrawn and assigned to others.
Participants are required to produce two pieces of content (forms including but not limited to mind maps, study notes, blogs, and tutorials) in the course of the activity, each of which should be at least 200 words.
Got questions? Join our Slack channel and find channel: #sql-planner.
Before you start
Read Contributing.md carefully to understand how to submit a pull request and how to configure BE and FE development environment.
Required work and output
Use antlr4 to complete parse statements. The generated statement must follow the original data structure, and should be compatible with the old statement.
In the original syntax file sql_parser.cup, the new syntax needs to be compatible with the syntax of the old version, using the syntax file sql_parser.cup of the old version as the reference standard.
Remove the logic of analytic functions in the statement and move the relevant logic to the new Analyzer framework. The new Analyzer is in the SQL/Analyzer directory.
If the code related to Privilege Check exists in the original analyzer, move the code related to privilege control into PrivilegeChecker.
When submitting the PR, please make sure there is unit test coverage for related changes.
Tasks
How to participate?
Pick an issue you are interested in, click the issue link and leave a comment under the issue to sign up. One person can only choose one issue and the first person who picks the issue will be assigned.
After the issue is assigned, you should complete the task in 14 days. If you are unable to complete it within the specified time, the task will be withdrawn and assigned to others.
Participants are required to produce two pieces of content (forms including but not limited to mind maps, study notes, blogs, and tutorials) in the course of the activity, each of which should be at least 200 words.
Got questions? Join our Slack channel and find channel: #sql-planner.
Before you start
Read Contributing.md carefully to understand how to submit a pull request and how to configure BE and FE development environment.
Sign the Contributor License Agreement before you make a pull request.
To learn more about StarRocks, please refer to StarRocks documentation.
Pull request requirements
The text was updated successfully, but these errors were encountered: