Github user JasonMWhite commented on the pull request:
https://github.com/apache/spark/pull/12470#issuecomment-211712175
After some experimentation on the Scala side, I see that this PR would be a
significant departure from Scala's interface, where the schema and field names
are not factors in equality checks at all. Column ordering is all that matters.
That seems odd to me, but perhaps that changes in 2.0.
There's a couple of other departures from Scala-style Rows:
- Accessing an ambiguous column doesn't throw an error
- You can't check row equality like `Row(1, 2) == Row(b=1, a=2)`
This second issue makes unit tests a little counterintuitive. The use of
kwargs at all, and making `Row` look dict-ish, might be an issue. I'll create
separate issues for these. Closing PR.
---
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]
