Status

...

...

...

...

...

...

Draft：flip draft and poc

Motivation

...

1. 1. We use table name as the operator name for sources and sinks, because the framework would add "Source:" or "Sink:" prefix for operator name.
   2. For other operators, we use the node class name as the operator name
      1. The common header StreamExec and BatchExec is trimmed.
      2. Node id is added as a postfix so that we can distinguish the operators at a vertex with the same class.
      3. The final format of operator name would be something like Calc[1]/Deduplicate[2]/LocalGroupAggregate[3]/GlobalGroupAggregate[4]. this kind of name is similar to the name of the operator in DataStream: FlatMap/Map etc.
   3. Current operator name will be used as operator description, we will add exec node id as the prefix of operator description and append the description of exec node, so that it would be easy to match the description to the node.
   4. we will add an option to allow user to disable the name simplification
2. Introduce a tree-mode detail description for a vertex, which provides better formatted detail information at web, can be used when debugging and analyzing sql jobs at runtime.
   1. We need to add a field “description” in the job vertex summary at the rest api and modify the ui to use the description.
   2. We can also introduce an option to fall back to old mode, in case that people may not like it.
3. Add a prefix [vertex-idx]  for vertex name, so that we can easily match the name at WebUI and the content at log
   1. idx  would be the index of the job vertex order by node id of its head operator at StreamGraph, so that we can make the idx not changed when the program not changed.
4. In addition, some optimization in sql operator description could be done:
   1. currently literal string contains encoding and length, which is not necessary at the description
   2. change log mode can be show at the description, so that we can know what kind of record is expected

...