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-35195][table] Support the execution of create materialized table in continuous refresh mode #24750
Conversation
May I ask how to find the list of issues/requests I can contribute to? |
You can find it in jira: https://issues.apache.org/jira/projects/FLINK/issues/ |
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.
@lsyldliu Thanks for your contribution, I left some comments.
...g/apache/flink/table/operations/materializedtable/AlterMaterializedTableChangeOperation.java
Outdated
Show resolved
Hide resolved
...ateway/src/main/java/org/apache/flink/table/gateway/service/operation/OperationExecutor.java
Outdated
Show resolved
Hide resolved
.../java/org/apache/flink/table/gateway/service/materializedtable/MaterializedTableManager.java
Outdated
Show resolved
Hide resolved
.../java/org/apache/flink/table/gateway/service/materializedtable/MaterializedTableManager.java
Outdated
Show resolved
Hide resolved
...g/apache/flink/table/operations/materializedtable/AlterMaterializedTableChangeOperation.java
Outdated
Show resolved
Hide resolved
…reate generic table
… to generate execution plan for planner
…eMaterializedTableOperation
…r for continuous refresh mode
…ate materialized table refresh status and RefreshHandler
…ort drop materialized table
… for continuous refresh mode in SqlGateway
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.
@lsyldliu Thanks for updating the code. LGTM. only left some minor comments.
operationExecutor, handle, createMaterializedTableOperation); | ||
} else { | ||
throw new SqlExecutionException( | ||
"Only support create materialized table in continuous refresh mode currently."); |
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.
The wording here is a bit strange. How about change it to . Currently, we only support creating materialized tables with continuous refresh mode.
operationExecutor.callExecutableOperation( | ||
handle, alterMaterializedTableChangeOperation); | ||
} catch (Exception e) { | ||
// drop materialized table while submit flink streaming job occur exception. Thus, weak |
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.
// drop materialized table while submit flink streaming job occur exception. Thus, weak | |
// drop materialized table while submitting flink streaming job occur exception. Thus, weak |
} | ||
} | ||
|
||
public static CatalogMaterializedTable.LogicalRefreshMode deriveLogicalRefreshMode( |
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.
We can add some documentation to this function.
} | ||
} | ||
|
||
public static CatalogMaterializedTable.RefreshMode deriveRefreshMode( |
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.
Add doc too.
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.
@hackergin Thanks for your reviewing, I think we can improve the minor comments in next PR.
What is the purpose of the change
Support the execution of create materialized table in continuous refresh mode
Brief change log
Verifying this change
This change added tests and can be verified as follows:
Does this pull request potentially affect one of the following parts:
@Public(Evolving)
: (no)Documentation