Hi folks
As part of the Tez APIs, every object ( Input / Output / Processor /
EdgeManagerPlugin / VertexManagerPlugin ) can be associated with its own user
provided payload to set itself up. The format of this payload is not known to
Tez as it could be a java serialized object/protobuf/xml, etc. In a lot of
cases, this payload is usually a serialized configuration object. To make it
easy to expose this configuration aspects in the Tez UI, a setHistoryText API
was added to the UserPayload class.
This history text was meant to be something which could be displayed in the UI.
To make this more meaningful, I am proposing that we define a common standard
that everyone using this API can conform to. This will allow the UI to make
some assumptions about the structure and display the data in a more consumable
manner.
A possible standard could be:
- history text should be a json blob mapping to a json object containing
key-val pairs.
- the keys that should be used:
- description: value should be a simple string
- config: value should be an object in the format: { “key1”: “value1”,
“key2” : “value2”, … }
The above is not a final version or the recommended one. Folks like Jonathan
and Prakash who are working on TEZ-8 may have stronger recommendations on the
json structure.
@Gunther, @Rohini - any comments from the user point of view for exposing
Hive/Pig information in the Tez UI?
Comments/Questions/Suggestions?
thanks
— HItesh
