Github user zsxwing commented on the issue:
    > My main point is that whoever implements SPARK-17812 is going to have to 
deal with the issue shown in SPARK-17782, which means much of this patch is 
going to need to be changed anyway.
    @koeninger I agreed that this patch will be changed. However, this PR does 
fix a known issue for the current supported features and there is not user 
facing changes. Considering 2.0.2 may come out soon and I don't think 
SPARK-17812 will be done soon, I would like to merge this to fix issues for 
2.0.2. What do you think?

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 or file a JIRA ticket
with INFRA.

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to