You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Kokila N (Jira)" <ji...@apache.org> on 2024/01/29 06:59:00 UTC
[jira] [Commented] (HIVE-28007) Java 11: Failure of TimeStamp tests
[ https://issues.apache.org/jira/browse/HIVE-28007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17811751#comment-17811751 ]
Kokila N commented on HIVE-28007:
---------------------------------
Two DATETIME format changes in JDK11:{*}D{*} represents DAY_OF_YEAR as in it counts days from 1-366 which requires DDD in format (dd represents DAY_OF_MONTH -> counts 1-31).
*JDK8:* If given format is DD(width=2) but the day is actually with 3 width(above 100) in the input value then this will trigger error that width exceeds 2 and returns null.
*JDK11:* If given format is DD or DDD then max width is set to 3(hardcoded) so it considers days with 2 and 3 digits as valid and returns the value which corresponds to the day in the year.
*Commit:* [https://github.com/openjdk/jdk11u-dev/commit/4900a8320308f0b55344644a599c4d86afec72d2]{*}A{*} represents MILLI_OF_DAY.
*JDK8:* Depending on the number of A's given in format, max width is set and only those number of digits are considered and if the converted value exceeds max width , it will throw error and return null.
*JDK11:* A's max width is hardcoded to 19, so an error is thrown only if it exceeds 19 digits.
*Commit:* [https://github.com/openjdk/jdk11u-dev/commit/386a77fd91612badbb14edc05fe4142415192b46]Changing the value in test cases should be fine for these tests in *TestGenericUDFDateFormatEvaluate.java and TestGenericUDFFromUnixTimeEvaluate.java* as the JDK behaviour has changed.
> Java 11: Failure of TimeStamp tests
> ------------------------------------
>
> Key: HIVE-28007
> URL: https://issues.apache.org/jira/browse/HIVE-28007
> Project: Hive
> Issue Type: Sub-task
> Components: Hive
> Affects Versions: 4.1.0
> Reporter: Kokila N
> Assignee: Kokila N
> Priority: Major
>
> Test cases are failing with value changes in timestamp. Check if its jdk behavioural change and solve.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)