Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/3718#issuecomment-67923806
I see. Yes, a random group ID string is not intuitive nor useful. And just
realize another reason that we shouldn't set group ID in
`SparkExecuteStatementOperation.run`: this class is also used in the Thrift
server, which can be accessed by multiple concurrent connections. Interleaved
concurrent SQL jobs may mess up the group IDs.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
