Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/15035
+1 on adding a test, otherwise this risks regressing in future
refactorings. Also, I'm not sure whether `SpecificMutableRow` itself is
necessarily the right place to be performing this type widening since that
could introduce / mask bugs in other uses of this API.
Also seems slightly dodgy to let users call `setInt` with a long since that
could cause / mask overflow bugs.
---
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]
