THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Add a optional field
description
for Transformation to allow user set detailed information for the operation- if not set, the description would be name of transformation
- Add a execution config option
table.optimizer.splitseparate-name-and-description
to decide whether generated Transformation would use the proposed simplified name or not- it is true by default
- when it is true, the generated Transformation will has a simplified name and responding detailed description as proposed in this FLIP
- when it is false, the description and name of Transformation will the same as what it is before this FLIP
- Add a pipeline config option
pipeline.tree-mode-vertex-description
to control the style of description- it is false by default, so that no side effects on DataStreamAPI, will be set as true by default at sql planner.
- if you don't like the tree-mode description proposed by this FLIP you can set it to false
- Rest API/Web UI changes
- "/jobs/${jobId}" will return the both name and description of all vertices, a new field
description
will be added to JobVertexDetailsInfo responding to the description of vertex. - "/jobs/${jobId}/plan" will return both name and description of all vertices, a new field
name
will be added to vertex info in JsonPlan of job graph. - at web ui, we will display the description of a job vertex instead of name of job vertex for details and display name at the topology
- "/jobs/${jobId}" will return the both name and description of all vertices, a new field
...