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

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

                Author: ASF GitHub Bot
            Created on: 20/Jul/21 23:13
            Start Date: 20/Jul/21 23:13
    Worklog Time Spent: 10m 
      Work Description: vihangk1 commented on pull request #2425:
URL: https://github.com/apache/hive/pull/2425#issuecomment-883765338


   There is no code changes in the latest commit (only some comment 
realignments). I am going to merge the patch without waiting for the precommit.


-- 
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: 625841)
    Time Spent: 0.5h  (was: 20m)

> Add optional fields to enable returning filemetadata for tables and partitions
> ------------------------------------------------------------------------------
>
>                 Key: HIVE-25281
>                 URL: https://issues.apache.org/jira/browse/HIVE-25281
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Vihang Karajgaonkar
>            Assignee: Vihang Karajgaonkar
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The hive_metastore.thrift interface defines the fields for Table and 
> Partition objects. Certain SQL engines like Impala use Table and Partition 
> from the HMS and then augment it to include additional metadata useful for 
> the engine itself e.g file metadata. It would be good to add support for such 
> fields in the thrift definition itself. These fields currently will be 
> optional fields so that HMS itself doesn't really need to support it for now, 
> but this can be supported in future depending on which SQL engine is talking 
> to HMS.



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

Reply via email to