Hello,
Since it is recommend by the developer guide of Streampark website, to make a
post to this mailing lists before commit any code of new feature, I initiate
this post. If it is unnecessary, please ignore this message.
To whom it may concern, this is a raw proposal of "Git Tag" of Streampark
project:
Database table design: three available ways are:
1. Add a new field "tags" into table t_flink_project, store tags and branches
separately.
2. Rename filed "branches" to "branch_or_tag", add prefix("refs/heads/" or
"refs/tags/") when write this filed in order to distinguish.
3. Rename filed "branches" to "branch_or_tag_name", it only store the name of
branches/tags, then add a new field "branch_or_tag_type" to distinguish.
API design for frontend backend interaction:
API POST /flink/project/branches, return a new format which contain both name
and type(branch or tag). For now, it return a List<String> which only contain
the name.
API POST /flink/project/create and API POST /flink/project/update, add new
field in the parameter class "project" to both save the name and distinguish of
branches/tags. For now, it onle contains a String field "branches".
That is all for the proposal, please leave comment with your suggestion. Thank
you very much for your concern to this proposal.
Best regards,
Zhenhao Li
https://github.com/lizh501
