Re: Error: DATA_READ ERROR: The JDBC storage plugin failed while trying setup the SQL query

2020-02-20 Thread David Du
I got dremio from this link:
https://download.dremio.com/community-server/4.1.4-202001240912140359-a90eb503/

then unzip, go to conf folder, open file dremio.conf, then change the port
from 31010 to 41010,

services: {
  coordinator.enabled: true,
  coordinator.master.enabled: true,
  executor.enabled: true,
  coordinator.client-endpoint.port: 41010

}
 then go to bin directory and type: ./dremio start
since apache drill also use port 31010, this is a conflict.

Thanks



On Wed, Feb 19, 2020 at 7:10 PM Paul Rogers 
wrote:

> Hi David,
>
> So I tried to reproduce the problem, but I could not get Dremio to start:
> it consistently crashes when I follow the GitHub community edition
> instructions. [1] Something about "Unable to find injectable based on
> javax.ws.rs.core.SecurityContext."
>
>
> I don't want to turn our attempt to diagnose a Drill issue into an attempt
> to diagnose my Dremo issue.
>
> What I had planned to do was to start the server, then use the Dremio JDBC
> driver to create a very simple Java program that uses JDBC to connect to
> Dremio and issues the query in question. Then, I planned to muck around
> with the table path: leaving out the schema part, etc. until I got Dremio
> to accept the query. This would tell us what Dremio wants.
>
> Once I had that information, I could then compare that with what Drill is
> sending and figure out how you might adjust your setup to get things to
> work.
>
> Given that I could not get past the step to get Dremio running, are you
> comfortable enough with Java to run the little experiment outlined above?
> Once you have a SELECT statement that works, we can move on to the next
> step above: working out how to get Drill to issue that statement.
>
> Thanks,
> - Paul
>
> [1] https://github.com/dremio/dremio-oss
>
>
>
>
> On Tuesday, February 18, 2020, 8:23:23 AM PST, David Du <
> d...@bcmcgroup.com> wrote:
>
>  Thanks for your response, from http://localhost:9047/space/Demo, then I
> run
> select * from weather, it works and got data back, then I reconfigured
> apache drill plugin:
> dremiodemo
> {
>   "type": "jdbc",
>   "driver": "com.dremio.jdbc.Driver",
>   "url": "jdbc:dremio:direct=localhost:41010",
>   "username": "admin",
>   "password": "admin",
>   "caseInsensitiveTableNames": true,
>   "enabled": true
> }
>
> then restarted drill and run commands:
>
> apache drill (dremiodemo.demo)> show *databases*;
>
> +---+
>
> | *  SCHEMA_NAME  * |
>
> +---+
>
> | cp.default|
>
> | dfs.default  |
>
> | dfs.root  |
>
> | dfs.tmp  |
>
> | dremiodemo.$scratch  |
>
> | dremiodemo.@admin|
>
> | dremiodemo.demo  |
>
> | dremiodemo.dremio
>
>   dremiodemo.sys|
>
> | dremiodemo.sys.cache  |
>
> | dremiodemo.testspace  |
>
> | dremiodemo|
>
> | information_schema|
>
> | qi.admin
>
> apache drill (dremiodemo.demo)> *use* dremiodemo.demo;
>
> +--+-+
>
> | * ok * | *  summary  * |
>
> +--+-+
>
> | true | Default schema changed to [dremiodemo.demo] |
>
> +--+-+
>
> 1 row selected (0.098 seconds)
>
> apache drill (dremiodemo.demo)> *use* dremiodemo.demo;
>
> +--+-+
>
> | * ok * | *  summary  * |
>
> +--+-+
>
> | true | Default schema changed to [dremiodemo.demo] |
>
> +--+-+
>
> 1 row selected (0.121 seconds)
>
> apache drill (dremiodemo.demo)> show *tables*;
>
> +-++
>
> | * TABLE_SCHEMA  * | *TABLE_NAME* |
>
> +-++
>
> | dremiodemo.demo | topips|
>
> | dremiodemo.demo | weather|
>
> +-++
>
> 2 rows selected (0.25 seconds)
>
> apache drill (dremiodemo.demo)> *select* * *from* weather;
>
> Error: DATA_READ ERROR: The JDBC storage plugin failed while trying setup
> the SQL query.
>
>
> sql SELECT *
>
> FROM "DREMIO"."Demo"."weather"
>
> plugin dremiodemo
>
> Fragment 0:0
>
>
> [Error Id: fb821614-d752-4ffb-896a-5a61f7e7cfd5 on
> 1672851h-t2349.noblis.org:31010] (state=,code=0)
>
> apache drill (dremiodemo.demo)>
>
>
> So in this test, I removed the schema=Demo part from the dremiodemo
> profile, and the weather table shows up from "show tables" command, but the
> query select * from weather; returned the same Data_READ ERROR, and the in
> the error message: FROM "DREMIO"."Demo"."weather", the word "DREMRIO" is
> added b

Re: Error: DATA_READ ERROR: The JDBC storage plugin failed while trying setup the SQL query

2020-02-19 Thread Paul Rogers
Hi David,

So I tried to reproduce the problem, but I could not get Dremio to start: it 
consistently crashes when I follow the GitHub community edition instructions. 
[1] Something about "Unable to find injectable based on 
javax.ws.rs.core.SecurityContext."


I don't want to turn our attempt to diagnose a Drill issue into an attempt to 
diagnose my Dremo issue.

What I had planned to do was to start the server, then use the Dremio JDBC 
driver to create a very simple Java program that uses JDBC to connect to Dremio 
and issues the query in question. Then, I planned to muck around with the table 
path: leaving out the schema part, etc. until I got Dremio to accept the query. 
This would tell us what Dremio wants.

Once I had that information, I could then compare that with what Drill is 
sending and figure out how you might adjust your setup to get things to work.

Given that I could not get past the step to get Dremio running, are you 
comfortable enough with Java to run the little experiment outlined above? Once 
you have a SELECT statement that works, we can move on to the next step above: 
working out how to get Drill to issue that statement.

Thanks,
- Paul

[1] https://github.com/dremio/dremio-oss


 

On Tuesday, February 18, 2020, 8:23:23 AM PST, David Du 
 wrote:  
 
 Thanks for your response, from http://localhost:9047/space/Demo, then I run
select * from weather, it works and got data back, then I reconfigured
apache drill plugin:
dremiodemo
{
  "type": "jdbc",
  "driver": "com.dremio.jdbc.Driver",
  "url": "jdbc:dremio:direct=localhost:41010",
  "username": "admin",
  "password": "admin",
  "caseInsensitiveTableNames": true,
  "enabled": true
}

then restarted drill and run commands:

apache drill (dremiodemo.demo)> show *databases*;

+---+

| *              SCHEMA_NAME              * |

+---+

| cp.default                                |

| dfs.default                              |

| dfs.root                                  |

| dfs.tmp                                  |

| dremiodemo.$scratch                      |

| dremiodemo.@admin                        |

| dremiodemo.demo                          |

| dremiodemo.dremio

  dremiodemo.sys                            |

| dremiodemo.sys.cache                      |

| dremiodemo.testspace                      |

| dremiodemo                                |

| information_schema                        |

| qi.admin

apache drill (dremiodemo.demo)> *use* dremiodemo.demo;

+--+-+

| * ok * | *                  summary                  * |

+--+-+

| true | Default schema changed to [dremiodemo.demo] |

+--+-+

1 row selected (0.098 seconds)

apache drill (dremiodemo.demo)> *use* dremiodemo.demo;

+--+-+

| * ok * | *                  summary                  * |

+--+-+

| true | Default schema changed to [dremiodemo.demo] |

+--+-+

1 row selected (0.121 seconds)

apache drill (dremiodemo.demo)> show *tables*;

+-++

| * TABLE_SCHEMA  * | *TABLE_NAME* |

+-++

