Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/18887
There's quite a log of unit tests that cover this code; forking would mean
also making those unit tests run against both versions of the code so that no
one breaks anything, and potentially fixing bugs in two different places if
they're found.
I'd rather avoid the overhead. The bulk of `FsHistoryProvider`, which is
the part that actually monitors the file system and makes decisions about when
to parse things, is mostly unchanged.
And the rest of this project is way more disruptive than this one change.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
