Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/12524
@seayi -- can you close this PR, since it's a duplicate of #16620?
---
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
Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/12524
Can you update the PR description here to have the JIRA number
(SPARK-14658), not the PR number?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/12524
Also, the approach in this PR was discussed and rejected in #16620 (see
https://github.com/apache/spark/pull/16620#issuecomment-279125227 for a
description of why; the approach here will also
Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/12524
I just closed the PR as a duplicate and agree with @markhamstra that this
duplicates #16620 (let's move discussion about whether this is a duplicate to
the JIRA so it's recorded)
---
If
Github user mridulm commented on the issue:
https://github.com/apache/spark/pull/12524
@JoshRosen This is interesting : thanks for the details !
On the face of it, I think @markhamstra's comment about #16620 should apply
- but given the additional details, it might possible to
Github user markhamstra commented on the issue:
https://github.com/apache/spark/pull/12524
@JoshRosen I haven't tried to walk through the logs in your JIRA comment,
but it wouldn't surprise me at all if this is the same issue that we've been
working through in
Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/12524
Per [my comment on the
JIRA](https://issues.apache.org/jira/browse/SPARK-14658?focusedCommentId=15870777=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15870777),
I
Github user mridulm commented on the issue:
https://github.com/apache/spark/pull/12524
@seayi any progress on this ? Would be good to add this in if consistently
reproducible.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12524
Can one of the admins verify this patch?
---
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
