[ 
https://issues.apache.org/jira/browse/HIVE-25610?focusedWorklogId=664015&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-664015
 ]

ASF GitHub Bot logged work on HIVE-25610:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 12/Oct/21 12:09
            Start Date: 12/Oct/21 12:09
    Worklog Time Spent: 10m 
      Work Description: pvary opened a new pull request #2715:
URL: https://github.com/apache/hive/pull/2715


   ### What changes were proposed in this pull request?
   Fixing partition column comments handling for Iceberg tables.
   Also AbstractSerDe provides methods to parse the column related fields from 
the properties. We should reuse them whenever possible.
   
   ### Why are the changes needed?
   Fixing the comment issue, and cleaning the code
   
   ### Does this PR introduce _any_ user-facing change?
   Fixes the issue
   
   ### How was this patch tested?
   Added unit tests


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: gitbox-unsubscr...@hive.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 664015)
    Remaining Estimate: 0h
            Time Spent: 10m

> Handle partition field comments for Iceberg tables
> --------------------------------------------------
>
>                 Key: HIVE-25610
>                 URL: https://issues.apache.org/jira/browse/HIVE-25610
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Peter Vary
>            Assignee: Peter Vary
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently partition comments are not sent to Iceberg during table creation.
> Also {{AbstractSerDe}} provides methods to parse the column related fields 
> from the properties. We should reuse them whenever possible.



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

Reply via email to