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

Hive QA commented on HIVE-20044:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12934722/HIVE-20044.3.patch

{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.

{color:green}SUCCESS:{color} +1 due to 14869 tests passed

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/13091/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/13091/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-13091/

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: 12934722 - PreCommit-HIVE-Build

> Arrow Serde should pad char values and handle empty strings correctly
> ---------------------------------------------------------------------
>
>                 Key: HIVE-20044
>                 URL: https://issues.apache.org/jira/browse/HIVE-20044
>             Project: Hive
>          Issue Type: Bug
>          Components: Serializers/Deserializers
>            Reporter: Teddy Choi
>            Assignee: Teddy Choi
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: HIVE-20044.1.branch-3.patch, HIVE-20044.1.patch, 
> HIVE-20044.1.patch, HIVE-20044.2.patch, HIVE-20044.3.patch, HIVE-20044.patch
>
>
> When Arrow Serde serializes char values, it loses padding. Also when it 
> counts empty strings, sometimes it makes a smaller number. It should pad char 
> values and handle empty strings correctly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to