AlexNilone opened a new issue, #7170: URL: https://github.com/apache/kyuubi/issues/7170
### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) ### Search before asking - [x] I have searched in the [issues](https://github.com/apache/kyuubi/issues?q=is%3Aissue) and found no similar issues. ### Describe the bug When using SparkListener to receive lineage information from the Spark event bus, I observed that the executionId in OperationLineageSparkEvent does not match the executionId from SparkListenerSQLExecutionStart. The latter matches the execution ID shown in the Spark Web UI. This discrepancy causes difficulty in associating lineage information with the corresponding SQL executions when outputting lineage data to files. @Override public void onOtherEvent(SparkListenerEvent event) { if (event instanceof SparkListenerSQLExecutionStart) { SparkListenerSQLExecutionStart e = (SparkListenerSQLExecutionStart) event; System.out.println("** executionId :" + e.executionId()); // ... } else if (event instanceof SparkListenerSQLExecutionEnd) { SparkListenerSQLExecutionEnd e = (SparkListenerSQLExecutionEnd) event; // output metrics info to file } else if (event instanceof OperationLineageSparkEvent) { OperationLineageSparkEvent e = (OperationLineageSparkEvent) event; System.out.println("** executionId :" + e.executionId()); } // ... } Is this a known issue? Or is there an alternative way to reliably link lineage events with SQL executions? ### Affects Version(s) 1.9 ### Kyuubi Server Log Output ```logtalk ``` ### Kyuubi Engine Log Output ```logtalk ``` ### Kyuubi Server Configurations ```yaml ``` ### Kyuubi Engine Configurations ```yaml ``` ### Additional context _No response_ ### Are you willing to submit PR? - [ ] Yes. I would be willing to submit a PR with guidance from the Kyuubi community to fix. - [ ] No. I cannot submit a PR at this time. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
