Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2337#issuecomment-56408573
> More than that, it's private[spark], which means I have to hardcode the
string in my code and hope it never changes...
Yeah, I wasn't suggesting that as a substitute for a real public API.
> Just to be clear, I'm ok with switching to using job groups to achieve
what HoS needs (and close this PR/bug), but even that path seems like it could
use some changes to make the lives of people using the API easier.
I think there are two separate design issues here:
1. How do I get the jobId associated with a job that I've launched?
2. Given that I know the jobId, how do I find out more information about
the status of that job?
Let's keep this open for now, since this PR sounds like an okay way to
address 1) and these two concerns are largely orthogonal.
---
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
