[ 
https://issues.apache.org/jira/browse/IMPALA-9531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17158586#comment-17158586
 ] 

ASF subversion and git services commented on IMPALA-9531:
---------------------------------------------------------

Commit 6d1a707cf50c2297972a69a7c0469afe4a78d739 in impala's branch 
refs/heads/master from Adam Tamas
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=6d1a707 ]

IMPALA-9941: ExprTest.CastExprs fails when running with ASAN fix

Fixed the issue with the ASAN build where too short tokens in
timestamps fails because of indexing out of bounds because of a
missing check.
Updated some missed files connected to the drop of dateless timestamps
(IMPALA-9531) regarding tests, comments.

Testing:
 - Ran CORE tests
 - Ran ASAN with EE_TEST_SHARDS=6 (with the help of IMPALA-9887)

Change-Id: I75bd47b6627a2e338c46dc354f7e67d34c1abbcf
Reviewed-on: http://gerrit.cloudera.org:8080/16179
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>


> Drop support for "dateless timestamps"
> --------------------------------------
>
>                 Key: IMPALA-9531
>                 URL: https://issues.apache.org/jira/browse/IMPALA-9531
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Backend
>            Reporter: Csaba Ringhofer
>            Assignee: Adam Tamas
>            Priority: Minor
>             Fix For: Impala 4.0
>
>
> Currently cast("15:42:00" as timestamp) doesn't return NULL, but it should, 
> as the resulting timestamps are more or less useless:
> - other fileformats than text do not support them
> - most built-in unctions don't support them - even those where it could  make 
> sense
> IMPALA-5942 contains more details about these issues.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to