Github user lalinsky commented on the issue:
https://github.com/apache/spark/pull/14582
You were asking for more interest in the feature, there was no way I could
answer that. :)
Regarding the change itself, the system can already auto cast integer to a
timestamp, but not a floating point number. Floating number timestamps are
pretty common in a Python ecosystem, more so than integer ones. From my point
of view, that's an inconsistent and surprising behavior, that I wanted to
correct. I wouldn't send the patch if it didn't work for any number, but having
it done for just one number type seemed wrong to me.
---
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]
