Github user henryr commented on the issue:
https://github.com/apache/spark/pull/21482
I think consistency in Spark's naming convention (and therefore increased
discoverability by users) outweighs the advantage of naming it exactly for
the Impala equivalent. I do agree that multiple aliases probably aren't
worth the trouble at this point.
FWIW, I would have used this function if it had been available recently. So
it's not just hypothetical. And to me this provides some symmetry for
support for 'special' float values, since we already have isnan().
On 7 June 2018 at 15:36, Reynold Xin <[email protected]> wrote:
> Thanks, Henry. In general I'm not a huge fan of adding something because
> hypothetically somebody might want it. Also if you want this to be
> compatible with Impala, wouldn't you want to name this the same way as
> Impala?
>
> â
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/spark/pull/21482#issuecomment-395587233>, or
mute
> the thread
>
<https://github.com/notifications/unsubscribe-auth/AAFc1dxwI0XBXVvtW7qXKOu3BmbuXEV0ks5t6asDgaJpZM4UXVuP>
> .
>
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
