Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/12313
@rdblue Thank you for updating the patch. I was out of town late last week
and was busy on spark summit early this week. Sorry for my late reply. Having
name-based resolution is very useful! Since this is a major improvement and we
are pretty late in the 2.0 QA period, how about we re-target the work to 2.1?
Also, I feel it will be good to have a short design doc to discuss the
following:
1. DataframeWriter and SQL interfaces and how to switch between matching by
ordinals and matching by names.
2. Approaches for handling missing fields and new fields (both top level
fields and inner fields). It will be good to discuss the semantics when we have
missing fields and new fields as well as how to maintain the schema in the
metastore.
Based on the design, we can break the work to multiple pieces and get them
merged for 2.1 release.
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
