Github user lirui-intel commented on the pull request:
https://github.com/apache/spark/pull/2176#issuecomment-53679584
Hi @rxin, thanks for the review! I can add interface to SimpleFutureAction
to get the job id if we shouldn't expose JobWaiter to users.
Hive on spark currently only uses foreach to submit the job, we can change
it to foreachAsync which just returns a SimpleFutureAction.
I agree this doesn't seem to be a perfect way to solve the problem and we
still have ComplexFutureAction to worry about. So please let me know if you
have a better idea in mind or if you think we shouldn't expose the job ID at
all.
---
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]
