Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/3718#issuecomment-67886480
It's not deprecated for any good reason and I think we should undeprecate
it.
I'm not opposed to setting the job group, but I am opposed to setting it to
a random value and then throwing that away. That seems to have no point, and
would override a value that might have been set for some reason elsewhere.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
