Hi,

Is there support for sessionId to be GUID for batch usecase ? or can the
sessionId be made to be user-defined.

This will be useful for uniquely identifying sessions across restarts or
crashes. We are maintaining client side mappings to session Id and restart
/ HA scenarios will make this session Id irrelevant.

Found this Jira ticket https://issues.cloudera.org/browse/LIVY-367 , but no
further comments on it.

It would be good if there is an option to assign GUID for a session,
similar to Yarn AppId, which will be unique for certain extent.

Please suggest what is the best way to maintain sessionIds across restarts
or HA scenarios ?

Regards,
Praveen M

Reply via email to