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

ASF GitHub Bot commented on DRILL-7138:
---------------------------------------

arina-ielchiieva commented on issue #1719: DRILL-7138: Implement command to 
describe schema for table
URL: https://github.com/apache/drill/pull/1719#issuecomment-477692710
 
 
   @vvysotskyi please review.
 
----------------------------------------------------------------
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:
[email protected]


> Implement command to describe schema for table
> ----------------------------------------------
>
>                 Key: DRILL-7138
>                 URL: https://issues.apache.org/jira/browse/DRILL-7138
>             Project: Apache Drill
>          Issue Type: Sub-task
>            Reporter: Arina Ielchiieva
>            Assignee: Arina Ielchiieva
>            Priority: Major
>              Labels: doc-impacting
>             Fix For: 1.16.0
>
>
> As part of schema provisioning project, it will be handy for the user to see 
> if table has schema and its content. 
> Command syntax:
> *describe schema for table dfs.tmp.`text_table`*
> By default schema will be output in JSON format (format schema is stored in 
> .drill.schema file):
> {noformat}
> {
>   "table" : "dfs.tmp.`text_table`",
>   "schema" : {
>     "columns" : [
>       {
>         "name" : "id",
>         "type" : "INT",
>         "mode" : "OPTIONAL"
>       }
>     ]
>   },
>   "version" : 1
> }
> {noformat}
> JSON format can be indicated explicitly:
> *describe schema for table dfs.tmp.`text_table` as json*
> Other formats:
> STATEMENT - schema will be output in the form of CREATE SCHEMA statement.
> *describe schema for table dfs.tmp.`text_table` as statement*



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

Reply via email to