[
https://issues.apache.org/jira/browse/HIVE-21619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16829544#comment-16829544
]
Hive QA commented on HIVE-21619:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12967384/HIVE-21619.03.patch
{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.
{color:green}SUCCESS:{color} +1 due to 15934 tests passed
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/17069/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/17069/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-17069/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12967384 - PreCommit-HIVE-Build
> Print timestamp type without precision in SQL explain extended
> --------------------------------------------------------------
>
> Key: HIVE-21619
> URL: https://issues.apache.org/jira/browse/HIVE-21619
> Project: Hive
> Issue Type: Bug
> Components: CBO
> Reporter: Jesus Camacho Rodriguez
> Assignee: Jesus Camacho Rodriguez
> Priority: Major
> Attachments: HIVE-21619.01.patch, HIVE-21619.01.patch,
> HIVE-21619.01.patch, HIVE-21619.01.patch, HIVE-21619.01.patch,
> HIVE-21619.02.patch, HIVE-21619.02.patch, HIVE-21619.02.patch,
> HIVE-21619.02.patch, HIVE-21619.03.patch, HIVE-21619.patch
>
>
> Hive dialect should print timestamp type without precision in generated SQL,
> since currently Hive does not support user-defined precision.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