| dremiodemo.demo | topips    |

| dremiodemo.demo | weather    |

+-++

2 rows selected (0.25 seconds)

apache drill (dremiodemo.demo)> *select* * *from* weather;

Error: DATA_READ ERROR: The JDBC storage plugin failed while trying setup
the SQL query.


sql SELECT *

FROM "DREMIO"."Demo"."weather"

plugin dremiodemo

Fragment 0:0


[Error Id: fb821614-d752-4ffb-896a-5a61f7e7cfd5 on
1672851h-t2349.noblis.org:31010] (state=,code=0)

apache drill (dremiodemo.demo)>


So in this test, I removed the schema=Demo part from the dremiodemo
profile, and the weather table shows up from "show tables" command, but the
query select * from weather; returned the same Data_READ ERROR, and the in
the error message: FROM "DREMIO"."Demo"."weather", the word "DREMRIO" is
added by drill, not me, not sure why, in the sqlline.log file, the error
message is:

org.apache.drill.common.exceptions.UserRemoteException: VALIDATION ERROR:
Schema [[Demo]] is not valid with respect to either root schema or current
default schema.


Current default schema:  dremiodemo.demo


and in server.log file of dremio server log folder, this error message is:

Caused by: org.apache.calcite.sql.validate.SqlValidatorException: Table
'DREMIO.Demo.weather' not found



I also tested qi.admin schema, which I configured for postgres database, it
worked perfectly when I queried some tables with the admin schema, got data
back as expected.


Any clues?

Thanks for your help!

On Fri, Feb 14, 2020 at 5:15 PM Paul Rogers 
wrote:

> Hi David,
>
> Thanks much for the log files. I take it

Re: Error: DATA_READ ERROR: The JDBC storage plugin failed while trying setup the SQL query

2020-02-18 Thread David Du
Thanks for your response, from http://localhost:9047/space/Demo, then I run
select * from weather, it works and got data back, then I reconfigured
apache drill plugin:
dremiodemo
{
  "type": "jdbc",
  "driver": "com.dremio.jdbc.Driver",
  "url": "jdbc:dremio:direct=localhost:41010",
  "username": "admin",
  "password": "admin",
  "caseInsensitiveTableNames": true,
  "enabled": true
}

then restarted drill and run commands:

apache drill (dremiodemo.demo)> show *databases*;

+---+

| *   SCHEMA_NAME   * |

+---+

| cp.default|

| dfs.default   |

| dfs.root  |

| dfs.tmp   |

| dremiodemo.$scratch   |

| dremiodemo.@admin |

| dremiodemo.demo   |

| dremiodemo.dremio

  dremiodemo.sys|

| dremiodemo.sys.cache  |

| dremiodemo.testspace  |

| dremiodemo|

| information_schema|

| qi.admin

apache drill (dremiodemo.demo)> *use* dremiodemo.demo;

+--+-+

| * ok * | *  summary  * |

+--+-+

| true | Default schema changed to [dremiodemo.demo] |

+--+-+

1 row selected (0.098 seconds)

apache drill (dremiodemo.demo)> *use* dremiodemo.demo;

+--+-+

| * ok * | *  summary  * |

+--+-+

| true | Default schema changed to [dremiodemo.demo] |

+--+-+

1 row selected (0.121 seconds)

apache drill (dremiodemo.demo)> show *tables*;

+-++

| * TABLE_SCHEMA  * | *TABLE_NAME* |

+-++

| dremiodemo.demo | topips |

| dremiodemo.demo | weather|

+-++

2 rows selected (0.25 seconds)

apache drill (dremiodemo.demo)> *select* * *from* weather;

Error: DATA_READ ERROR: The JDBC storage plugin failed while trying setup
the SQL query.


sql SELECT *

FROM "DREMIO"."Demo"."weather"

plugin dremiodemo

Fragment 0:0


[Error Id: fb821614-d752-4ffb-896a-5a61f7e7cfd5 on
1672851h-t2349.noblis.org:31010] (state=,code=0)

apache drill (dremiodemo.demo)>


So in this test, I removed the schema=Demo part from the dremiodemo
profile, and the weather table shows up from "show tables" command, but the
query select * from weather; returned the same Data_READ ERROR, and the in
the error message: FROM "DREMIO"."Demo"."weather", the word "DREMRIO" is
added by drill, not me, not sure why, in the sqlline.log file, the error
message is:

org.apache.drill.common.exceptions.UserRemoteException: VALIDATION ERROR:
Schema [[Demo]] is not valid with respect to either root schema or current
default schema.


Current default schema:  dremiodemo.demo


and in server.log file of dremio server log folder, this error message is:

Caused by: org.apache.calcite.sql.validate.SqlValidatorException: Table
'DREMIO.Demo.weather' not found



I also tested qi.admin schema, which I configured for postgres database, it
worked perfectly when I queried some tables with the admin schema, got data
back as expected.


Any clues?

Thanks for your help!

On Fri, Feb 14, 2020 at 5:15 PM Paul Rogers 
wrote:

> Hi David,
>
> Thanks much for the log files. I take it that one log is from Drill, the
> other from Dremio?
>
> What I see is that Drill sends the query off to Dremio via JDBC. This
> tells us that most of your configuration is correct: Drill did establish a
> connection to Dremio. It is just the query that has an issue.
>
>
> The Dremio logs (those with "com.dremio") show that Dremio plans the query
> using its version of Calcite. Dremio then fails because it does not
> recognize the "namespace".
>
> The code in Drill which raises the exception includes the translated SQL
> query; the one that Drill tries to send to Dremio via JDBC. The translated
> query seems to be the one from your e-mail:
>
> SELECT *
>
> FROM "DREMIO"."Demo"."weather"
>
> Your earlier e-mail included your config parameters, including the
> connection string:
>
>  "url": "jdbc:dremio:direct=localhost:41010;schema=Demo",
>
> Dremio's explanation of their connection string is at [1]. The syntax is:
>
> jdbc:dremio:direct=:31010[;schema=]
>
> The above says that Drill is connecting (via the network) to a Dremo
> server running on he same host. All good.
>
> The part that still has me concerned is the "schema=Demo" part.
> Unfortunately, the Dremio page does not explain the "schema" parameter, but
> we can guess that it gives the default namespace for resolvin

Re: Error: DATA_READ ERROR: The JDBC storage plugin failed while trying setup the SQL query

2020-02-14 Thread Paul Rogers
Hi David,

Thanks much for the log files. I take it that one log is from Drill, the other 
from Dremio?

What I see is that Drill sends the query off to Dremio via JDBC. This tells us 
that most of your configuration is correct: Drill did establish a connection to 
Dremio. It is just the query that has an issue.


The Dremio logs (those with "com.dremio") show that Dremio plans the query 
using its version of Calcite. Dremio then fails because it does not recognize 
the "namespace".

The code in Drill which raises the exception includes the translated SQL query; 
the one that Drill tries to send to Dremio via JDBC. The translated query seems 
to be the one from your e-mail:

SELECT *

FROM "DREMIO"."Demo"."weather"

Your earlier e-mail included your config parameters, including the connection 
string:

 "url": "jdbc:dremio:direct=localhost:41010;schema=Demo",

Dremio's explanation of their connection string is at [1]. The syntax is:

jdbc:dremio:direct=:31010[;schema=]

The above says that Drill is connecting (via the network) to a Dremo server 
running on he same host. All good.

The part that still has me concerned is the "schema=Demo" part. Unfortunately, 
the Dremio page does not explain the "schema" parameter, but we can guess that 
it gives the default namespace for resolving tables. That is, if the default 
Schema is "Demo", then I'd expect the valid SQL to be:

SELECT * FROM weather

Let's try an experiment. From Dremio's UI, try selecting a schema (perhaps with 
USE?) and run the full query. Then try running the simpler query. Which worked?

