Github user zasdfgbnm commented on the issue:
https://github.com/apache/spark/pull/14027
OK, but will the status of the original JIRA keep being "won't fix", if
someone decide to reopen the discussion on it?
Can anyone give a comment on whether the running on foreground feature
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14027
I'm suggesting you keep the conversation together with the original JIRA,
at least. I don't know if it was going to be merged or not, but it was not
updated by the author in any event.
---
If your
Github user zasdfgbnm commented on the issue:
https://github.com/apache/spark/pull/14027
I followed that PR (https://github.com/apache/spark/pull/3881)
"I was under the impression all the shell scripts were getting refactored
and that this patch had become obsolete. I agree it's
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14027
Please don't open a duplicate JIRA. You can see the discussion on the
previous issue and JIRA, which is WontFix, mostly because it ultimately wasn't
followed up on. It's not out of the quesiton but
Github user zasdfgbnm commented on the issue:
https://github.com/apache/spark/pull/14027
I see similar pull request here:
https://github.com/apache/spark/pull/3881
But I didn't get what happened to that and why it was closed without adding
any support for running in
