Github user darabos commented on the pull request:
https://github.com/apache/spark/pull/3346#issuecomment-114877984
Thanks for the note, @andrewor14. @Forevian is not working with Spark
lately, but I'm happy to take over this change from him. From a superficial
look at the code it seems to me that the same approach would still work. It's a
fantastically flexible solution yet it's entirely backward-compatible. Since
the old code path would remain unchanged, there is also very little risk in it.
So I'd like to dust it off and send a new pull request against the current
master. I'd just like to ask first if you have any recommendations for avoiding
the same fate as this pull request. Why was it never reviewed? Why did it not
get any comments? Thanks!
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