If only the simpler one worked, try changing your config url to omit the schema.

I don't yet understand where the "DREMIO" part of the table name is coming 
from. I rather suspect that is also not needed. To test, try all three various 
using the Dremio UI: DREMIO.Demo.weather, Demo.weather and just weather


Hard to know if this is the problem just from reading logs, but it seems worth 
a shot. Once we see what happens, we can figure out what to try next.


Thanks,
- Paul

[1] https://docs.dremio.com/drivers/dremio-jdbc-driver.html 

On Thursday, February 13, 2020, 6:31:08 AM PST, David Du 
 wrote:  
 
 Thanks for your help, my command is:

apache drill> *select* * *from* dremiodemo.demo.weather;


this gave me error from console:

Error: DATA_READ ERROR: The JDBC storage plugin failed while trying setup
the SQL query.


sql SELECT *

FROM "DREMIO"."Demo"."weather"

plugin dremiodemo

Fragment 0:0


[Error Id: dd01f1ff-c7c8-4f36-996f-5f4ed3839c43 on 172.24.30.68:31010]
(state=,code=0)




But the log file is:



tail -f sqlline.log

2020-02-13 09:23:48,780 [main] WARN  o.a.drill.exec.metrics.DrillMetrics -
Removing old metric since name matched newly registered metric. Metric
name: drill.allocator.root.used

2020-02-13 09:23:48,780 [main] WARN  o.a.drill.exec.metrics.DrillMetrics -
Removing old metric since name matched newly registered metric. Metric
name: drill.allocator.root.peak

2020-02-13 09:23:48,913 [main] INFO  o.a.drill.exec.client.DrillClient -
Foreman drillbit is 172.24.30.68

2020-02-13 09:23:48,913 [main] INFO  o.a.drill.exec.client.DrillClient -
Successfully connected to server 172.24.30.68:31010

2020-02-13 09:24:02,371 [21baa3fc-c178-4227-5d3d-00bf55c59097:foreman]
INFO  o.a.drill.exec.work.foreman.Foreman - Query text for query with id
21baa3fc-c178-4227-5d3d-00bf55c59097 issued by anonymous: show databases

2020-02-13 09:24:04,145 [21baa3fc-c178-4227-5d3d-00bf55c59097:frag:0:0]
INFO  o.a.d.e.w.fragment.FragmentExecutor -
21baa3fc-c178-4227-5d3d-00bf55c59097:0:0: State change requested
AWAITING_ALLOCATION --> RUNNING

2020-02-13 09:24:04,156 [21baa3fc-c178-4227-5d3d-00bf55c59097:frag:0:0]
INFO  o.a.d.e.w.f.FragmentStatusReporter -
21baa3fc-c178-4227-5d3d-00bf55c59097:0:0: State to report: RUNNING

2020-02-13 09:24:04,401 [21baa3fc-c178-4227-5d3d-00bf55c59097:frag:0:0]
INFO  o.a.d.e.c.ClassCompilerSelector - Java compiler policy: DEFAULT,
Debug option: true

2020-02-13 09:24:04,571 [21baa3fc-c178-4227-5d3d-00bf55c59097:frag:0:0]
INFO  o.a.d.e.w.fragment.FragmentExecutor -
21baa3fc-c178-4227-5d3d-00bf55c59097:0:0: State change requested RUNNING
--> FINISHED

2020-02-13 09:24:04,573 [21baa3fc-c178-4227-5d3d-00bf55c59097:frag:0:0]
INFO  o.a.d.e.w.f.FragmentStatusReporter -
21baa3fc-c178-4227-5d3d-00bf55c59097:0:0: State to report: FINISHED

2020-02-13 09:26:39,805 [21baa35f-ef83-15fe-f40b-8ff0415620f2:foreman]
INFO  o.a.drill.exec.work.foreman.Foreman - Query text for query with id
21baa35f-ef83-15fe-f40b-8ff0415620f2 issued by anonymous: select * from
dremiodemo.demo.weather

2020-02-13 09:26:40,308 [21baa35f-ef83-15fe-f40b-8ff0415620f2:frag:0:0]
INFO  o.a.d.e.w.fragment.FragmentExecutor -
21baa35f-ef83-15fe-f40b-8ff0415620f2:0:0: State change requested
AWAITING_ALLOCATION --> RUNNING

2020-02-13 09:26:40,308 [21baa35f-ef83-15fe-f40b-8ff0415620f2:frag:0:0]
INFO  o.a.d.e.w.f.FragmentStatusReporter -
21baa35f-ef83-15fe-f40b-8ff0415620f2:0:0:

Re: Error: DATA_READ ERROR: The JDBC storage plugin failed while trying setup the SQL query

2020-02-14 Thread Charles Givre
Hi David,
A few questions: 
How are you querying Drill?  The queries you are sending in the emails do not 
look syntactically correct to begin with.  I'm referring to the use of 
quotation marks and backticks.  These make a HUGE difference with Drill so it 
is really important to use the correct ones.  It is therefore difficult to 
offer suggestions if we are seeing queries like that.

Can you query other schemata in Dremio?  Do they work?

Are you first executing a USE query?  If so have you tried removing the schema 
and table names?

IE:
USE dremiodemo

Then
SELECT * FROM `demo`

Is your Dremio installation running on the same box as Drill?  Out of mere 
curiosity, what is the use case for querying Dremio via Drill?  
Best,
-- C






