paul-rogers commented on a change in pull request #2030: Update docs for 
Metastore to point that all format plugins are supported
URL: https://github.com/apache/drill/pull/2030#discussion_r394562214
 
 

 ##########
 File path: _docs/sql-reference/sql-commands/021-create-schema.md
 ##########
 @@ -4,9 +4,9 @@ date: 2019-05-31
 parent: "SQL Commands"
 ---
 
-Starting in Drill 1.16, you can define a schema for text files using the 
CREATE OR REPLACE SCHEMA command. Schema is only available for tables 
represented by a directory. To use this feature with a single file, put the 
file inside a directory, and use the directory name to query the table.
+Starting in Drill 1.16, you can define a schema for text files using the 
`CREATE OR REPLACE SCHEMA` command. Such schema is only available for tables 
represented by a directory. To use this feature with a single file, put the 
file inside a directory, and use the directory name to query the table or use 
table function with schema parameter instead.
 
 Review comment:
   Starting in Drill 1.16 you can define a schema for text files. Drill places 
a schema file in the root directory of your text table and so the schema 
feature only works for tables within a directory. If you have a single-file 
table, simply create a directory to hold that file and the schema file.
   
   In Drill 1.17, the provided schema feature is disabled by default. Enable it 
by setting the `store.table.use_schema_file` system/session option to true:
   
   ```
   ALTER SESSION SET `store.table.use_schema_file` = true
   ```
    
   Next you create the schema using the `CREATE OR REPLACE SCHEMA` command (as 
described where? Please point to an example, or put the example here.)
   
   As described (insert link), you can also use a table function to apply a 
query to individual queries. Or, you can place the table function within a 
view, and query the table through the view. (Would be good to have examples of 
these also.)

----------------------------------------------------------------
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]


With regards,
Apache Git Services

Reply via email to