[
https://issues.apache.org/jira/browse/HIVE-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13733034#comment-13733034
]
Gunther Hagleitner commented on HIVE-3191:
------------------------------------------
[~jdere]: Yeah, sounds good. An INTERVAL type as per SQL standard would be
great in future. For now it makes sense to fail gracefully.
As for the fix: Both ComparisonOpMethodResolver as well as
DefaultMethodResolver throw NoMatchingMethodException when they find no
applicable UDF. So, I think it makes more sense to put the same check for
NumericOpReolver rather than check for null on the calling function. What do
you think?
> timestamp - timestamp causes null pointer exception
> ---------------------------------------------------
>
> Key: HIVE-3191
> URL: https://issues.apache.org/jira/browse/HIVE-3191
> Project: Hive
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: N Campbell
> Assignee: Jason Dere
> Attachments: HIVE-3191.1.patch
>
>
> select tts.rnum, tts.cts - tts.cts from cert.tts tts
> Error: Query returned non-zero code: 12, cause: FAILED: Hive Internal Error:
> java.lang.NullPointerException(null)
> SQLState: 42000
> ErrorCode: 12
> create table if not exists CERT.TTS ( RNUM int , CTS timestamp)
> stored as sequencefile;
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
