Details
-
New Feature
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
I don’t know if you have encountered the following scenario.
- When other platforms use JDBC to integrate with Livy, they need to save the session ID and application ID.
- When the connection creation fails, it may be that the spark session failed to start. At this time, they need to check the reason why the spark session failed to start.
I thought it would be possible to provide an action statement for getting the fields in the list.
// code placeholder
DESC LIVY SESSION;
field |
---|
id |
appId |
state |
logs |