> On Feb 14, 2020, at 11:19 AM, David Du  wrote:
> 
> Anybody has any ideas about this issue?
> 
> Thanks
> 
> On Thu, Feb 13, 2020 at 10:05 AM David Du  wrote:
> 
>> I used this command:
>> 
>> *select* * *from* dremiodemo.demo.weather;
>> 
>> 
>> since dremiodemo.demo  is the schema name listed from show
>> databases command.
>> 
>> 
>> But why the drill generated a different query as?:
>> 
>> sql SELECT *
>> 
>> FROM "DREMIO"."Demo"."weather"
>> 
>> plugin dremiodemo
>> 
>> 
>> Why "DREMIO" is added instead of "dremiodemo"?
>> 
>> 
>> Thanks
>> 
>> 
>> 
>> 
>> 
>> 
>> On Thu, Feb 13, 2020 at 9:30 AM David Du  wrote:
>> 
>>> Thanks for your help, my command is:
>>> 
>>> apache drill> *select* * *from* dremiodemo.demo.weather;
>>> 
>>> 
>>> this gave me error from console:
>>> 
>>> Error: DATA_READ ERROR: The JDBC storage plugin failed while trying setup
>>> the SQL query.
>>> 
>>> 
>>> sql SELECT *
>>> 
>>> FROM "DREMIO"."Demo"."weather"
>>> 
>>> plugin dremiodemo
>>> 
>>> Fragment 0:0
>>> 
>>> 
>>> [Error Id: dd01f1ff-c7c8-4f36-996f-5f4ed3839c43 on 172.24.30.68:31010]
>>> (state=,code=0)
>>> 
>>> 
>>> 
>>> 
>>> But the log file is:
>>> 
>>> 
>>> 
>>> tail -f sqlline.log
>>> 
>>> 2020-02-13 09:23:48,780 [main] WARN  o.a.drill.exec.metrics.DrillMetrics
>>> - Removing old metric since name matched newly registered metric. Metric
>>> name: drill.allocator.root.used
>>> 
>>> 2020-02-13 09:23:48,780 [main] WARN  o.a.drill.exec.metrics.DrillMetrics
>>> - Removing old metric since name matched newly registered metric. Metric
>>> name: drill.allocator.root.peak
>>> 
>>> 2020-02-13 09:23:48,913 [main] INFO  o.a.drill.exec.client.DrillClient -
>>> Foreman drillbit is 172.24.30.68
>>> 
>>> 2020-02-13 09:23:48,913 [main] INFO  o.a.drill.exec.client.DrillClient -
>>> Successfully connected to server 172.24.30.68:31010
>>> 
>>> 2020-02-13 09:24:02,371 [21baa3fc-c178-4227-5d3d-00bf55c59097:foreman]
>>> INFO  o.a.drill.exec.work.foreman.Foreman - Query text for query with id
>>> 21baa3fc-c178-4227-5d3d-00bf55c59097 issued by anonymous: show databases
>>> 
>>> 2020-02-13 09:24:04,145 [21baa3fc-c178-4227-5d3d-00bf55c59097:frag:0:0]
>>> INFO  o.a.d.e.w.fragment.FragmentExecutor -
>>> 21baa3fc-c178-4227-5d3d-00bf55c59097:0:0: State change requested
>>> AWAITING_ALLOCATION --> RUNNING
>>> 
>>> 2020-02-13 09:24:04,156 [21baa3fc-c178-4227-5d3d-00bf55c59097:frag:0:0]
>>> INFO  o.a.d.e.w.f.FragmentStatusReporter -
>>> 21baa3fc-c178-4227-5d3d-00bf55c59097:0:0: State to report: RUNNING
>>> 
>>> 2020-02-13 09:24:04,401 [21baa3fc-c178-4227-5d3d-00bf55c59097:frag:0:0]
>>> INFO  o.a.d.e.c.ClassCompilerSelector - Java compiler policy: DEFAULT,
>>> Debug option: true
>>> 
>>> 2020-02-13 09:24:04,571 [21baa3fc-c178-4227-5d3d-00bf55c59097:frag:0:0]
>>> INFO  o.a.d.e.w.fragment.FragmentExecutor -
>>> 21baa3fc-c178-4227-5d3d-00bf55c59097:0:0: State change requested RUNNING
>>> --> FINISHED
>>> 
>>> 2020-02-13 09:24:04,573 [21baa3fc-c178-4227-5d3d-00bf55c59097:frag:0:0]
>>> INFO  o.a.d.e.w.f.FragmentStatusReporter -
>>> 21baa3fc-c178-4227-5d3d-00bf55c59097:0:0: State to report: FINISHED
>>> 
>>> 2020-02-13 09:26:39,805 [21baa35f-ef83-15fe-f40b-8ff0415620f2:foreman]
>>> INFO  o.a.drill.exec.work.foreman.Foreman - Query text for query with id
>>> 21baa35f-ef83-15fe-f40b-8ff0415620f2 issued by anonymous: select * from
>>> dremiodemo.demo.weather
>>> 
>>> 2020-02-13 09:26:40,308 [21baa35f-ef83-15fe-f40b-8ff0415620f2:frag:0:0]
>>> INFO  o.a.d.e.w.fragment.FragmentExecutor -
>>> 21baa35f-ef83-15fe-f40b-8ff0415620f2:0:0: State change requested
>>> AWAITING_ALLOCATION --> RUNNING
>>> 
>>> 2020-02-13 09:26:40,308 [21baa35f-ef83-15fe-f40b-8ff0415620f2:frag:0:0]
>>> INFO  o.a.d.e.w.f.FragmentStatusReporter -
>>> 21baa35f-ef83-15fe-f40b-8ff0415620f2:0:0: State to report: RUNNING
>>> 
>>> 2020-02-13 09:26:40,472 [21baa35f-ef83-15fe-f40b-8ff0415620f2:frag:0:0]
>>> INFO  o.a.d.e.store.jdbc.JdbcRecordReader - User Error Occurred: The JDBC
>>> storage plugin failed while trying setup the SQL query.  (VALIDATION ERROR:
>>> Table 'DREMIO.Demo.weather' not found
>>> 
>>> 
>>> SQL Query SELECT *
>>> 
>>> FROM "DREMIO"."Demo"."weather"
>>> 
>>> startLine 2
>>> 
>>> startColumn 6
>>> 
>>> endLine 2
>>> 
>>> endColumn 13
>>> 
>>> 

Re: Error: DATA_READ ERROR: The JDBC storage plugin failed while trying setup the SQL query

2020-02-14 Thread David Du
Anybody has any ideas about this issue?

Thanks

On Thu, Feb 13, 2020 at 10:05 AM David Du  wrote:

> I used this command:
>
> *select* * *from* dremiodemo.demo.weather;
>
>
> since dremiodemo.demo  is the schema name listed from show
> databases command.
>
>
> But why the drill generated a different query as?:
>
> sql SELECT *
>
> FROM "DREMIO"."Demo"."weather"
>
> plugin dremiodemo
>
>
> Why "DREMIO" is added instead of "dremiodemo"?
>
>
> Thanks
>
>
>
>
>
>
> On Thu, Feb 13, 2020 at 9:30 AM David Du  wrote:
>
>> Thanks for your help, my command is:
>>
>> apache drill> *select* * *from* dremiodemo.demo.weather;
>>
>>
>> this gave me error from console:
>>
>> Error: DATA_READ ERROR: The JDBC storage plugin failed while trying setup
>> the SQL query.
>>
>>
>> sql SELECT *
>>
>> FROM "DREMIO"."Demo"."weather"
>>
>> plugin dremiodemo
>>
>> Fragment 0:0
>>
>>
>> [Error Id: dd01f1ff-c7c8-4f36-996f-5f4ed3839c43 on 172.24.30.68:31010]
>> (state=,code=0)
>>
>>
>>
>>
>> But the log file is:
>>
>>
>>
>> tail -f sqlline.log
>>
>> 2020-02-13 09:23:48,780 [main] WARN  o.a.drill.exec.metrics.DrillMetrics
>> - Removing old metric since name matched newly registered metric. Metric
>> name: drill.allocator.root.used
>>
>> 2020-02-13 09:23:48,780 [main] WARN  o.a.drill.exec.metrics.DrillMetrics
>> - Removing old metric since name matched newly registered metric. Metric
>> name: drill.allocator.root.peak
>>
>> 2020-02-13 09:23:48,913 [main] INFO  o.a.drill.exec.client.DrillClient -
>> Foreman drillbit is 172.24.30.68
>>
>> 2020-02-13 09:23:48,913 [main] INFO  o.a.drill.exec.client.DrillClient -
>> Successfully connected to server 172.24.30.68:31010
>>
>> 2020-02-13 09:24:02,371 [21baa3fc-c178-4227-5d3d-00bf55c59097:foreman]
>> INFO  o.a.drill.exec.work.foreman.Foreman - Query text for query with id
>> 21baa3fc-c178-4227-5d3d-00bf55c59097 issued by anonymous: show databases
>>
>> 2020-02-13 09:24:04,145 [21baa3fc-c178-4227-5d3d-00bf55c59097:frag:0:0]
>> INFO  o.a.d.e.w.fragment.FragmentExecutor -
>> 21baa3fc-c178-4227-5d3d-00bf55c59097:0:0: State change requested
>> AWAITING_ALLOCATION --> RUNNING
>>
>> 2020-02-13 09:24:04,156 [21baa3fc-c178-4227-5d3d-00bf55c59097:frag:0:0]
>> INFO  o.a.d.e.w.f.FragmentStatusReporter -
>> 21baa3fc-c178-4227-5d3d-00bf55c59097:0:0: State to report: RUNNING
>>
>> 2020-02-13 09:24:04,401 [21baa3fc-c178-4227-5d3d-00bf55c59097:frag:0:0]
>> INFO  o.a.d.e.c.ClassCompilerSelector - Java compiler policy: DEFAULT,
>> Debug option: true
>>
>> 2020-02-13 09:24:04,571 [21baa3fc-c178-4227-5d3d-00bf55c59097:frag:0:0]
>> INFO  o.a.d.e.w.fragment.FragmentExecutor -
>> 21baa3fc-c178-4227-5d3d-00bf55c59097:0:0: State change requested RUNNING
>> --> FINISHED
>>
>> 2020-02-13 09:24:04,573 [21baa3fc-c178-4227-5d3d-00bf55c59097:frag:0:0]
>> INFO  o.a.d.e.w.f.FragmentStatusReporter -
>> 21baa3fc-c178-4227-5d3d-00bf55c59097:0:0: State to report: FINISHED
>>
>> 2020-02-13 09:26:39,805 [21baa35f-ef83-15fe-f40b-8ff0415620f2:foreman]
>> INFO  o.a.drill.exec.work.foreman.Foreman - Query text for query with id
>> 21baa35f-ef83-15fe-f40b-8ff0415620f2 issued by anonymous: select * from
>> dremiodemo.demo.weather
>>
>> 2020-02-13 09:26:40,308 [21baa35f-ef83-15fe-f40b-8ff0415620f2:frag:0:0]
>> INFO  o.a.d.e.w.fragment.FragmentExecutor -
>> 21baa35f-ef83-15fe-f40b-8ff0415620f2:0:0: State change requested
>> AWAITING_ALLOCATION --> RUNNING
>>
>> 2020-02-13 09:26:40,308 [21baa35f-ef83-15fe-f40b-8ff0415620f2:frag:0:0]
>> INFO  o.a.d.e.w.f.FragmentStatusReporter -
>> 21baa35f-ef83-15fe-f40b-8ff0415620f2:0:0: State to report: RUNNING
>>
>> 2020-02-13 09:26:40,472 [21baa35f-ef83-15fe-f40b-8ff0415620f2:frag:0:0]
>> INFO  o.a.d.e.store.jdbc.JdbcRecordReader - User Error Occurred: The JDBC
>> storage plugin failed while trying setup the SQL query.  (VALIDATION ERROR:
>> Table 'DREMIO.Demo.weather' not found
>>
>>
>> SQL Query SELECT *
>>
>> FROM "DREMIO"."Demo"."weather"
>>
>> startLine 2
>>
>> startColumn 6
>>
>> endLine 2
>>
>> endColumn 13
>>
>>
>> [Error Id: b7ae16cc-80dc-4950-b7e1-7ccbd9cad7e8 on
>> 1672851h-t2349.noblis.org:41010]
>>
>>
>>   (org.apache.calcite.runtime.CalciteContextException) From line 2,
>> column 6 to line 2, column 13: Table 'DREMIO.Demo.weather' not found
>>
>> sun.reflect.GeneratedConstructorAccessor149.newInstance():-1
>>
>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance():45
>>
>> java.lang.reflect.Constructor.newInstance():423
>>
>> org.apache.calcite.runtime.Resources$ExInstWithCause.ex():463
>>
>> org.apache.calcite.sql.SqlUtil.newContextException():803
>>
>> org.apache.calcite.sql.SqlUtil.newContextException():788
>>
>>
>> org.apache.calcite.sql.validate.SqlValidatorImpl.newValidationError():4470
>>
>> org.apache.calcite.sql.validate.IdentifierNamespace.resolveImpl():104
>>
>> org.apache.calcite.sql.validate.IdentifierNamespace.validateImpl():120
>>
>> org.apache.calcite.sql.validate.AbstractNamespace.validate():84
>>
>>
>> org.apache.calcite.sql.validate.

Re: Error: DATA_READ ERROR: The JDBC storage plugin failed while trying setup the SQL query

2020-02-13 Thread David Du
I used this command:

*select* * *from* dremiodemo.demo.weather;


since dremiodemo.demo  is the schema name listed from show
databases command.


But why the drill generated a different query as?:

sql SELECT *

FROM "DREMIO"."Demo"."weather"

plugin dremiodemo


Why "DREMIO" is added instead of "dremiodemo"?


Thanks






On Thu, Feb 13, 2020 at 9:30 AM David Du  wrote:

> Thanks for your help, my command is:
>
> apache drill> *select* * *from* dremiodemo.demo.weather;
>
>
> this gave me error from console:
>
> Error: DATA_READ ERROR: The JDBC storage plugin failed while trying setup
> the SQL query.
>
>
> sql SELECT *
>
> FROM "DREMIO"."Demo"."weather"
>
> plugin dremiodemo
>
> Fragment 0:0
>
>
> [Error Id: dd01f1ff-c7c8-4f36-996f-5f4ed3839c43 on 172.24.30.68:31010]
> (state=,code=0)
>
>
>
>
> But the log file is:
>
>
>
> tail -f sqlline.log
>
> 2020-02-13 09:23:48,780 [main] WARN  o.a.drill.exec.metrics.DrillMetrics -
> Removing old metric since name matched newly registered metric. Metric
> name: drill.allocator.root.used
>
> 2020-02-13 09:23:48,780 [main] WARN  o.a.drill.exec.metrics.DrillMetrics -
> Removing old metric since name matched newly registered metric. Metric
> name: drill.allocator.root.peak
>
> 2020-02-13 09:23:48,913 [main] INFO  o.a.drill.exec.client.DrillClient -
> Foreman drillbit is 172.24.30.68
>
> 2020-02-13 09:23:48,913 [main] INFO  o.a.drill.exec.client.DrillClient -
> Successfully connected to server 172.24.30.68:31010
>
> 2020-02-13 09:24:02,371 [21baa3fc-c178-4227-5d3d-00bf55c59097:foreman]
> INFO  o.a.drill.exec.work.foreman.Foreman - Query text for query with id
> 21baa3fc-c178-4227-5d3d-00bf55c59097 issued by anonymous: show databases
>
> 2020-02-13 09:24:04,145 [21baa3fc-c178-4227-5d3d-00bf55c59097:frag:0:0]
> INFO  o.a.d.e.w.fragment.FragmentExecutor -
> 21baa3fc-c178-4227-5d3d-00bf55c59097:0:0: State change requested
> AWAITING_ALLOCATION --> RUNNING
>
> 2020-02-13 09:24:04,156 [21baa3fc-c178-4227-5d3d-00bf55c59097:frag:0:0]
> INFO  o.a.d.e.w.f.FragmentStatusReporter -
> 21baa3fc-c178-4227-5d3d-00bf55c59097:0:0: State to report: RUNNING
>
> 2020-02-13 09:24:04,401 [21baa3fc-c178-4227-5d3d-00bf55c59097:frag:0:0]
> INFO  o.a.d.e.c.ClassCompilerSelector - Java compiler policy: DEFAULT,
> Debug option: true
>
> 2020-02-13 09:24:04,571 [21baa3fc-c178-4227-5d3d-00bf55c59097:frag:0:0]
> INFO  o.a.d.e.w.fragment.FragmentExecutor -
> 21baa3fc-c178-4227-5d3d-00bf55c59097:0:0: State change requested RUNNING
> --> FINISHED
>
> 2020-02-13 09:24:04,573 [21baa3fc-c178-4227-5d3d-00bf55c59097:frag:0:0]
> INFO  o.a.d.e.w.f.FragmentStatusReporter -
> 21baa3fc-c178-4227-5d3d-00bf55c59097:0:0: State to report: FINISHED
>
> 2020-02-13 09:26:39,805 [21baa35f-ef83-15fe-f40b-8ff0415620f2:foreman]
> INFO  o.a.drill.exec.work.foreman.Foreman - Query text for query with id
> 21baa35f-ef83-15fe-f40b-8ff0415620f2 issued by anonymous: select * from
> dremiodemo.demo.weather
>
> 2020-02-13 09:26:40,308 [21baa35f-ef83-15fe-f40b-8ff0415620f2:frag:0:0]
> INFO  o.a.d.e.w.fragment.FragmentExecutor -
> 21baa35f-ef83-15fe-f40b-8ff0415620f2:0:0: State change requested
> AWAITING_ALLOCATION --> RUNNING
>
> 2020-02-13 09:26:40,308 [21baa35f-ef83-15fe-f40b-8ff0415620f2:frag:0:0]
> INFO  o.a.d.e.w.f.FragmentStatusReporter -
> 21baa35f-ef83-15fe-f40b-8ff0415620f2:0:0: State to report: RUNNING
>
> 2020-02-13 09:26:40,472 [21baa35f-ef83-15fe-f40b-8ff0415620f2:frag:0:0]
> INFO  o.a.d.e.store.jdbc.JdbcRecordReader - User Error Occurred: The JDBC
> storage plugin failed while trying setup the SQL query.  (VALIDATION ERROR:
> Table 'DREMIO.Demo.weather' not found
>
>
> SQL Query SELECT *
>
> FROM "DREMIO"."Demo"."weather"
>
> startLine 2
>
> startColumn 6
>
> endLine 2
>
> endColumn 13
>
>
> [Error Id: b7ae16cc-80dc-4950-b7e1-7ccbd9cad7e8 on
> 1672851h-t2349.noblis.org:41010]
>
>
>   (org.apache.calcite.runtime.CalciteContextException) From line 2, column
> 6 to line 2, column 13: Table 'DREMIO.Demo.weather' not found
>
> sun.reflect.GeneratedConstructorAccessor149.newInstance():-1
>
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance():45
>
> java.lang.reflect.Constructor.newInstance():423
>
> org.apache.calcite.runtime.Resources$ExInstWithCause.ex():463
>
> org.apache.calcite.sql.SqlUtil.newContextException():803
>
> org.apache.calcite.sql.SqlUtil.newContextException():788
>
>
> org.apache.calcite.sql.validate.SqlValidatorImpl.newValidationError():4470
>
> org.apache.calcite.sql.validate.IdentifierNamespace.resolveImpl():104
>
> org.apache.calcite.sql.validate.IdentifierNamespace.validateImpl():120
>
> org.apache.calcite.sql.validate.AbstractNamespace.validate():84
>
>
> org.apache.calcite.sql.validate.SqlValidatorImpl.validateNamespace():943
>
> org.apache.calcite.sql.validate.SqlValidatorImpl.validateQuery():924
>
> org.apache.calcite.sql.validate.SqlValidatorImpl.validateFrom():2971
>
> org.apache.calcite.sql.validate.SqlValidatorImpl.validateFrom():2956
>
> 

Re: Error: DATA_READ ERROR: The JDBC storage plugin failed while trying setup the SQL query

2020-02-13 Thread David Du
Thanks for your help, my command is:

apache drill> *select* * *from* dremiodemo.demo.weather;


this gave me error from console:

Error: DATA_READ ERROR: The JDBC storage plugin failed while trying setup
the SQL query.


sql SELECT *

FROM "DREMIO"."Demo"."weather"

plugin dremiodemo

Fragment 0:0


[Error Id: dd01f1ff-c7c8-4f36-996f-5f4ed3839c43 on 172.24.30.68:31010]
(state=,code=0)




But the log file is:



tail -f sqlline.log

2020-02-13 09:23:48,780 [main] WARN  o.a.drill.exec.metrics.DrillMetrics -
Removing old metric since name matched newly registered metric. Metric
name: drill.allocator.root.used

2020-02-13 09:23:48,780 [main] WARN  o.a.drill.exec.metrics.DrillMetrics -
Removing old metric since name matched newly registered metric. Metric
name: drill.allocator.root.peak

2020-02-13 09:23:48,913 [main] INFO  o.a.drill.exec.client.DrillClient -
Foreman drillbit is 172.24.30.68

2020-02-13 09:23:48,913 [main] INFO  o.a.drill.exec.client.DrillClient -
Successfully connected to server 172.24.30.68:31010

2020-02-13 09:24:02,371 [21baa3fc-c178-4227-5d3d-00bf55c59097:foreman]
INFO  o.a.drill.exec.work.foreman.Foreman - Query text for query with id
21baa3fc-c178-4227-5d3d-00bf55c59097 issued by anonymous: show databases

2020-02-13 09:24:04,145 [21baa3fc-c178-4227-5d3d-00bf55c59097:frag:0:0]
INFO  o.a.d.e.w.fragment.FragmentExecutor -
21baa3fc-c178-4227-5d3d-00bf55c59097:0:0: State change requested
AWAITING_ALLOCATION --> RUNNING

2020-02-13 09:24:04,156 [21baa3fc-c178-4227-5d3d-00bf55c59097:frag:0:0]
INFO  o.a.d.e.w.f.FragmentStatusReporter -
21baa3fc-c178-4227-5d3d-00bf55c59097:0:0: State to report: RUNNING

2020-02-13 09:24:04,401 [21baa3fc-c178-4227-5d3d-00bf55c59097:frag:0:0]
INFO  o.a.d.e.c.ClassCompilerSelector - Java compiler policy: DEFAULT,
Debug option: true

2020-02-13 09:24:04,571 [21baa3fc-c178-4227-5d3d-00bf55c59097:frag:0:0]
INFO  o.a.d.e.w.fragment.FragmentExecutor -
21baa3fc-c178-4227-5d3d-00bf55c59097:0:0: State change requested RUNNING
--> FINISHED

2020-02-13 09:24:04,573 [21baa3fc-c178-4227-5d3d-00bf55c59097:frag:0:0]
INFO  o.a.d.e.w.f.FragmentStatusReporter -
21baa3fc-c178-4227-5d3d-00bf55c59097:0:0: State to report: FINISHED

2020-02-13 09:26:39,805 [21baa35f-ef83-15fe-f40b-8ff0415620f2:foreman]
INFO  o.a.drill.exec.work.foreman.Foreman - Query text for query with id
21baa35f-ef83-15fe-f40b-8ff0415620f2 issued by anonymous: select * from
dremiodemo.demo.weather

2020-02-13 09:26:40,308 [21baa35f-ef83-15fe-f40b-8ff0415620f2:frag:0:0]
INFO  o.a.d.e.w.fragment.FragmentExecutor -
21baa35f-ef83-15fe-f40b-8ff0415620f2:0:0: State change requested
AWAITING_ALLOCATION --> RUNNING

2020-02-13 09:26:40,308 [21baa35f-ef83-15fe-f40b-8ff0415620f2:frag:0:0]
INFO  o.a.d.e.w.f.FragmentStatusReporter -
21baa35f-ef83-15fe-f40b-8ff0415620f2:0:0: State to report: RUNNING

2020-02-13 09:26:40,472 [21baa35f-ef83-15fe-f40b-8ff0415620f2:frag:0:0]
INFO  o.a.d.e.store.jdbc.JdbcRecordReader - User Error Occurred: The JDBC
storage plugin failed while trying setup the SQL query.  (VALIDATION ERROR:
Table 'DREMIO.Demo.weather' not found


SQL Query SELECT *

FROM "DREMIO"."Demo"."weather"

startLine 2

startColumn 6

endLine 2

endColumn 13


[Error Id: b7ae16cc-80dc-4950-b7e1-7ccbd9cad7e8 on
1672851h-t2349.noblis.org:41010]


  (org.apache.calcite.runtime.CalciteContextException) From line 2, column
6 to line 2, column 13: Table 'DREMIO.Demo.weather' not found

sun.reflect.GeneratedConstructorAccessor149.newInstance():-1

sun.reflect.DelegatingConstructorAccessorImpl.newInstance():45

java.lang.reflect.Constructor.newInstance():423

org.apache.calcite.runtime.Resources$ExInstWithCause.ex():463

org.apache.calcite.sql.SqlUtil.newContextException():803

org.apache.calcite.sql.SqlUtil.newContextException():788


org.apache.calcite.sql.validate.SqlValidatorImpl.newValidationError():4470

org.apache.calcite.sql.validate.IdentifierNamespace.resolveImpl():104

org.apache.calcite.sql.validate.IdentifierNamespace.validateImpl():120

org.apache.calcite.sql.validate.AbstractNamespace.validate():84

org.apache.calcite.sql.validate.SqlValidatorImpl.validateNamespace():943

org.apache.calcite.sql.validate.SqlValidatorImpl.validateQuery():924

org.apache.calcite.sql.validate.SqlValidatorImpl.validateFrom():2971

org.apache.calcite.sql.validate.SqlValidatorImpl.validateFrom():2956

org.apache.calcite.sql.validate.SqlValidatorImpl.validateSelect():3197

org.apache.calcite.sql.validate.SelectNamespace.validateImpl():60

org.apache.calcite.sql.validate.AbstractNamespace.validate():84

org.apache.calcite.sql.validate.SqlValidatorImpl.validateNamespace():943

org.apache.calcite.sql.validate.SqlValidatorImpl.validateQuery():924

org.apache.calcite.sql.SqlSelect.validate():226


org.apache.calcite.sql.validate.SqlValidatorImpl.validateScopedExpression():899

org.apache.calcite.sql.validate.SqlValidatorImpl.validate():609

com.dremio.exec.planner.

Re: Error: DATA_READ ERROR: The JDBC storage plugin failed while trying setup the SQL query

2020-02-12 Thread Paul Rogers
The next step would be to take a look at the log file. Anything interesting 
there? Maybe an error or a stack trace?

Thanks,
- Paul

 

On Wednesday, February 12, 2020, 8:12:19 PM PST, Paul Rogers 
 wrote:  
 
 Going to take a wild guess. Since you configured the "Demo" schema in the JDBC 
driver, you may not need it in the Drill query. Maybe try:

SELECT * FROM dremiodemo.weather;

Thanks,
- Paul

 

    On Wednesday, February 12, 2020, 10:34:35 AM PST, David Du 
 wrote:  
 
 My command is:

*select* * *from* dremiodemo.demo.weather;


there is no quotes, but for some reason, the error message returned with
quotes


Thanks for your help!


    

Re: Error: DATA_READ ERROR: The JDBC storage plugin failed while trying setup the SQL query

2020-02-12 Thread Paul Rogers
Going to take a wild guess. Since you configured the "Demo" schema in the JDBC 
driver, you may not need it in the Drill query. Maybe try:

SELECT * FROM dremiodemo.weather;

Thanks,
- Paul

 

On Wednesday, February 12, 2020, 10:34:35 AM PST, David Du 
 wrote:  
 
 My command is:

*select* * *from* dremiodemo.demo.weather;


there is no quotes, but for some reason, the error message returned with
quotes


Thanks for your help!


  

Re: Error: DATA_READ ERROR: The JDBC storage plugin failed while trying setup the SQL query

2020-02-12 Thread David Du
show *schemas*;

+---+

| *   SCHEMA_NAME   * |

+---+

| cp.default|

| dfs.default   |

| dfs.root  |

| dfs.tmp   |

| dremiodemo.$scratch   |

| dremiodemo.@admin |

| dremiodemo.demo   |

| dremiodemo.dremio

  dremiodemo.information_schema |

| dremiodemo.samples|

| dremiodemo.samples.samples.dremio.com |

| dremiodemo.sys|

| dremiodemo.sys.cache  |

| dremiodemo.testspace  |

| dremiodemo|

| information_schema|

| sys



 *use* dremiodemo.demo;

+--+-+

| * ok * | *  summary  * |

+--+-+

| true | Default schema changed to [dremiodemo.demo] |

+--+-+

1 row selected (0.109 seconds)

apache drill (dremiodemo.demo)> show *tables*;

+-++

| * TABLE_SCHEMA  * | *TABLE_NAME* |

+-++

| dremiodemo.demo | topips |

| dremiodemo.demo | weather|

+-++

2 rows selected (0.229 seconds)



apache drill (dremiodemo.demo)> *describe* weather;

+-+---+-+

| *COLUMN_NAME* | *DATA_TYPE* | *IS_NULLABLE* |

+-+---+-+

| A   | CHARACTER VARYING | YES |

| B   | CHARACTER VARYING | YES |

| C   | CHARACTER VARYING | YES |

| D   | CHARACTER VARYING | YES |

| E   | CHARACTER VARYING | YES |

| F   | CHARACTER VARYING | YES |

| G   | CHARACTER VARYING | YES |

| H   | CHARACTER VARYING | YES |

| I   | CHARACTER VARYING | YES |

| J   | CHARACTER VARYING | YES |

| K   | CHARACTER VARYING | YES |

| L   | CHARACTER VARYING | YES |

+-+---+-+

12 rows selected (0.601 seconds)

apache drill (dremiodemo.demo)> *select* * *from* weather;

Error: DATA_READ ERROR: The JDBC storage plugin failed while trying setup
the SQL query.


sql SELECT *

FROM "DREMIO"."Demo"."weather"

plugin dremiodemo

Fragment 0:0


On Wed, Feb 12, 2020 at 1:35 PM Jaimes, Rafael 
wrote:

> Like Charles recommended, try backticks.
>
> Also:
>
>  From the Drill shell what is the output of 'show schemas;' ?
> After 'use ', what is the output of 'show tables;' ?
>
> On 2/12/20 1:32 PM, Charles Givre wrote:
> > Did you try removing the double quotes?
> > IE:
> > SELECT *
> > FROM dremio.`demo`.`weather`
> >
> >
> >> On Feb 12, 2020, at 1:27 PM, David Du  wrote:
> >>
> >> Hi
> >> 1.  I installed the 4.1.4 community version of dremio, and from its web
> UI,
> >> created Demo workspace, then used the samples csv file Samples."
> >> samples.dremio.com"."SF weather 2018-2019.csv" and saved as weather
> into
> >> the Demo workspace, so when clicked on Demo workspace, on the right side
> >> panel the weather name showed up, the copied path is Demo.weather.
> >> 2. I installed the apache-drill-1.17.0 and dropped the jdbc file:
> >> dremio-jdbc-driver-4.1.4-202001240912140359-a90eb503.jar into the
> >> jars/3rdparty folder and jdbc-driver folder.
> >> 3. Started apache drill with ./drill-embedded command, then went to
> drill
> >> web UI, created storage plugin: dremiodemo:
> >> {
> >>   "type": "jdbc",
> >>   "driver": "com.dremio.jdbc.Driver",
> >>   "url": "jdbc:dremio:direct=localhost:41010;schema=Demo",
> >>   "username": "admin",
> >>   "password": "",
> >>   "caseInsensitiveTableNames": true,
> >>   "enabled": true
> >> }
> >> since apache drill is also using 31010, I changed the dremio jdbc port
> to
> >> 41010 in the conf file.
> >> 4. from drill started session, type show databases;
> >> dremiodemo.demo is listed as one of the schema names,
> >> then:
> >> type select * from dremiodemo.demo.weather;
> >> I got error: Error: DATA_READ ERROR: The JDBC storage plugin failed
> while
> >> trying setup the SQL query.
> >>
> >> sql SELECT *
> >>
> >> FROM "DREMIO"."Demo"."weather"
> >>
> >> plugin dremiodemo
> >>
> >> Fragment 0:0
> >>
> >> in  the Dremio server.log file, it showed erro:
> >> Caused by: org.apache.calcite.sql.validate.SqlValidatorException: Table
> >> 'DREMIO.Demo.weather' not found
> >> Any clues? thanks for help.
> >>
> >> --
> >> 
> >> DISCLAIMER:  This
> >> e-mail, including any attached files,
> >> is confidential, may  be legally
> >> privileged, and is

Re: Error: DATA_READ ERROR: The JDBC storage plugin failed while trying setup the SQL query

2020-02-12 Thread Jaimes, Rafael

Like Charles recommended, try backticks.

Also:

From the Drill shell what is the output of 'show schemas;' ?
After 'use ', what is the output of 'show tables;' ?

On 2/12/20 1:32 PM, Charles Givre wrote:

Did you try removing the double quotes?
IE:
SELECT *
FROM dremio.`demo`.`weather`



On Feb 12, 2020, at 1:27 PM, David Du  wrote:

Hi
1.  I installed the 4.1.4 community version of dremio, and from its web UI,
created Demo workspace, then used the samples csv file Samples."
samples.dremio.com"."SF weather 2018-2019.csv" and saved as weather into
the Demo workspace, so when clicked on Demo workspace, on the right side
panel the weather name showed up, the copied path is Demo.weather.
2. I installed the apache-drill-1.17.0 and dropped the jdbc file:
dremio-jdbc-driver-4.1.4-202001240912140359-a90eb503.jar into the
jars/3rdparty folder and jdbc-driver folder.
3. Started apache drill with ./drill-embedded command, then went to drill
web UI, created storage plugin: dremiodemo:
{
  "type": "jdbc",
  "driver": "com.dremio.jdbc.Driver",
  "url": "jdbc:dremio:direct=localhost:41010;schema=Demo",
  "username": "admin",
  "password": "",
  "caseInsensitiveTableNames": true,
  "enabled": true
}
since apache drill is also using 31010, I changed the dremio jdbc port to
41010 in the conf file.
4. from drill started session, type show databases;
dremiodemo.demo is listed as one of the schema names,
then:
type select * from dremiodemo.demo.weather;
I got error: Error: DATA_READ ERROR: The JDBC storage plugin failed while
trying setup the SQL query.

sql SELECT *

FROM "DREMIO"."Demo"."weather"

plugin dremiodemo

Fragment 0:0

in  the Dremio server.log file, it showed erro:
Caused by: org.apache.calcite.sql.validate.SqlValidatorException: Table
'DREMIO.Demo.weather' not found
Any clues? thanks for help.

--

DISCLAIMER:  This
e-mail, including any attached files,
is confidential, may  be legally
privileged, and is
solely for the intended recipient(s).  If you received

this e-mail in error, please destroy it and notify us
immediately by reply
e-mail.  Any unauthorized
use, dissemination, disclosure, copying or
printing is
strictly prohibited. - BCMC, LLC




smime.p7s
Description: S/MIME Cryptographic Signature


Re: Error: DATA_READ ERROR: The JDBC storage plugin failed while trying setup the SQL query

2020-02-12 Thread David Du
My command is:

*select* * *from* dremiodemo.demo.weather;


there is no quotes, but for some reason, the error message returned with
quotes


Thanks for your help!



On Wed, Feb 12, 2020 at 1:32 PM Charles Givre  wrote:

> Did you try removing the double quotes?
> IE:
> SELECT *
> FROM dremio.`demo`.`weather`
>
>
> > On Feb 12, 2020, at 1:27 PM, David Du  wrote:
> >
> > Hi
> > 1.  I installed the 4.1.4 community version of dremio, and from its web
> UI,
> > created Demo workspace, then used the samples csv file Samples."
> > samples.dremio.com"."SF weather 2018-2019.csv" and saved as weather into
> > the Demo workspace, so when clicked on Demo workspace, on the right side
> > panel the weather name showed up, the copied path is Demo.weather.
> > 2. I installed the apache-drill-1.17.0 and dropped the jdbc file:
> > dremio-jdbc-driver-4.1.4-202001240912140359-a90eb503.jar into the
> > jars/3rdparty folder and jdbc-driver folder.
> > 3. Started apache drill with ./drill-embedded command, then went to drill
> > web UI, created storage plugin: dremiodemo:
> > {
> >  "type": "jdbc",
> >  "driver": "com.dremio.jdbc.Driver",
> >  "url": "jdbc:dremio:direct=localhost:41010;schema=Demo",
> >  "username": "admin",
> >  "password": "",
> >  "caseInsensitiveTableNames": true,
> >  "enabled": true
> > }
> > since apache drill is also using 31010, I changed the dremio jdbc port to
> > 41010 in the conf file.
> > 4. from drill started session, type show databases;
> > dremiodemo.demo is listed as one of the schema names,
> > then:
> > type select * from dremiodemo.demo.weather;
> > I got error: Error: DATA_READ ERROR: The JDBC storage plugin failed while
> > trying setup the SQL query.
> >
> > sql SELECT *
> >
> > FROM "DREMIO"."Demo"."weather"
> >
> > plugin dremiodemo
> >
> > Fragment 0:0
> >
> > in  the Dremio server.log file, it showed erro:
> > Caused by: org.apache.calcite.sql.validate.SqlValidatorException: Table
> > 'DREMIO.Demo.weather' not found
> > Any clues? thanks for help.
> >
> > --
> > 
> > DISCLAIMER:  This
> > e-mail, including any attached files,
> > is confidential, may  be legally
> > privileged, and is
> > solely for the intended recipient(s).  If you received
> >
> > this e-mail in error, please destroy it and notify us
> > immediately by reply
> > e-mail.  Any unauthorized
> > use, dissemination, disclosure, copying or
> > printing is
> > strictly prohibited. - BCMC, LLC
>
>

-- 

DISCLAIMER:  This 
e-mail, including any attached files, 
is confidential, may  be legally 
privileged, and is 
solely for the intended recipient(s).  If you received 

this e-mail in error, please destroy it and notify us 
immediately by reply 
e-mail.  Any unauthorized 
use, dissemination, disclosure, copying or 
printing is 
strictly prohibited. - BCMC, LLC


Re: Error: DATA_READ ERROR: The JDBC storage plugin failed while trying setup the SQL query

2020-02-12 Thread Charles Givre
Did you try removing the double quotes?
IE:
SELECT *
FROM dremio.`demo`.`weather`


> On Feb 12, 2020, at 1:27 PM, David Du  wrote:
> 
> Hi
> 1.  I installed the 4.1.4 community version of dremio, and from its web UI,
> created Demo workspace, then used the samples csv file Samples."
> samples.dremio.com"."SF weather 2018-2019.csv" and saved as weather into
> the Demo workspace, so when clicked on Demo workspace, on the right side
> panel the weather name showed up, the copied path is Demo.weather.
> 2. I installed the apache-drill-1.17.0 and dropped the jdbc file:
> dremio-jdbc-driver-4.1.4-202001240912140359-a90eb503.jar into the
> jars/3rdparty folder and jdbc-driver folder.
> 3. Started apache drill with ./drill-embedded command, then went to drill
> web UI, created storage plugin: dremiodemo:
> {
>  "type": "jdbc",
>  "driver": "com.dremio.jdbc.Driver",
>  "url": "jdbc:dremio:direct=localhost:41010;schema=Demo",
>  "username": "admin",
>  "password": "",
>  "caseInsensitiveTableNames": true,
>  "enabled": true
> }
> since apache drill is also using 31010, I changed the dremio jdbc port to
> 41010 in the conf file.
> 4. from drill started session, type show databases;
> dremiodemo.demo is listed as one of the schema names,
> then:
> type select * from dremiodemo.demo.weather;
> I got error: Error: DATA_READ ERROR: The JDBC storage plugin failed while
> trying setup the SQL query.
> 
> sql SELECT *
> 
> FROM "DREMIO"."Demo"."weather"
> 
> plugin dremiodemo
> 
> Fragment 0:0
> 
> in  the Dremio server.log file, it showed erro:
> Caused by: org.apache.calcite.sql.validate.SqlValidatorException: Table
> 'DREMIO.Demo.weather' not found
> Any clues? thanks for help.
> 
> -- 
> 
> DISCLAIMER:  This 
> e-mail, including any attached files, 
> is confidential, may  be legally 
> privileged, and is 
> solely for the intended recipient(s).  If you received 
> 
> this e-mail in error, please destroy it and notify us 
> immediately by reply 
> e-mail.  Any unauthorized 
> use, dissemination, disclosure, copying or 
> printing is 
> strictly prohibited. - BCMC, LLC