Github user steveloughran commented on the issue:
https://github.com/apache/spark/pull/12695
As #13868 does adopt `org.apache.hadoop.io.Path`, I don't see this patch
being needed âthough it may highlight some places where the new code may need
applying
---
If your project is set
Github user steveloughran commented on the issue:
https://github.com/apache/spark/pull/12695
If you are working with windows paths; Hadoop's Path class contains the
code to do this, stabilised and addressing the corner cases
---
If your project is set up for it, you can reply to
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/12695
Let's close this PR
---
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,
Github user avulanov commented on the issue:
https://github.com/apache/spark/pull/12695
@vanzin This PR partly addresses a broader problem that path construction
is not consistent throughout Spark sources. Indeed, this is a potential source
of bugs. Here is an example
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/12695
Is this needed after #13868? pinging @avulanov
---
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
