Code of Conduct
Search before asking
Describe the bug
WARN AtlasLineageDispatcher: Send lineage to atlas failed. java.lang.IllegalStateException: Shutdown in progress, cannot add a shutdownHook
Affects Version(s)
master
Kyuubi Server Log Output
Kyuubi Engine Log Output
Kyuubi Server Configurations
Kyuubi Engine Configurations
Additional context
Hello, I’m a student studying big data, and recently I’ve been researching the integration of Apache Atlas and Spark lineage. I noticed that the Kyuubi extension you contributed can send Spark lineage to Atlas. However, in my usage, when I execute a single SQL statement using spark-sql -e, I encounter the following error:
WARN AtlasLineageDispatcher: Send lineage to atlas failed. java.lang.IllegalStateException: Shutdown in progress, cannot add a shutdownHook
As a result, the lineage data cannot be uploaded to Atlas. But if I run multiple SQL statements, it seems to “warm up” the Atlas client, and the error does not occur. Do you know how I could optimize this so that lineage can be sent successfully even when running only a single SQL statement?
Are you willing to submit PR?
Code of Conduct
Search before asking
Describe the bug
WARN AtlasLineageDispatcher: Send lineage to atlas failed. java.lang.IllegalStateException: Shutdown in progress, cannot add a shutdownHook
Affects Version(s)
master
Kyuubi Server Log Output
Kyuubi Engine Log Output
Kyuubi Server Configurations
Kyuubi Engine Configurations
Additional context
Hello, I’m a student studying big data, and recently I’ve been researching the integration of Apache Atlas and Spark lineage. I noticed that the Kyuubi extension you contributed can send Spark lineage to Atlas. However, in my usage, when I execute a single SQL statement using spark-sql -e, I encounter the following error:
WARN AtlasLineageDispatcher: Send lineage to atlas failed. java.lang.IllegalStateException: Shutdown in progress, cannot add a shutdownHook
As a result, the lineage data cannot be uploaded to Atlas. But if I run multiple SQL statements, it seems to “warm up” the Atlas client, and the error does not occur. Do you know how I could optimize this so that lineage can be sent successfully even when running only a single SQL statement?
Are you willing to submit PR?