Github user steveloughran commented on the issue:
https://github.com/apache/spark/pull/22952
bq. GlobExpander is private
that's correctable.
1. Make sure there are standalone tests (if none around)
1. Make sure that off filesystem.md there's something declaring normatively
WTF it expands
1. Provide a patch moving from @Private to @Public/Evolving
We can apply those changes to branch-2 and trunk, and, because the class is
already public you can use it knowing that in the development line of hadoop
we've committed to not moving, deleting or breaking it.
As usual: file a HADOOP-* jira with the patch, link me to it, I'll do my
best to review
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
