[ 
https://issues.apache.org/jira/browse/DRILL-7058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bridget Bevens updated DRILL-7058:
----------------------------------
    Labels: doc-complete ready-to-commit  (was: doc-impacting ready-to-commit)

> Refresh command to support subset of columns
> --------------------------------------------
>
>                 Key: DRILL-7058
>                 URL: https://issues.apache.org/jira/browse/DRILL-7058
>             Project: Apache Drill
>          Issue Type: Sub-task
>          Components: Metadata
>            Reporter: Venkata Jyothsna Donapati
>            Assignee: Venkata Jyothsna Donapati
>            Priority: Major
>              Labels: doc-complete, ready-to-commit
>             Fix For: 1.16.0
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> Modify the REFRESH TABLE METADATA command to specify selected columns which 
> are deemed interesting in some form - either sorted/partitioned/clustered by 
> and column metadata will be stored only for those columns. The proposed 
> syntax is 
>   REFRESH TABLE METADATA  *_[ COLUMNS (list of columns) / NONE ]_*  <table 
> path>
> For example, REFRESH TABLE METADATA COLUMNS (age, salary) `/tmp/employee` 
> stores column metadata only for the age and salary columns. REFRESH TABLE 
> METADATA COLUMNS NONE `/tmp/employee` will not store column metadata for any 
> column. 
> By default, if the optional 'COLUMNS' clause is omitted, column metadata is 
> collected for all the columns.  
>  



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

Reply via email to