[
https://issues.apache.org/jira/browse/DRILL-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923470#comment-13923470
]
Jacques Nadeau commented on DRILL-399:
--------------------------------------
Drill also creates a default schema. Currently that is a random selection.
That is why CP works for you. Short term, if you are trying to do constrained
testing and want a workaround, I believe you can avoid doing fully qualified
schema names by only including a single storage engine in your
storage-engines.json file. This it was default to the schema you want to
query.
> Specifying schema=dfs and not specifying schema at query does not work
> ----------------------------------------------------------------------
>
> Key: DRILL-399
> URL: https://issues.apache.org/jira/browse/DRILL-399
> Project: Apache Drill
> Issue Type: Bug
> Reporter: Ramana Inukonda Nagaraj
>
> Repro steps:
> Start sqlline
> bin/sqlline -u jdbc:drill:schema=dfs -n admin -p admin
> 0: jdbc:drill:schema=dfs> select * from `/region.parquet`;
> Query failed: org.apache.drill.exec.rpc.RpcException: Remote failure while
> running query.[error_id: "76bae1a1-3b86-4dc8-9cd4-6e42cb7fe900"
> endpoint {
> address: "perfnode166.perf.lab"
> user_port: 31010
> control_port: 31011
> data_port: 31012
> }
> error_type: 0
> message: "Failure while parsing sql. < ValidationException:[
> org.eigenbase.util.EigenbaseContextException: From line 1, column 15 to line
> 1, column 31 ] < EigenbaseContextException:[ From line 1, column 15 to line
> 1, column 31 ] < SqlValidatorException:[ Table \'/region.parquet\' not found
> ]"
> ]
> Error: exception while executing query (state=,code=0)
> This works though.
> 0: jdbc:drill:schema=dfs> select * from dfs.`region.parquet`;
> Also, specifying cp as schema works.
> [root@perfnode166 drill]# bin/sqlline -u jdbc:drill:schema=cp -n admin -p
> admin
> 0: jdbc:drill:schema=cp> select * from `employee.json`;
--
This message was sent by Atlassian JIRA
(v6.2#6252)
