ASF GitHub Bot logged work on GOBBLIN-877:

                Author: ASF GitHub Bot
            Created on: 09/Sep/19 22:06
            Start Date: 09/Sep/19 22:06
    Worklog Time Spent: 10m 
      Work Description: ZihanLi58 commented on issue #2731: [GOBBLIN-877]Add 
column metadata for partition for inline hive registration
   > @ZihanLi58 can you check why Travis failed?
   I think there is something wrong in the sever side because I cannot 
reproduce it locally. I'll try to force it run build again?
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.
For queries about this service, please contact Infrastructure at:

Issue Time Tracking

    Worklog Id:     (was: 309310)
    Time Spent: 40m  (was: 0.5h)

> Add column metadata for partition for inline hive registration
> --------------------------------------------------------------
>                 Key: GOBBLIN-877
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-877
>             Project: Apache Gobblin
>          Issue Type: Task
>            Reporter: Zihan Li
>            Priority: Major
>          Time Spent: 40m
>  Remaining Estimate: 0h
> Previously, we remove the schema.literal for partition.  Because Avro schemas 
> should _only_ be defined at the table level. Hive overrides table properties 
> if the same property is defined on the partition. Defining them at the 
> partition level may lead to partitions with inconsistent schemas. And because 
> column metadata is calculated from schema.literal, so we remove the column 
> metadata as well.
> Then we encounter a problem that presto cannot read data from orc file. 
> Because ORC (and other Hive serdes) need metadata in the partitions so that 
> coercion can be done between a partition schema and the table schema.
> So we need to treat Avro and other formate separately to make sure hive 
> registration works well so that user can read right data from Presto.

This message was sent by Atlassian Jira

Reply via email to