Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/10208#issuecomment-165215923
I suppose the decision is what we want to maintain more: our own
encode/decode logic, or potential dependency conflicts. If we test the
encode/decode logic well then we probably don't need to maintain it much, but
at the same time it's good to use a trusted library in case there's something
we missed. Though I agree the dependency thing could be more difficult to
maintain. I'm OK one way or the other, so we can just do it ourselves as
@srowen prefers.
---
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]
