macksonmu commented on issue #1477:
URL:
https://github.com/apache/incubator-streampark/issues/1477#issuecomment-1279695968
Here I summarize the functions to be completed in version 1.2.4.
1.The table structure of the variable contains the following main contents.
- variable code is placeholder, For example the variable code is
"collect.kafka.cluster", it will be referenced as ${collect.kafka.cluster}, it
is unique within a team.
- variable name is removed, after discussion, it is not necessarily retained.
- variable value is the value of a specific variable, such as ip and port.
- description is a detailed introduction.
- team is the team the variable belongs to.
2.Basic functions of variable management.
- Add and modify variables: need to check whether the variable code is
unique under the current team.
- Deleting a variable: It is necessary to check whether it has been
referenced by the Application under the team to which the variable belongs. If
there is metadata management in the future, it is also necessary to check
whether it has been referenced by the metadata. If it is referenced, it will
prompt that the variable is referenced and cannot be deleted.
3.References in Flink sql and program args.
- In the application, the variables are uniformly referenced in the form of
placeholders ${xxx}, such as in Flink sql, program args.
- For a better experience, it is necessary to provide the function of
following the search prompt when entering variable placeholders. For example,
when entering "${", the variable list is displayed, and when "${kafka" is
entered, the display contains variables for kafka strings, in "variable code"
or "description".
- When the focus is lost, it is judged whether there is a variable
placeholder, and if so, a verification button is displayed to prompt the user
to perform verification. When the user clicks the verification button, the
replaced content of the placeholder is displayed, and only the user clicks the
verification button to click the submit button.
- If the user enters "okir23${j2Rts}pEt", this placeholder "${j2Rts}" will
not be replaced if "j2Rts" is not a variable we defined.
- If I copy some sql from a old application, and the sql includes some
placeholders, these placeholders will take effect in the new application.
4.Future plan
- Display the application or metadata list of a referenced variable in the
variable basic management module.
- Improve user experience.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
