[jira] [Commented] (DRILL-6912) NPE when other drillbit is already running
[
https://issues.apache.org/jira/browse/DRILL-6912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16724760#comment-16724760
]
Aman Sinha commented on DRILL-6912:
---
[~vvysotskyi] Yes, certainly the bug exists as you mentioned and affects both
distributed and embedded. It is up to the release manager to decide whether to
consider this for this release but it is sounding like a blocker. In case you
have a tentative fix, you can contribute that :)
> NPE when other drillbit is already running
> --
>
> Key: DRILL-6912
> URL: https://issues.apache.org/jira/browse/DRILL-6912
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Vitalii Diravka
>Assignee: Boaz Ben-Zvi
>Priority: Critical
>
> If user tries to run the second drillbit process, the following output will
> be obtained:
> {code:java}
> vitalii@vitalii-pc:/tmp/apache-drill-1.15.0$ bin/drill-embedded
> java.lang.NullPointerException
> Apache Drill 1.15.0
> "This isn't your grandfather's SQL."
> sqlline> select * from (values(1));
> No current connection
> sqlline> !q
> {code}
> For 1.14.0 drill version the output was correct (but too long):
> {code:java}
> ./bin/drill-embedded
> Dec 18, 2018 7:58:47 PM org.glassfish.jersey.server.ApplicationHandler
> initialize
> INFO: Initiating Jersey application, version Jersey: 2.8 2014-04-29
> 01:25:26...
> Error: Failure in starting embedded Drillbit: java.net.BindException: Address
> already in use (state=,code=0)
> java.sql.SQLException: Failure in starting embedded Drillbit:
> java.net.BindException: Address already in use
> at
> org.apache.drill.jdbc.impl.DrillConnectionImpl.(DrillConnectionImpl.java:143)
> at
> org.apache.drill.jdbc.impl.DrillJdbc41Factory.newDrillConnection(DrillJdbc41Factory.java:72)
> at
> org.apache.drill.jdbc.impl.DrillFactory.newConnection(DrillFactory.java:68)
> at
> org.apache.calcite.avatica.UnregisteredDriver.connect(UnregisteredDriver.java:138)
> at org.apache.drill.jdbc.Driver.connect(Driver.java:72)
> at sqlline.DatabaseConnection.connect(DatabaseConnection.java:167)
> at sqlline.DatabaseConnection.getConnection(DatabaseConnection.java:213)
> at sqlline.Commands.connect(Commands.java:1083)
> at sqlline.Commands.connect(Commands.java:1015)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:36)
> at sqlline.SqlLine.dispatch(SqlLine.java:742)
> at sqlline.SqlLine.initArgs(SqlLine.java:528)
> at sqlline.SqlLine.begin(SqlLine.java:596)
> at sqlline.SqlLine.start(SqlLine.java:375)
> at sqlline.SqlLine.main(SqlLine.java:268)
> Caused by: java.net.BindException: Address already in use
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
> at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:279)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
> at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:218)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at org.eclipse.jetty.server.Server.doStart(Server.java:337)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at org.apache.drill.exec.server.rest.WebServer.start(WebServer.java:155)
> at org.apache.drill.exec.server.Drillbit.run(Drillbit.java:200)
> at
> org.apache.drill.jdbc.impl.DrillConnectionImpl.(DrillConnectionImpl.java:134)
> ... 18 more
> apache drill 1.14.0
> "just drill it"
> 0: jdbc:drill:zk=local> !q{code}
> Looks like it is fine to have a short message in console about the reason of
> error, similar to:
> {code:java}
> java.sql.SQLException: Failure in starting embedded Drillbit:
> java.net.BindException: Address already in use
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-6735) Enhance the Hash-Join Operator to perform Semi-Join
[
https://issues.apache.org/jira/browse/DRILL-6735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16724722#comment-16724722
]
Bridget Bevens commented on DRILL-6735:
---
Hi [~ben-zvi],
I've updated this page with info about semi-joins:
https://drill.apache.org/docs/sort-based-and-hash-based-memory-constrained-operators/
https://drill.apache.org/docs/sort-based-and-hash-based-memory-constrained-operators/#disabling-the-hash-operators
Please let me know if you see anything that needs to be edited.
Thanks,
Bridget
> Enhance the Hash-Join Operator to perform Semi-Join
> ---
>
> Key: DRILL-6735
> URL: https://issues.apache.org/jira/browse/DRILL-6735
> Project: Apache Drill
> Issue Type: Improvement
> Components: Execution - Relational Operators, Query Planning
> Optimization
>Affects Versions: 1.14.0
>Reporter: Boaz Ben-Zvi
>Assignee: Boaz Ben-Zvi
>Priority: Major
> Labels: doc-complete, ready-to-commit
> Fix For: 1.15.0
>
>
> Currently Drill implements Semi-Join (see DRILL-402) by using a regular join,
> with a DISTINCT operator under the build upstream side to eliminate
> duplicates. Typically a physical plan for the Semi uses a hash-join, with a
> hash-aggr performing the DISTINCT (see example below).
> This effectively builds the same hash table(s) twice - a big waste of
> time and memory.
> +Improvement+: Eliminate the Hash-Aggr from the plan, and notify the
> Hash-Join to perform a Semi-join. The HJ then would just skip the duplicates
> in its hash table(s), thus performing a Semi -Join.
> Example:
> {code}
> select c.c_first_name, c.c_last_name from dfs.`/data/json/s1/customer` c
> where c.c_customer_sk in (select s.ss_customer_sk from
> dfs.`/data/json/s1/store_sales` s) limit 4;
> {code}
> And the result plan (see the HJ at 01-03, and the Hash Agg at 01-05):
> {code}
> 00-00Screen : rowType = RecordType(ANY c_first_name, ANY c_last_name):
> rowcount = 4.0, cumulative cost = {4693752.96 rows, 2.309557672003E7 cpu,
> 0.0 io, 2.1598011392E9 network, 3.589586176005E7 memory}, id = 1320
> 00-01 Project(c_first_name=[$1], c_last_name=[$2]) : rowType =
> RecordType(ANY c_first_name, ANY c_last_name): rowcount = 4.0, cumulative
> cost = {4693752.56 rows, 2.309557632004E7 cpu, 0.0 io, 2.1598011392E9
> network, 3.589586176005E7 memory}, id = 1319
> 00-02Project(c_customer_sk=[$1], c_first_name=[$2], c_last_name=[$3],
> ss_customer_sk=[$0]) : rowType = RecordType(ANY c_customer_sk, ANY
> c_first_name, ANY c_last_name, ANY ss_customer_sk): rowcount = 4.0,
> cumulative cost = {4693748.56 rows, 2.309556832004E7 cpu, 0.0 io,
> 2.1598011392E9 network, 3.589586176005E7 memory}, id = 1318
> 00-03 SelectionVectorRemover : rowType = RecordType(ANY
> ss_customer_sk, ANY c_customer_sk, ANY c_first_name, ANY c_last_name):
> rowcount = 4.0, cumulative cost = {4693744.56 rows, 2.309555232004E7 cpu,
> 0.0 io, 2.1598011392E9 network, 3.589586176005E7 memory}, id = 1317
> 00-04Limit(fetch=[4]) : rowType = RecordType(ANY ss_customer_sk,
> ANY c_customer_sk, ANY c_first_name, ANY c_last_name): rowcount = 4.0,
> cumulative cost = {4693740.56 rows, 2.309554832004E7 cpu, 0.0 io,
> 2.1598011392E9 network, 3.589586176005E7 memory}, id = 1316
> 00-05 UnionExchange : rowType = RecordType(ANY ss_customer_sk,
> ANY c_customer_sk, ANY c_first_name, ANY c_last_name): rowcount = 4.0,
> cumulative cost = {4693736.56 rows, 2.309553232004E7 cpu, 0.0 io,
> 2.1598011392E9 network, 3.589586176005E7 memory}, id = 1315
> 01-01SelectionVectorRemover : rowType = RecordType(ANY
> ss_customer_sk, ANY c_customer_sk, ANY c_first_name, ANY c_last_name):
> rowcount = 4.0, cumulative cost = {4693732.56 rows, 2.309550032004E7 cpu,
> 0.0 io, 2.1597356032E9 network, 3.589586176005E7 memory}, id = 1314
> 01-02 Limit(fetch=[4]) : rowType = RecordType(ANY
> ss_customer_sk, ANY c_customer_sk, ANY c_first_name, ANY c_last_name):
> rowcount = 4.0, cumulative cost = {4693728.56 rows, 2.309549632004E7 cpu,
> 0.0 io, 2.1597356032E9 network, 3.589586176005E7 memory}, id = 1313
> 01-03HashJoin(condition=[=($1, $0)], joinType=[inner]) :
> rowType = RecordType(ANY ss_customer_sk, ANY c_customer_sk, ANY c_first_name,
> ANY c_last_name): rowcount = 90182.8, cumulative cost = {4693724.56 rows,
> 2.309548032004E7 cpu, 0.0 io, 2.1597356032E9 network,
> 3.589586176005E7 memory}, id = 1312
> 01-05 HashAgg(group=[{0}]) : rowType = RecordType(ANY
> ss_customer_sk): rowcount = 18036.56, cumulative cost = {4509140.0 rows,
> 2.182423760005E7 cpu, 0.0 io, 1.4775549952E9 network,
>
[jira] [Updated] (DRILL-6735) Enhance the Hash-Join Operator to perform Semi-Join
[
https://issues.apache.org/jira/browse/DRILL-6735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bridget Bevens updated DRILL-6735:
--
Labels: doc-complete ready-to-commit (was: ready-to-commit)
> Enhance the Hash-Join Operator to perform Semi-Join
> ---
>
> Key: DRILL-6735
> URL: https://issues.apache.org/jira/browse/DRILL-6735
> Project: Apache Drill
> Issue Type: Improvement
> Components: Execution - Relational Operators, Query Planning
> Optimization
>Affects Versions: 1.14.0
>Reporter: Boaz Ben-Zvi
>Assignee: Boaz Ben-Zvi
>Priority: Major
> Labels: doc-complete, ready-to-commit
> Fix For: 1.15.0
>
>
> Currently Drill implements Semi-Join (see DRILL-402) by using a regular join,
> with a DISTINCT operator under the build upstream side to eliminate
> duplicates. Typically a physical plan for the Semi uses a hash-join, with a
> hash-aggr performing the DISTINCT (see example below).
> This effectively builds the same hash table(s) twice - a big waste of
> time and memory.
> +Improvement+: Eliminate the Hash-Aggr from the plan, and notify the
> Hash-Join to perform a Semi-join. The HJ then would just skip the duplicates
> in its hash table(s), thus performing a Semi -Join.
> Example:
> {code}
> select c.c_first_name, c.c_last_name from dfs.`/data/json/s1/customer` c
> where c.c_customer_sk in (select s.ss_customer_sk from
> dfs.`/data/json/s1/store_sales` s) limit 4;
> {code}
> And the result plan (see the HJ at 01-03, and the Hash Agg at 01-05):
> {code}
> 00-00Screen : rowType = RecordType(ANY c_first_name, ANY c_last_name):
> rowcount = 4.0, cumulative cost = {4693752.96 rows, 2.309557672003E7 cpu,
> 0.0 io, 2.1598011392E9 network, 3.589586176005E7 memory}, id = 1320
> 00-01 Project(c_first_name=[$1], c_last_name=[$2]) : rowType =
> RecordType(ANY c_first_name, ANY c_last_name): rowcount = 4.0, cumulative
> cost = {4693752.56 rows, 2.309557632004E7 cpu, 0.0 io, 2.1598011392E9
> network, 3.589586176005E7 memory}, id = 1319
> 00-02Project(c_customer_sk=[$1], c_first_name=[$2], c_last_name=[$3],
> ss_customer_sk=[$0]) : rowType = RecordType(ANY c_customer_sk, ANY
> c_first_name, ANY c_last_name, ANY ss_customer_sk): rowcount = 4.0,
> cumulative cost = {4693748.56 rows, 2.309556832004E7 cpu, 0.0 io,
> 2.1598011392E9 network, 3.589586176005E7 memory}, id = 1318
> 00-03 SelectionVectorRemover : rowType = RecordType(ANY
> ss_customer_sk, ANY c_customer_sk, ANY c_first_name, ANY c_last_name):
> rowcount = 4.0, cumulative cost = {4693744.56 rows, 2.309555232004E7 cpu,
> 0.0 io, 2.1598011392E9 network, 3.589586176005E7 memory}, id = 1317
> 00-04Limit(fetch=[4]) : rowType = RecordType(ANY ss_customer_sk,
> ANY c_customer_sk, ANY c_first_name, ANY c_last_name): rowcount = 4.0,
> cumulative cost = {4693740.56 rows, 2.309554832004E7 cpu, 0.0 io,
> 2.1598011392E9 network, 3.589586176005E7 memory}, id = 1316
> 00-05 UnionExchange : rowType = RecordType(ANY ss_customer_sk,
> ANY c_customer_sk, ANY c_first_name, ANY c_last_name): rowcount = 4.0,
> cumulative cost = {4693736.56 rows, 2.309553232004E7 cpu, 0.0 io,
> 2.1598011392E9 network, 3.589586176005E7 memory}, id = 1315
> 01-01SelectionVectorRemover : rowType = RecordType(ANY
> ss_customer_sk, ANY c_customer_sk, ANY c_first_name, ANY c_last_name):
> rowcount = 4.0, cumulative cost = {4693732.56 rows, 2.309550032004E7 cpu,
> 0.0 io, 2.1597356032E9 network, 3.589586176005E7 memory}, id = 1314
> 01-02 Limit(fetch=[4]) : rowType = RecordType(ANY
> ss_customer_sk, ANY c_customer_sk, ANY c_first_name, ANY c_last_name):
> rowcount = 4.0, cumulative cost = {4693728.56 rows, 2.309549632004E7 cpu,
> 0.0 io, 2.1597356032E9 network, 3.589586176005E7 memory}, id = 1313
> 01-03HashJoin(condition=[=($1, $0)], joinType=[inner]) :
> rowType = RecordType(ANY ss_customer_sk, ANY c_customer_sk, ANY c_first_name,
> ANY c_last_name): rowcount = 90182.8, cumulative cost = {4693724.56 rows,
> 2.309548032004E7 cpu, 0.0 io, 2.1597356032E9 network,
> 3.589586176005E7 memory}, id = 1312
> 01-05 HashAgg(group=[{0}]) : rowType = RecordType(ANY
> ss_customer_sk): rowcount = 18036.56, cumulative cost = {4509140.0 rows,
> 2.182423760005E7 cpu, 0.0 io, 1.4775549952E9 network,
> 3.491878016004E7 memory}, id = 1309
> 01-06Project(ss_customer_sk=[$0]) : rowType =
> RecordType(ANY ss_customer_sk): rowcount = 180365.6, cumulative cost =
> {4328774.4 rows, 2.038131280004E7 cpu, 0.0 io, 1.4775549952E9 network,
> 3.17443456E7 memory}, id = 1308
> 01-07
[jira] [Commented] (DRILL-6912) NPE when other drillbit is already running
[
https://issues.apache.org/jira/browse/DRILL-6912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16724694#comment-16724694
]
Volodymyr Vysotskyi commented on DRILL-6912:
I still think that the problem is in the code part I have pointed in my
comment. In the case when we starting drill in distribution mode, NPE is also
present in {{drillbit.log}}, but for this case workaround with *DRILL_EMBEDDED*
is not acceptable.
> NPE when other drillbit is already running
> --
>
> Key: DRILL-6912
> URL: https://issues.apache.org/jira/browse/DRILL-6912
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Vitalii Diravka
>Assignee: Boaz Ben-Zvi
>Priority: Critical
>
> If user tries to run the second drillbit process, the following output will
> be obtained:
> {code:java}
> vitalii@vitalii-pc:/tmp/apache-drill-1.15.0$ bin/drill-embedded
> java.lang.NullPointerException
> Apache Drill 1.15.0
> "This isn't your grandfather's SQL."
> sqlline> select * from (values(1));
> No current connection
> sqlline> !q
> {code}
> For 1.14.0 drill version the output was correct (but too long):
> {code:java}
> ./bin/drill-embedded
> Dec 18, 2018 7:58:47 PM org.glassfish.jersey.server.ApplicationHandler
> initialize
> INFO: Initiating Jersey application, version Jersey: 2.8 2014-04-29
> 01:25:26...
> Error: Failure in starting embedded Drillbit: java.net.BindException: Address
> already in use (state=,code=0)
> java.sql.SQLException: Failure in starting embedded Drillbit:
> java.net.BindException: Address already in use
> at
> org.apache.drill.jdbc.impl.DrillConnectionImpl.(DrillConnectionImpl.java:143)
> at
> org.apache.drill.jdbc.impl.DrillJdbc41Factory.newDrillConnection(DrillJdbc41Factory.java:72)
> at
> org.apache.drill.jdbc.impl.DrillFactory.newConnection(DrillFactory.java:68)
> at
> org.apache.calcite.avatica.UnregisteredDriver.connect(UnregisteredDriver.java:138)
> at org.apache.drill.jdbc.Driver.connect(Driver.java:72)
> at sqlline.DatabaseConnection.connect(DatabaseConnection.java:167)
> at sqlline.DatabaseConnection.getConnection(DatabaseConnection.java:213)
> at sqlline.Commands.connect(Commands.java:1083)
> at sqlline.Commands.connect(Commands.java:1015)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:36)
> at sqlline.SqlLine.dispatch(SqlLine.java:742)
> at sqlline.SqlLine.initArgs(SqlLine.java:528)
> at sqlline.SqlLine.begin(SqlLine.java:596)
> at sqlline.SqlLine.start(SqlLine.java:375)
> at sqlline.SqlLine.main(SqlLine.java:268)
> Caused by: java.net.BindException: Address already in use
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
> at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:279)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
> at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:218)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at org.eclipse.jetty.server.Server.doStart(Server.java:337)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at org.apache.drill.exec.server.rest.WebServer.start(WebServer.java:155)
> at org.apache.drill.exec.server.Drillbit.run(Drillbit.java:200)
> at
> org.apache.drill.jdbc.impl.DrillConnectionImpl.(DrillConnectionImpl.java:134)
> ... 18 more
> apache drill 1.14.0
> "just drill it"
> 0: jdbc:drill:zk=local> !q{code}
> Looks like it is fine to have a short message in console about the reason of
> error, similar to:
> {code:java}
> java.sql.SQLException: Failure in starting embedded Drillbit:
> java.net.BindException: Address already in use
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (DRILL-5671) Set secure ACLs (Access Control List) for Drill ZK nodes in a secure cluster
[ https://issues.apache.org/jira/browse/DRILL-5671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bridget Bevens updated DRILL-5671: -- Labels: doc-complete ready-to-commit (was: doc-impacting ready-to-commit) > Set secure ACLs (Access Control List) for Drill ZK nodes in a secure cluster > > > Key: DRILL-5671 > URL: https://issues.apache.org/jira/browse/DRILL-5671 > Project: Apache Drill > Issue Type: New Feature > Components: Server >Reporter: Karthikeyan Manivannan >Assignee: Karthikeyan Manivannan >Priority: Major > Labels: doc-complete, ready-to-commit > Fix For: 1.15.0 > > > All Drill ZK nodes, currently, are assigned a default [world:all] ACL i.e. > anyone gets to do CDRWA(create, delete, read, write, admin access). This > means that even on a secure cluster anyone can perform all CRDWA actions on > the znodes. > This should be changed such that: > - In a non-secure cluster, Drill will continue using the current default > [world:all] ACL > - In a secure cluster, all nodes should have an [authid: all] ACL i.e. the > authenticated user that created the znode gets full access. The discovery > znodes i.e. the znodes with the list of Drillbits will have an additional > [world:read] ACL, i.e. the list of Drillbits will be readable by anyone. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DRILL-5671) Set secure ACLs (Access Control List) for Drill ZK nodes in a secure cluster
[ https://issues.apache.org/jira/browse/DRILL-5671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16724686#comment-16724686 ] Bridget Bevens commented on DRILL-5671: --- [~karthikm] and [~shamirwasia], I created/edited content based on your feedback and some steps from Anisha. I've posted the doc here: [https://drill.apache.org/docs/configuring-custom-acls-to-secure-znodes/] Please review and let me know if I need to make any changes. Thanks, Bridget > Set secure ACLs (Access Control List) for Drill ZK nodes in a secure cluster > > > Key: DRILL-5671 > URL: https://issues.apache.org/jira/browse/DRILL-5671 > Project: Apache Drill > Issue Type: New Feature > Components: Server >Reporter: Karthikeyan Manivannan >Assignee: Karthikeyan Manivannan >Priority: Major > Labels: doc-impacting, ready-to-commit > Fix For: 1.15.0 > > > All Drill ZK nodes, currently, are assigned a default [world:all] ACL i.e. > anyone gets to do CDRWA(create, delete, read, write, admin access). This > means that even on a secure cluster anyone can perform all CRDWA actions on > the znodes. > This should be changed such that: > - In a non-secure cluster, Drill will continue using the current default > [world:all] ACL > - In a secure cluster, all nodes should have an [authid: all] ACL i.e. the > authenticated user that created the znode gets full access. The discovery > znodes i.e. the znodes with the list of Drillbits will have an additional > [world:read] ACL, i.e. the list of Drillbits will be readable by anyone. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DRILL-6912) NPE when other drillbit is already running
[
https://issues.apache.org/jira/browse/DRILL-6912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16724656#comment-16724656
]
Aman Sinha commented on DRILL-6912:
---
[~ben-zvi] Thanks, I suppose we should document that env variable (currently,
it is set internally in the drill_embedded script) ? I would think quite a few
people (me included) run sqlline directly in the embedded mode. I am curious
though why [~vitalii]'s command failed since he ran drill_embedded. Let's
wait for his confirmation to see if it was an environment issue.
> NPE when other drillbit is already running
> --
>
> Key: DRILL-6912
> URL: https://issues.apache.org/jira/browse/DRILL-6912
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Vitalii Diravka
>Assignee: Boaz Ben-Zvi
>Priority: Critical
>
> If user tries to run the second drillbit process, the following output will
> be obtained:
> {code:java}
> vitalii@vitalii-pc:/tmp/apache-drill-1.15.0$ bin/drill-embedded
> java.lang.NullPointerException
> Apache Drill 1.15.0
> "This isn't your grandfather's SQL."
> sqlline> select * from (values(1));
> No current connection
> sqlline> !q
> {code}
> For 1.14.0 drill version the output was correct (but too long):
> {code:java}
> ./bin/drill-embedded
> Dec 18, 2018 7:58:47 PM org.glassfish.jersey.server.ApplicationHandler
> initialize
> INFO: Initiating Jersey application, version Jersey: 2.8 2014-04-29
> 01:25:26...
> Error: Failure in starting embedded Drillbit: java.net.BindException: Address
> already in use (state=,code=0)
> java.sql.SQLException: Failure in starting embedded Drillbit:
> java.net.BindException: Address already in use
> at
> org.apache.drill.jdbc.impl.DrillConnectionImpl.(DrillConnectionImpl.java:143)
> at
> org.apache.drill.jdbc.impl.DrillJdbc41Factory.newDrillConnection(DrillJdbc41Factory.java:72)
> at
> org.apache.drill.jdbc.impl.DrillFactory.newConnection(DrillFactory.java:68)
> at
> org.apache.calcite.avatica.UnregisteredDriver.connect(UnregisteredDriver.java:138)
> at org.apache.drill.jdbc.Driver.connect(Driver.java:72)
> at sqlline.DatabaseConnection.connect(DatabaseConnection.java:167)
> at sqlline.DatabaseConnection.getConnection(DatabaseConnection.java:213)
> at sqlline.Commands.connect(Commands.java:1083)
> at sqlline.Commands.connect(Commands.java:1015)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:36)
> at sqlline.SqlLine.dispatch(SqlLine.java:742)
> at sqlline.SqlLine.initArgs(SqlLine.java:528)
> at sqlline.SqlLine.begin(SqlLine.java:596)
> at sqlline.SqlLine.start(SqlLine.java:375)
> at sqlline.SqlLine.main(SqlLine.java:268)
> Caused by: java.net.BindException: Address already in use
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
> at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:279)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
> at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:218)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at org.eclipse.jetty.server.Server.doStart(Server.java:337)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at org.apache.drill.exec.server.rest.WebServer.start(WebServer.java:155)
> at org.apache.drill.exec.server.Drillbit.run(Drillbit.java:200)
> at
> org.apache.drill.jdbc.impl.DrillConnectionImpl.(DrillConnectionImpl.java:134)
> ... 18 more
> apache drill 1.14.0
> "just drill it"
> 0: jdbc:drill:zk=local> !q{code}
> Looks like it is fine to have a short message in console about the reason of
> error, similar to:
> {code:java}
> java.sql.SQLException: Failure in starting embedded Drillbit:
> java.net.BindException: Address already in use
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-6912) NPE when other drillbit is already running
[
https://issues.apache.org/jira/browse/DRILL-6912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16724639#comment-16724639
]
Boaz Ben-Zvi commented on DRILL-6912:
-
[~amansinha100] - the difference is the environment variable *DRILL_EMBEDDED* :
{code:java}
~/test/apache-drill-1.15.0/bin 99 > ./sqlline -u jdbc:drill:zk=local -n admin
--maxWidth=10
java.lang.NullPointerException
Apache Drill 1.15.0-SNAPSHOT
"Let's Drill something more solid than concrete."
sqlline> !q
~/test/apache-drill-1.15.0/bin 100 > export DRILL_EMBEDDED=1
~/test/apache-drill-1.15.0/bin 101 > ./sqlline -u jdbc:drill:zk=local -n admin
--maxWidth=10
Picked up JAVA_TOOL_OPTIONS: -ea
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized
[debugInit.c:750]
~/test/apache-drill-1.15.0/bin 102 >{code}
> NPE when other drillbit is already running
> --
>
> Key: DRILL-6912
> URL: https://issues.apache.org/jira/browse/DRILL-6912
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Vitalii Diravka
>Assignee: Boaz Ben-Zvi
>Priority: Critical
>
> If user tries to run the second drillbit process, the following output will
> be obtained:
> {code:java}
> vitalii@vitalii-pc:/tmp/apache-drill-1.15.0$ bin/drill-embedded
> java.lang.NullPointerException
> Apache Drill 1.15.0
> "This isn't your grandfather's SQL."
> sqlline> select * from (values(1));
> No current connection
> sqlline> !q
> {code}
> For 1.14.0 drill version the output was correct (but too long):
> {code:java}
> ./bin/drill-embedded
> Dec 18, 2018 7:58:47 PM org.glassfish.jersey.server.ApplicationHandler
> initialize
> INFO: Initiating Jersey application, version Jersey: 2.8 2014-04-29
> 01:25:26...
> Error: Failure in starting embedded Drillbit: java.net.BindException: Address
> already in use (state=,code=0)
> java.sql.SQLException: Failure in starting embedded Drillbit:
> java.net.BindException: Address already in use
> at
> org.apache.drill.jdbc.impl.DrillConnectionImpl.(DrillConnectionImpl.java:143)
> at
> org.apache.drill.jdbc.impl.DrillJdbc41Factory.newDrillConnection(DrillJdbc41Factory.java:72)
> at
> org.apache.drill.jdbc.impl.DrillFactory.newConnection(DrillFactory.java:68)
> at
> org.apache.calcite.avatica.UnregisteredDriver.connect(UnregisteredDriver.java:138)
> at org.apache.drill.jdbc.Driver.connect(Driver.java:72)
> at sqlline.DatabaseConnection.connect(DatabaseConnection.java:167)
> at sqlline.DatabaseConnection.getConnection(DatabaseConnection.java:213)
> at sqlline.Commands.connect(Commands.java:1083)
> at sqlline.Commands.connect(Commands.java:1015)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:36)
> at sqlline.SqlLine.dispatch(SqlLine.java:742)
> at sqlline.SqlLine.initArgs(SqlLine.java:528)
> at sqlline.SqlLine.begin(SqlLine.java:596)
> at sqlline.SqlLine.start(SqlLine.java:375)
> at sqlline.SqlLine.main(SqlLine.java:268)
> Caused by: java.net.BindException: Address already in use
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
> at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:279)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
> at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:218)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at org.eclipse.jetty.server.Server.doStart(Server.java:337)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at org.apache.drill.exec.server.rest.WebServer.start(WebServer.java:155)
> at org.apache.drill.exec.server.Drillbit.run(Drillbit.java:200)
> at
> org.apache.drill.jdbc.impl.DrillConnectionImpl.(DrillConnectionImpl.java:134)
> ... 18 more
> apache drill 1.14.0
> "just drill it"
> 0: jdbc:drill:zk=local> !q{code}
> Looks like it is fine to have a short message in console about the reason of
> error, similar to:
> {code:java}
> java.sql.SQLException: Failure in starting embedded Drillbit:
> java.net.BindException: Address already in use
> {code}
--
This message was sent by
[jira] [Commented] (DRILL-6912) NPE when other drillbit is already running
[
https://issues.apache.org/jira/browse/DRILL-6912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16724622#comment-16724622
]
Aman Sinha commented on DRILL-6912:
---
Odd...I do see the same NPE that [~vitalii] reported:
{noformat}
[root@aman1 ~]# which sqlline
/root/apache-drill-1.15.0-src/distribution/target/apache-drill-1.15.0/apache-drill-1.15.0/bin/sqlline
[root@aman1 ~]# sqlline -u jdbc:drill:zk=local -n admin --maxWidth=10
java.lang.NullPointerException
Apache Drill 1.15.0
{noformat}
> NPE when other drillbit is already running
> --
>
> Key: DRILL-6912
> URL: https://issues.apache.org/jira/browse/DRILL-6912
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Vitalii Diravka
>Assignee: Boaz Ben-Zvi
>Priority: Critical
>
> If user tries to run the second drillbit process, the following output will
> be obtained:
> {code:java}
> vitalii@vitalii-pc:/tmp/apache-drill-1.15.0$ bin/drill-embedded
> java.lang.NullPointerException
> Apache Drill 1.15.0
> "This isn't your grandfather's SQL."
> sqlline> select * from (values(1));
> No current connection
> sqlline> !q
> {code}
> For 1.14.0 drill version the output was correct (but too long):
> {code:java}
> ./bin/drill-embedded
> Dec 18, 2018 7:58:47 PM org.glassfish.jersey.server.ApplicationHandler
> initialize
> INFO: Initiating Jersey application, version Jersey: 2.8 2014-04-29
> 01:25:26...
> Error: Failure in starting embedded Drillbit: java.net.BindException: Address
> already in use (state=,code=0)
> java.sql.SQLException: Failure in starting embedded Drillbit:
> java.net.BindException: Address already in use
> at
> org.apache.drill.jdbc.impl.DrillConnectionImpl.(DrillConnectionImpl.java:143)
> at
> org.apache.drill.jdbc.impl.DrillJdbc41Factory.newDrillConnection(DrillJdbc41Factory.java:72)
> at
> org.apache.drill.jdbc.impl.DrillFactory.newConnection(DrillFactory.java:68)
> at
> org.apache.calcite.avatica.UnregisteredDriver.connect(UnregisteredDriver.java:138)
> at org.apache.drill.jdbc.Driver.connect(Driver.java:72)
> at sqlline.DatabaseConnection.connect(DatabaseConnection.java:167)
> at sqlline.DatabaseConnection.getConnection(DatabaseConnection.java:213)
> at sqlline.Commands.connect(Commands.java:1083)
> at sqlline.Commands.connect(Commands.java:1015)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:36)
> at sqlline.SqlLine.dispatch(SqlLine.java:742)
> at sqlline.SqlLine.initArgs(SqlLine.java:528)
> at sqlline.SqlLine.begin(SqlLine.java:596)
> at sqlline.SqlLine.start(SqlLine.java:375)
> at sqlline.SqlLine.main(SqlLine.java:268)
> Caused by: java.net.BindException: Address already in use
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
> at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:279)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
> at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:218)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at org.eclipse.jetty.server.Server.doStart(Server.java:337)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at org.apache.drill.exec.server.rest.WebServer.start(WebServer.java:155)
> at org.apache.drill.exec.server.Drillbit.run(Drillbit.java:200)
> at
> org.apache.drill.jdbc.impl.DrillConnectionImpl.(DrillConnectionImpl.java:134)
> ... 18 more
> apache drill 1.14.0
> "just drill it"
> 0: jdbc:drill:zk=local> !q{code}
> Looks like it is fine to have a short message in console about the reason of
> error, similar to:
> {code:java}
> java.sql.SQLException: Failure in starting embedded Drillbit:
> java.net.BindException: Address already in use
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-6912) NPE when other drillbit is already running
[
https://issues.apache.org/jira/browse/DRILL-6912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16724608#comment-16724608
]
Pritesh Maker commented on DRILL-6912:
--
Based on [~ben-zvi] ' comment it seems to report the issue correctly.
[~vitalii] can you confirm if the test is different in anyway?
cc [~amansinha100]
> NPE when other drillbit is already running
> --
>
> Key: DRILL-6912
> URL: https://issues.apache.org/jira/browse/DRILL-6912
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Vitalii Diravka
>Assignee: Boaz Ben-Zvi
>Priority: Critical
>
> If user tries to run the second drillbit process, the following output will
> be obtained:
> {code:java}
> vitalii@vitalii-pc:/tmp/apache-drill-1.15.0$ bin/drill-embedded
> java.lang.NullPointerException
> Apache Drill 1.15.0
> "This isn't your grandfather's SQL."
> sqlline> select * from (values(1));
> No current connection
> sqlline> !q
> {code}
> For 1.14.0 drill version the output was correct (but too long):
> {code:java}
> ./bin/drill-embedded
> Dec 18, 2018 7:58:47 PM org.glassfish.jersey.server.ApplicationHandler
> initialize
> INFO: Initiating Jersey application, version Jersey: 2.8 2014-04-29
> 01:25:26...
> Error: Failure in starting embedded Drillbit: java.net.BindException: Address
> already in use (state=,code=0)
> java.sql.SQLException: Failure in starting embedded Drillbit:
> java.net.BindException: Address already in use
> at
> org.apache.drill.jdbc.impl.DrillConnectionImpl.(DrillConnectionImpl.java:143)
> at
> org.apache.drill.jdbc.impl.DrillJdbc41Factory.newDrillConnection(DrillJdbc41Factory.java:72)
> at
> org.apache.drill.jdbc.impl.DrillFactory.newConnection(DrillFactory.java:68)
> at
> org.apache.calcite.avatica.UnregisteredDriver.connect(UnregisteredDriver.java:138)
> at org.apache.drill.jdbc.Driver.connect(Driver.java:72)
> at sqlline.DatabaseConnection.connect(DatabaseConnection.java:167)
> at sqlline.DatabaseConnection.getConnection(DatabaseConnection.java:213)
> at sqlline.Commands.connect(Commands.java:1083)
> at sqlline.Commands.connect(Commands.java:1015)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:36)
> at sqlline.SqlLine.dispatch(SqlLine.java:742)
> at sqlline.SqlLine.initArgs(SqlLine.java:528)
> at sqlline.SqlLine.begin(SqlLine.java:596)
> at sqlline.SqlLine.start(SqlLine.java:375)
> at sqlline.SqlLine.main(SqlLine.java:268)
> Caused by: java.net.BindException: Address already in use
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
> at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:279)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
> at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:218)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at org.eclipse.jetty.server.Server.doStart(Server.java:337)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at org.apache.drill.exec.server.rest.WebServer.start(WebServer.java:155)
> at org.apache.drill.exec.server.Drillbit.run(Drillbit.java:200)
> at
> org.apache.drill.jdbc.impl.DrillConnectionImpl.(DrillConnectionImpl.java:134)
> ... 18 more
> apache drill 1.14.0
> "just drill it"
> 0: jdbc:drill:zk=local> !q{code}
> Looks like it is fine to have a short message in console about the reason of
> error, similar to:
> {code:java}
> java.sql.SQLException: Failure in starting embedded Drillbit:
> java.net.BindException: Address already in use
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (DRILL-6912) NPE when other drillbit is already running
[
https://issues.apache.org/jira/browse/DRILL-6912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pritesh Maker reassigned DRILL-6912:
Assignee: Boaz Ben-Zvi
> NPE when other drillbit is already running
> --
>
> Key: DRILL-6912
> URL: https://issues.apache.org/jira/browse/DRILL-6912
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Vitalii Diravka
>Assignee: Boaz Ben-Zvi
>Priority: Critical
>
> If user tries to run the second drillbit process, the following output will
> be obtained:
> {code:java}
> vitalii@vitalii-pc:/tmp/apache-drill-1.15.0$ bin/drill-embedded
> java.lang.NullPointerException
> Apache Drill 1.15.0
> "This isn't your grandfather's SQL."
> sqlline> select * from (values(1));
> No current connection
> sqlline> !q
> {code}
> For 1.14.0 drill version the output was correct (but too long):
> {code:java}
> ./bin/drill-embedded
> Dec 18, 2018 7:58:47 PM org.glassfish.jersey.server.ApplicationHandler
> initialize
> INFO: Initiating Jersey application, version Jersey: 2.8 2014-04-29
> 01:25:26...
> Error: Failure in starting embedded Drillbit: java.net.BindException: Address
> already in use (state=,code=0)
> java.sql.SQLException: Failure in starting embedded Drillbit:
> java.net.BindException: Address already in use
> at
> org.apache.drill.jdbc.impl.DrillConnectionImpl.(DrillConnectionImpl.java:143)
> at
> org.apache.drill.jdbc.impl.DrillJdbc41Factory.newDrillConnection(DrillJdbc41Factory.java:72)
> at
> org.apache.drill.jdbc.impl.DrillFactory.newConnection(DrillFactory.java:68)
> at
> org.apache.calcite.avatica.UnregisteredDriver.connect(UnregisteredDriver.java:138)
> at org.apache.drill.jdbc.Driver.connect(Driver.java:72)
> at sqlline.DatabaseConnection.connect(DatabaseConnection.java:167)
> at sqlline.DatabaseConnection.getConnection(DatabaseConnection.java:213)
> at sqlline.Commands.connect(Commands.java:1083)
> at sqlline.Commands.connect(Commands.java:1015)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:36)
> at sqlline.SqlLine.dispatch(SqlLine.java:742)
> at sqlline.SqlLine.initArgs(SqlLine.java:528)
> at sqlline.SqlLine.begin(SqlLine.java:596)
> at sqlline.SqlLine.start(SqlLine.java:375)
> at sqlline.SqlLine.main(SqlLine.java:268)
> Caused by: java.net.BindException: Address already in use
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
> at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:279)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
> at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:218)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at org.eclipse.jetty.server.Server.doStart(Server.java:337)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at org.apache.drill.exec.server.rest.WebServer.start(WebServer.java:155)
> at org.apache.drill.exec.server.Drillbit.run(Drillbit.java:200)
> at
> org.apache.drill.jdbc.impl.DrillConnectionImpl.(DrillConnectionImpl.java:134)
> ... 18 more
> apache drill 1.14.0
> "just drill it"
> 0: jdbc:drill:zk=local> !q{code}
> Looks like it is fine to have a short message in console about the reason of
> error, similar to:
> {code:java}
> java.sql.SQLException: Failure in starting embedded Drillbit:
> java.net.BindException: Address already in use
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-6913) Excessive error output
[
https://issues.apache.org/jira/browse/DRILL-6913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16724609#comment-16724609
]
Pritesh Maker commented on DRILL-6913:
--
[~vvysotskyi] [~vitalii] is this error coming from Calcite?
> Excessive error output
> --
>
> Key: DRILL-6913
> URL: https://issues.apache.org/jira/browse/DRILL-6913
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Vitalii Diravka
>Assignee: Volodymyr Vysotskyi
>Priority: Minor
>
> There are redundant and duplicate error messages in query outputs in case of
> some mistake in query syntax or in case of any other error from Calcite:
> {code:java}
> 0: jdbc:drill:zk=local> select * from dfs.`tpch/nation.parquet`;
> 19:23:09.335 [23e6d301-9bf4-2d4d-69e4-335a3674fd53:foreman] ERROR
> o.a.calcite.runtime.CalciteException -
> org.apache.calcite.sql.validate.SqlValidatorException: Object
> 'tpch/nation.parquet' not found within 'dfs'
> 19:23:09.336 [23e6d301-9bf4-2d4d-69e4-335a3674fd53:foreman] ERROR
> o.a.calcite.runtime.CalciteException -
> org.apache.calcite.runtime.CalciteContextException: From line 1, column 15 to
> line 1, column 17: Object 'tpch/nation.parquet' not found within 'dfs'
> 19:23:09.411 [23e6d301-9bf4-2d4d-69e4-335a3674fd53:foreman] ERROR
> o.a.calcite.runtime.CalciteException -
> org.apache.calcite.sql.validate.SqlValidatorException: Object
> 'tpch/nation.parquet' not found within 'dfs'
> 19:23:09.411 [23e6d301-9bf4-2d4d-69e4-335a3674fd53:foreman] ERROR
> o.a.calcite.runtime.CalciteException -
> org.apache.calcite.runtime.CalciteContextException: From line 1, column 15 to
> line 1, column 17: Object 'tpch/nation.parquet' not found within 'dfs'
> 19:23:09.432 [Client-1] ERROR o.a.calcite.runtime.CalciteException -
> org.apache.calcite.sql.validate.SqlValidatorException: Object
> 'tpch/nation.parquet' not found within 'dfs'
> 19:23:09.432 [Client-1] ERROR o.a.calcite.runtime.CalciteException -
> org.apache.calcite.runtime.CalciteContextException: From line 1, column 15 to
> line 1, column 17: Object 'tpch/nation.parquet' not found within 'dfs':
> Object 'tpch/nation.parquet' not found within 'dfs'
> Error: VALIDATION ERROR: From line 1, column 15 to line 1, column 17: Object
> 'tpch/nation.parquet' not found within 'dfs'
> [Error Id: e3b6b9f6-1e8c-468f-954f-41b57defcf6a on vitalii-pc:31010]
> (state=,code=0)
> {code}
> {code:java}
> 0: jdbc:drill:zk=local> slect * from cp.`tpch/nation.parquet` limit 1;
> 20:40:27.783 [23e6c0e4-6dd7-2f72-12dc-abdb9f2f7634:foreman] ERROR
> o.a.calcite.runtime.CalciteException -
> org.apache.calcite.runtime.CalciteException: Non-query expression encountered
> in illegal context
> 20:40:27.783 [23e6c0e4-6dd7-2f72-12dc-abdb9f2f7634:foreman] ERROR
> o.a.calcite.runtime.CalciteException -
> org.apache.calcite.runtime.CalciteContextException: From line 1, column 1 to
> line 1, column 5: Non-query expression encountered in illegal context
> 20:40:27.787 [Client-1] ERROR o.a.calcite.runtime.CalciteException -
> org.apache.calcite.runtime.CalciteException: Non-query expression encountered
> in illegal context
> Error: PARSE ERROR: Non-query expression encountered in illegal context
> SQL Query slect * from cp.`tpch/nation.parquet` limit 1
> ^
> [Error Id: c1bf1800-6b70-420b-b95c-907d11889a6f on vitalii-pc:31010]
> (state=,code=0)
> 0: jdbc:drill:zk=local>
> {code}
> Errors from drill code are fine:
> {code}
> 0: jdbc:drill:zk=local> select count(4,5) from cp.`tpch/nation.parquet` limit
> 1;
> Error: SYSTEM ERROR: SchemaChangeException: Failure while materializing
> expression.
> Error in expression at index -1. Error: Missing function implementation:
> [count(INT-REQUIRED, INT-REQUIRED)]. Full expression: --UNKNOWN EXPRESSION--.
> Fragment 0:0
> Please, refer to logs for more information.
> [Error Id: de0abc5a-cda9-4ac7-b99f-58f0ef0c7a67 on vitalii-pc:31010]
> (state=,code=0)
> {code}
> In drill Web UI the output is fine for all above cases.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (DRILL-6913) Excessive error output
[
https://issues.apache.org/jira/browse/DRILL-6913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pritesh Maker reassigned DRILL-6913:
Assignee: Volodymyr Vysotskyi
> Excessive error output
> --
>
> Key: DRILL-6913
> URL: https://issues.apache.org/jira/browse/DRILL-6913
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Vitalii Diravka
>Assignee: Volodymyr Vysotskyi
>Priority: Minor
>
> There are redundant and duplicate error messages in query outputs in case of
> some mistake in query syntax or in case of any other error from Calcite:
> {code:java}
> 0: jdbc:drill:zk=local> select * from dfs.`tpch/nation.parquet`;
> 19:23:09.335 [23e6d301-9bf4-2d4d-69e4-335a3674fd53:foreman] ERROR
> o.a.calcite.runtime.CalciteException -
> org.apache.calcite.sql.validate.SqlValidatorException: Object
> 'tpch/nation.parquet' not found within 'dfs'
> 19:23:09.336 [23e6d301-9bf4-2d4d-69e4-335a3674fd53:foreman] ERROR
> o.a.calcite.runtime.CalciteException -
> org.apache.calcite.runtime.CalciteContextException: From line 1, column 15 to
> line 1, column 17: Object 'tpch/nation.parquet' not found within 'dfs'
> 19:23:09.411 [23e6d301-9bf4-2d4d-69e4-335a3674fd53:foreman] ERROR
> o.a.calcite.runtime.CalciteException -
> org.apache.calcite.sql.validate.SqlValidatorException: Object
> 'tpch/nation.parquet' not found within 'dfs'
> 19:23:09.411 [23e6d301-9bf4-2d4d-69e4-335a3674fd53:foreman] ERROR
> o.a.calcite.runtime.CalciteException -
> org.apache.calcite.runtime.CalciteContextException: From line 1, column 15 to
> line 1, column 17: Object 'tpch/nation.parquet' not found within 'dfs'
> 19:23:09.432 [Client-1] ERROR o.a.calcite.runtime.CalciteException -
> org.apache.calcite.sql.validate.SqlValidatorException: Object
> 'tpch/nation.parquet' not found within 'dfs'
> 19:23:09.432 [Client-1] ERROR o.a.calcite.runtime.CalciteException -
> org.apache.calcite.runtime.CalciteContextException: From line 1, column 15 to
> line 1, column 17: Object 'tpch/nation.parquet' not found within 'dfs':
> Object 'tpch/nation.parquet' not found within 'dfs'
> Error: VALIDATION ERROR: From line 1, column 15 to line 1, column 17: Object
> 'tpch/nation.parquet' not found within 'dfs'
> [Error Id: e3b6b9f6-1e8c-468f-954f-41b57defcf6a on vitalii-pc:31010]
> (state=,code=0)
> {code}
> {code:java}
> 0: jdbc:drill:zk=local> slect * from cp.`tpch/nation.parquet` limit 1;
> 20:40:27.783 [23e6c0e4-6dd7-2f72-12dc-abdb9f2f7634:foreman] ERROR
> o.a.calcite.runtime.CalciteException -
> org.apache.calcite.runtime.CalciteException: Non-query expression encountered
> in illegal context
> 20:40:27.783 [23e6c0e4-6dd7-2f72-12dc-abdb9f2f7634:foreman] ERROR
> o.a.calcite.runtime.CalciteException -
> org.apache.calcite.runtime.CalciteContextException: From line 1, column 1 to
> line 1, column 5: Non-query expression encountered in illegal context
> 20:40:27.787 [Client-1] ERROR o.a.calcite.runtime.CalciteException -
> org.apache.calcite.runtime.CalciteException: Non-query expression encountered
> in illegal context
> Error: PARSE ERROR: Non-query expression encountered in illegal context
> SQL Query slect * from cp.`tpch/nation.parquet` limit 1
> ^
> [Error Id: c1bf1800-6b70-420b-b95c-907d11889a6f on vitalii-pc:31010]
> (state=,code=0)
> 0: jdbc:drill:zk=local>
> {code}
> Errors from drill code are fine:
> {code}
> 0: jdbc:drill:zk=local> select count(4,5) from cp.`tpch/nation.parquet` limit
> 1;
> Error: SYSTEM ERROR: SchemaChangeException: Failure while materializing
> expression.
> Error in expression at index -1. Error: Missing function implementation:
> [count(INT-REQUIRED, INT-REQUIRED)]. Full expression: --UNKNOWN EXPRESSION--.
> Fragment 0:0
> Please, refer to logs for more information.
> [Error Id: de0abc5a-cda9-4ac7-b99f-58f0ef0c7a67 on vitalii-pc:31010]
> (state=,code=0)
> {code}
> In drill Web UI the output is fine for all above cases.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-6912) NPE when other drillbit is already running
[
https://issues.apache.org/jira/browse/DRILL-6912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16724580#comment-16724580
]
Boaz Ben-Zvi commented on DRILL-6912:
-
Just tested with 1.15.0 RC0 and there was no NPE :
{code:java}
~/test/apache-drill-1.15.0 8 > ./bin/drill-embedded
Picked up JAVA_TOOL_OPTIONS: -ea
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized
[debugInit.c:750]
~/test/apache-drill-1.15.0 9 >{code}
> NPE when other drillbit is already running
> --
>
> Key: DRILL-6912
> URL: https://issues.apache.org/jira/browse/DRILL-6912
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Vitalii Diravka
>Priority: Critical
>
> If user tries to run the second drillbit process, the following output will
> be obtained:
> {code:java}
> vitalii@vitalii-pc:/tmp/apache-drill-1.15.0$ bin/drill-embedded
> java.lang.NullPointerException
> Apache Drill 1.15.0
> "This isn't your grandfather's SQL."
> sqlline> select * from (values(1));
> No current connection
> sqlline> !q
> {code}
> For 1.14.0 drill version the output was correct (but too long):
> {code:java}
> ./bin/drill-embedded
> Dec 18, 2018 7:58:47 PM org.glassfish.jersey.server.ApplicationHandler
> initialize
> INFO: Initiating Jersey application, version Jersey: 2.8 2014-04-29
> 01:25:26...
> Error: Failure in starting embedded Drillbit: java.net.BindException: Address
> already in use (state=,code=0)
> java.sql.SQLException: Failure in starting embedded Drillbit:
> java.net.BindException: Address already in use
> at
> org.apache.drill.jdbc.impl.DrillConnectionImpl.(DrillConnectionImpl.java:143)
> at
> org.apache.drill.jdbc.impl.DrillJdbc41Factory.newDrillConnection(DrillJdbc41Factory.java:72)
> at
> org.apache.drill.jdbc.impl.DrillFactory.newConnection(DrillFactory.java:68)
> at
> org.apache.calcite.avatica.UnregisteredDriver.connect(UnregisteredDriver.java:138)
> at org.apache.drill.jdbc.Driver.connect(Driver.java:72)
> at sqlline.DatabaseConnection.connect(DatabaseConnection.java:167)
> at sqlline.DatabaseConnection.getConnection(DatabaseConnection.java:213)
> at sqlline.Commands.connect(Commands.java:1083)
> at sqlline.Commands.connect(Commands.java:1015)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:36)
> at sqlline.SqlLine.dispatch(SqlLine.java:742)
> at sqlline.SqlLine.initArgs(SqlLine.java:528)
> at sqlline.SqlLine.begin(SqlLine.java:596)
> at sqlline.SqlLine.start(SqlLine.java:375)
> at sqlline.SqlLine.main(SqlLine.java:268)
> Caused by: java.net.BindException: Address already in use
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
> at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:279)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
> at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:218)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at org.eclipse.jetty.server.Server.doStart(Server.java:337)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at org.apache.drill.exec.server.rest.WebServer.start(WebServer.java:155)
> at org.apache.drill.exec.server.Drillbit.run(Drillbit.java:200)
> at
> org.apache.drill.jdbc.impl.DrillConnectionImpl.(DrillConnectionImpl.java:134)
> ... 18 more
> apache drill 1.14.0
> "just drill it"
> 0: jdbc:drill:zk=local> !q{code}
> Looks like it is fine to have a short message in console about the reason of
> error, similar to:
> {code:java}
> java.sql.SQLException: Failure in starting embedded Drillbit:
> java.net.BindException: Address already in use
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-6768) Improve to_date, to_time and to_timestamp and corresponding cast functions to handle empty string when `drill.exec.functions.cast_empty_string_to_null` option is enable
[
https://issues.apache.org/jira/browse/DRILL-6768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16724549#comment-16724549
]
Bridget Bevens commented on DRILL-6768:
---
Hi [~KazydubB],
I will add this note to this page:
[https://drill.apache.org/docs/data-type-conversion/]
*NOTE*
_Starting in Drill 1.15, all cast and data type conversion functions return an
empty string ('') as NULL when the
drill.exec.functions.cast_empty_string_to_null option is enabled. Prior to
1.15, casting an empty string to null worked only for numeric types; in Drill
1.15 and later casting an empty string to null works for DATE, TIME, TIMESTAMP,
INTERVAL YEAR, INTERVAL MONTH, and INTERVAL DAY data types. You do not have to
use the CASE statement to cast empty strings to values null._
Also, on this page
[https://drill.apache.org/docs/text-files-csv-tsv-psv/#cast-data]
There is a bullet point that says you can use the CASE statement to cast empty
strings to the values you want.
• How would you write the query now, in Drill 1.15, when the
drill.exec.functions.cast_empty_string_to_null option is enabled?
• Do you still need to use the CASE statement or will Drill implicitly cast
the empty strings to null if you exclude the CASE statement, as follows?
CREATE TABLE test AS SELECT
CAST(COLUMNS[0] AS INTEGER) end AS c1,
CAST(COLUMNS[1] AS VARCHAR(20)) end AS c2,
CAST(COLUMNS[2] AS DOUBLE) end AS c3,
CAST(COLUMNS[3] AS DATE) end AS c4,
CAST(COLUMNS[4] AS VARCHAR(20)) end AS c5
FROM `test.csv`;
I will document this JIRA in the release notes also. Is there any other
information I need to include in the documentation for this JIRA or DRILL-6817?
Thanks,
Bridget
> Improve to_date, to_time and to_timestamp and corresponding cast functions to
> handle empty string when `drill.exec.functions.cast_empty_string_to_null`
> option is enabled
> -
>
> Key: DRILL-6768
> URL: https://issues.apache.org/jira/browse/DRILL-6768
> Project: Apache Drill
> Issue Type: Improvement
>Affects Versions: 1.14.0
>Reporter: Bohdan Kazydub
>Assignee: Bohdan Kazydub
>Priority: Major
> Labels: doc-impacting, ready-to-commit
> Fix For: 1.15.0
>
>
> When `drill.exec.functions.cast_empty_string_to_null` option is enabled
> `to_date`, `to_time` and `to_timestamp` functions while converting string to
> according type in case if null or empty string values are passed will return
> NULL (to avoid CASE clauses which are littering a query and will work in
> accordance with their respective CAST counterparts) for both cases.
>
>
>
> CASTs will be handled in a similar way (uniformly with numeric types):
>
> ||Value to cast||Now||Will be||
> |NULL|NULL|NULL|
> |'' (empty string)|Error in many cases (except numerical types)|NULL|
> CAST empty string to null (in case of enabled option) will be supported by
> DATE, TIME, TIMESTAMP, INTERVAL YEAR, INTERVAL MONTH and INTERVAL DAY
> functions in addition to numeric types.
>
> *For documentation*
> TBA
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (DRILL-6913) Excessive error output
[
https://issues.apache.org/jira/browse/DRILL-6913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arina Ielchiieva updated DRILL-6913:
Affects Version/s: (was: 1.14.0)
1.15.0
> Excessive error output
> --
>
> Key: DRILL-6913
> URL: https://issues.apache.org/jira/browse/DRILL-6913
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Vitalii Diravka
>Priority: Minor
>
> There are redundant and duplicate error messages in query outputs in case of
> some mistake in query syntax or in case of any other error from Calcite:
> {code:java}
> 0: jdbc:drill:zk=local> select * from dfs.`tpch/nation.parquet`;
> 19:23:09.335 [23e6d301-9bf4-2d4d-69e4-335a3674fd53:foreman] ERROR
> o.a.calcite.runtime.CalciteException -
> org.apache.calcite.sql.validate.SqlValidatorException: Object
> 'tpch/nation.parquet' not found within 'dfs'
> 19:23:09.336 [23e6d301-9bf4-2d4d-69e4-335a3674fd53:foreman] ERROR
> o.a.calcite.runtime.CalciteException -
> org.apache.calcite.runtime.CalciteContextException: From line 1, column 15 to
> line 1, column 17: Object 'tpch/nation.parquet' not found within 'dfs'
> 19:23:09.411 [23e6d301-9bf4-2d4d-69e4-335a3674fd53:foreman] ERROR
> o.a.calcite.runtime.CalciteException -
> org.apache.calcite.sql.validate.SqlValidatorException: Object
> 'tpch/nation.parquet' not found within 'dfs'
> 19:23:09.411 [23e6d301-9bf4-2d4d-69e4-335a3674fd53:foreman] ERROR
> o.a.calcite.runtime.CalciteException -
> org.apache.calcite.runtime.CalciteContextException: From line 1, column 15 to
> line 1, column 17: Object 'tpch/nation.parquet' not found within 'dfs'
> 19:23:09.432 [Client-1] ERROR o.a.calcite.runtime.CalciteException -
> org.apache.calcite.sql.validate.SqlValidatorException: Object
> 'tpch/nation.parquet' not found within 'dfs'
> 19:23:09.432 [Client-1] ERROR o.a.calcite.runtime.CalciteException -
> org.apache.calcite.runtime.CalciteContextException: From line 1, column 15 to
> line 1, column 17: Object 'tpch/nation.parquet' not found within 'dfs':
> Object 'tpch/nation.parquet' not found within 'dfs'
> Error: VALIDATION ERROR: From line 1, column 15 to line 1, column 17: Object
> 'tpch/nation.parquet' not found within 'dfs'
> [Error Id: e3b6b9f6-1e8c-468f-954f-41b57defcf6a on vitalii-pc:31010]
> (state=,code=0)
> {code}
> {code:java}
> 0: jdbc:drill:zk=local> slect * from cp.`tpch/nation.parquet` limit 1;
> 20:40:27.783 [23e6c0e4-6dd7-2f72-12dc-abdb9f2f7634:foreman] ERROR
> o.a.calcite.runtime.CalciteException -
> org.apache.calcite.runtime.CalciteException: Non-query expression encountered
> in illegal context
> 20:40:27.783 [23e6c0e4-6dd7-2f72-12dc-abdb9f2f7634:foreman] ERROR
> o.a.calcite.runtime.CalciteException -
> org.apache.calcite.runtime.CalciteContextException: From line 1, column 1 to
> line 1, column 5: Non-query expression encountered in illegal context
> 20:40:27.787 [Client-1] ERROR o.a.calcite.runtime.CalciteException -
> org.apache.calcite.runtime.CalciteException: Non-query expression encountered
> in illegal context
> Error: PARSE ERROR: Non-query expression encountered in illegal context
> SQL Query slect * from cp.`tpch/nation.parquet` limit 1
> ^
> [Error Id: c1bf1800-6b70-420b-b95c-907d11889a6f on vitalii-pc:31010]
> (state=,code=0)
> 0: jdbc:drill:zk=local>
> {code}
> Errors from drill code are fine:
> {code}
> 0: jdbc:drill:zk=local> select count(4,5) from cp.`tpch/nation.parquet` limit
> 1;
> Error: SYSTEM ERROR: SchemaChangeException: Failure while materializing
> expression.
> Error in expression at index -1. Error: Missing function implementation:
> [count(INT-REQUIRED, INT-REQUIRED)]. Full expression: --UNKNOWN EXPRESSION--.
> Fragment 0:0
> Please, refer to logs for more information.
> [Error Id: de0abc5a-cda9-4ac7-b99f-58f0ef0c7a67 on vitalii-pc:31010]
> (state=,code=0)
> {code}
> In drill Web UI the output is fine for all above cases.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (DRILL-6912) NPE when other drillbit is already running
[
https://issues.apache.org/jira/browse/DRILL-6912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arina Ielchiieva updated DRILL-6912:
Affects Version/s: (was: 1.14.0)
1.15.0
> NPE when other drillbit is already running
> --
>
> Key: DRILL-6912
> URL: https://issues.apache.org/jira/browse/DRILL-6912
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Vitalii Diravka
>Priority: Critical
>
> If user tries to run the second drillbit process, the following output will
> be obtained:
> {code:java}
> vitalii@vitalii-pc:/tmp/apache-drill-1.15.0$ bin/drill-embedded
> java.lang.NullPointerException
> Apache Drill 1.15.0
> "This isn't your grandfather's SQL."
> sqlline> select * from (values(1));
> No current connection
> sqlline> !q
> {code}
> For 1.14.0 drill version the output was correct (but too long):
> {code:java}
> ./bin/drill-embedded
> Dec 18, 2018 7:58:47 PM org.glassfish.jersey.server.ApplicationHandler
> initialize
> INFO: Initiating Jersey application, version Jersey: 2.8 2014-04-29
> 01:25:26...
> Error: Failure in starting embedded Drillbit: java.net.BindException: Address
> already in use (state=,code=0)
> java.sql.SQLException: Failure in starting embedded Drillbit:
> java.net.BindException: Address already in use
> at
> org.apache.drill.jdbc.impl.DrillConnectionImpl.(DrillConnectionImpl.java:143)
> at
> org.apache.drill.jdbc.impl.DrillJdbc41Factory.newDrillConnection(DrillJdbc41Factory.java:72)
> at
> org.apache.drill.jdbc.impl.DrillFactory.newConnection(DrillFactory.java:68)
> at
> org.apache.calcite.avatica.UnregisteredDriver.connect(UnregisteredDriver.java:138)
> at org.apache.drill.jdbc.Driver.connect(Driver.java:72)
> at sqlline.DatabaseConnection.connect(DatabaseConnection.java:167)
> at sqlline.DatabaseConnection.getConnection(DatabaseConnection.java:213)
> at sqlline.Commands.connect(Commands.java:1083)
> at sqlline.Commands.connect(Commands.java:1015)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:36)
> at sqlline.SqlLine.dispatch(SqlLine.java:742)
> at sqlline.SqlLine.initArgs(SqlLine.java:528)
> at sqlline.SqlLine.begin(SqlLine.java:596)
> at sqlline.SqlLine.start(SqlLine.java:375)
> at sqlline.SqlLine.main(SqlLine.java:268)
> Caused by: java.net.BindException: Address already in use
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
> at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:279)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
> at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:218)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at org.eclipse.jetty.server.Server.doStart(Server.java:337)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at org.apache.drill.exec.server.rest.WebServer.start(WebServer.java:155)
> at org.apache.drill.exec.server.Drillbit.run(Drillbit.java:200)
> at
> org.apache.drill.jdbc.impl.DrillConnectionImpl.(DrillConnectionImpl.java:134)
> ... 18 more
> apache drill 1.14.0
> "just drill it"
> 0: jdbc:drill:zk=local> !q{code}
> Looks like it is fine to have a short message in console about the reason of
> error, similar to:
> {code:java}
> java.sql.SQLException: Failure in starting embedded Drillbit:
> java.net.BindException: Address already in use
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-6912) NPE when other drillbit is already running
[
https://issues.apache.org/jira/browse/DRILL-6912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16724395#comment-16724395
]
Pritesh Maker commented on DRILL-6912:
--
Yes, it does look like odd and can be improved, but I don't think it's a
blocker. My recommendation would be to fix in 1.16.0
> NPE when other drillbit is already running
> --
>
> Key: DRILL-6912
> URL: https://issues.apache.org/jira/browse/DRILL-6912
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Vitalii Diravka
>Priority: Critical
>
> If user tries to run the second drillbit process, the following output will
> be obtained:
> {code:java}
> vitalii@vitalii-pc:/tmp/apache-drill-1.15.0$ bin/drill-embedded
> java.lang.NullPointerException
> Apache Drill 1.15.0
> "This isn't your grandfather's SQL."
> sqlline> select * from (values(1));
> No current connection
> sqlline> !q
> {code}
> For 1.14.0 drill version the output was correct (but too long):
> {code:java}
> ./bin/drill-embedded
> Dec 18, 2018 7:58:47 PM org.glassfish.jersey.server.ApplicationHandler
> initialize
> INFO: Initiating Jersey application, version Jersey: 2.8 2014-04-29
> 01:25:26...
> Error: Failure in starting embedded Drillbit: java.net.BindException: Address
> already in use (state=,code=0)
> java.sql.SQLException: Failure in starting embedded Drillbit:
> java.net.BindException: Address already in use
> at
> org.apache.drill.jdbc.impl.DrillConnectionImpl.(DrillConnectionImpl.java:143)
> at
> org.apache.drill.jdbc.impl.DrillJdbc41Factory.newDrillConnection(DrillJdbc41Factory.java:72)
> at
> org.apache.drill.jdbc.impl.DrillFactory.newConnection(DrillFactory.java:68)
> at
> org.apache.calcite.avatica.UnregisteredDriver.connect(UnregisteredDriver.java:138)
> at org.apache.drill.jdbc.Driver.connect(Driver.java:72)
> at sqlline.DatabaseConnection.connect(DatabaseConnection.java:167)
> at sqlline.DatabaseConnection.getConnection(DatabaseConnection.java:213)
> at sqlline.Commands.connect(Commands.java:1083)
> at sqlline.Commands.connect(Commands.java:1015)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:36)
> at sqlline.SqlLine.dispatch(SqlLine.java:742)
> at sqlline.SqlLine.initArgs(SqlLine.java:528)
> at sqlline.SqlLine.begin(SqlLine.java:596)
> at sqlline.SqlLine.start(SqlLine.java:375)
> at sqlline.SqlLine.main(SqlLine.java:268)
> Caused by: java.net.BindException: Address already in use
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
> at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:279)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
> at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:218)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at org.eclipse.jetty.server.Server.doStart(Server.java:337)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at org.apache.drill.exec.server.rest.WebServer.start(WebServer.java:155)
> at org.apache.drill.exec.server.Drillbit.run(Drillbit.java:200)
> at
> org.apache.drill.jdbc.impl.DrillConnectionImpl.(DrillConnectionImpl.java:134)
> ... 18 more
> apache drill 1.14.0
> "just drill it"
> 0: jdbc:drill:zk=local> !q{code}
> Looks like it is fine to have a short message in console about the reason of
> error, similar to:
> {code:java}
> java.sql.SQLException: Failure in starting embedded Drillbit:
> java.net.BindException: Address already in use
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-6911) Documentation issue - Hadoop core-site.xml is not supported by Drill to read S3 credentials
[
https://issues.apache.org/jira/browse/DRILL-6911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16724396#comment-16724396
]
Bridget Bevens commented on DRILL-6911:
---
Hi [~denysord88],
I removed the third item from the list; however, should I also remove [this
section|https://drill.apache.org/docs/s3-storage-plugin/#configuring-drill-to-use-aws-iam-roles-for-accessing-s3]
based on what the Note says?
*Note:* When you rename the file, Hadoop support breaks if $HADOOP_HOME was in
the path because Drill pulls in the Drill core-site.xml file instead of the
Hadoop core-site.xml file. In this situation, make the changes in the Hadoop
core-site.xml file. Do not create a core-site.xml file for Drill.
It says to remove the Drill core-site.xml. Should the section be removed or
just say that Hadoop support breaks when you rename the Drill core-site.xml
file if $HADOOP_HOME is in the path?
Thanks,
Bridget
> Documentation issue - Hadoop core-site.xml is not supported by Drill to read
> S3 credentials
> ---
>
> Key: DRILL-6911
> URL: https://issues.apache.org/jira/browse/DRILL-6911
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Denys Ordynskiy
>Assignee: Bridget Bevens
>Priority: Major
> Labels: doc-impacting
> Fix For: 1.16.0
>
>
> In the Drill S3 documentation https://drill.apache.org/docs/s3-storage-plugin/
> Section "Providing AWS Credentials" describing 3 ways to setup AWS S3
> credentials in Drill:
> - storage plugin;
> - Drill-specific core-site.xml;
> - existing S3 configuration for Hadoop.
> Third item is not supported by Drill. Hadoop core-site.xml config file may
> contains S3 credentials, but Drill doesn't read any S3 parameters directly
> from Hadoop config file.
> Third item
> {code:java}
> In a Hadoop environment, you can use the existing S3 configuration for
> Hadoop. The AWS credentials should already be defined. All you need to do is
> configure the S3 storage plugin.
> {code}
> should be removed from the document
> https://drill.apache.org/docs/s3-storage-plugin/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (DRILL-6913) Excessive error output
[
https://issues.apache.org/jira/browse/DRILL-6913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitalii Diravka updated DRILL-6913:
---
Summary: Excessive error output (was: Exchessive error output)
> Excessive error output
> --
>
> Key: DRILL-6913
> URL: https://issues.apache.org/jira/browse/DRILL-6913
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Vitalii Diravka
>Priority: Minor
>
> There are redundant and duplicate error messages in query outputs in case of
> some mistake in query syntax or in case of any other error from Calcite:
> {code:java}
> 0: jdbc:drill:zk=local> select * from dfs.`tpch/nation.parquet`;
> 19:23:09.335 [23e6d301-9bf4-2d4d-69e4-335a3674fd53:foreman] ERROR
> o.a.calcite.runtime.CalciteException -
> org.apache.calcite.sql.validate.SqlValidatorException: Object
> 'tpch/nation.parquet' not found within 'dfs'
> 19:23:09.336 [23e6d301-9bf4-2d4d-69e4-335a3674fd53:foreman] ERROR
> o.a.calcite.runtime.CalciteException -
> org.apache.calcite.runtime.CalciteContextException: From line 1, column 15 to
> line 1, column 17: Object 'tpch/nation.parquet' not found within 'dfs'
> 19:23:09.411 [23e6d301-9bf4-2d4d-69e4-335a3674fd53:foreman] ERROR
> o.a.calcite.runtime.CalciteException -
> org.apache.calcite.sql.validate.SqlValidatorException: Object
> 'tpch/nation.parquet' not found within 'dfs'
> 19:23:09.411 [23e6d301-9bf4-2d4d-69e4-335a3674fd53:foreman] ERROR
> o.a.calcite.runtime.CalciteException -
> org.apache.calcite.runtime.CalciteContextException: From line 1, column 15 to
> line 1, column 17: Object 'tpch/nation.parquet' not found within 'dfs'
> 19:23:09.432 [Client-1] ERROR o.a.calcite.runtime.CalciteException -
> org.apache.calcite.sql.validate.SqlValidatorException: Object
> 'tpch/nation.parquet' not found within 'dfs'
> 19:23:09.432 [Client-1] ERROR o.a.calcite.runtime.CalciteException -
> org.apache.calcite.runtime.CalciteContextException: From line 1, column 15 to
> line 1, column 17: Object 'tpch/nation.parquet' not found within 'dfs':
> Object 'tpch/nation.parquet' not found within 'dfs'
> Error: VALIDATION ERROR: From line 1, column 15 to line 1, column 17: Object
> 'tpch/nation.parquet' not found within 'dfs'
> [Error Id: e3b6b9f6-1e8c-468f-954f-41b57defcf6a on vitalii-pc:31010]
> (state=,code=0)
> {code}
> {code:java}
> 0: jdbc:drill:zk=local> slect * from cp.`tpch/nation.parquet` limit 1;
> 20:40:27.783 [23e6c0e4-6dd7-2f72-12dc-abdb9f2f7634:foreman] ERROR
> o.a.calcite.runtime.CalciteException -
> org.apache.calcite.runtime.CalciteException: Non-query expression encountered
> in illegal context
> 20:40:27.783 [23e6c0e4-6dd7-2f72-12dc-abdb9f2f7634:foreman] ERROR
> o.a.calcite.runtime.CalciteException -
> org.apache.calcite.runtime.CalciteContextException: From line 1, column 1 to
> line 1, column 5: Non-query expression encountered in illegal context
> 20:40:27.787 [Client-1] ERROR o.a.calcite.runtime.CalciteException -
> org.apache.calcite.runtime.CalciteException: Non-query expression encountered
> in illegal context
> Error: PARSE ERROR: Non-query expression encountered in illegal context
> SQL Query slect * from cp.`tpch/nation.parquet` limit 1
> ^
> [Error Id: c1bf1800-6b70-420b-b95c-907d11889a6f on vitalii-pc:31010]
> (state=,code=0)
> 0: jdbc:drill:zk=local>
> {code}
> Errors from drill code are fine:
> {code}
> 0: jdbc:drill:zk=local> select count(4,5) from cp.`tpch/nation.parquet` limit
> 1;
> Error: SYSTEM ERROR: SchemaChangeException: Failure while materializing
> expression.
> Error in expression at index -1. Error: Missing function implementation:
> [count(INT-REQUIRED, INT-REQUIRED)]. Full expression: --UNKNOWN EXPRESSION--.
> Fragment 0:0
> Please, refer to logs for more information.
> [Error Id: de0abc5a-cda9-4ac7-b99f-58f0ef0c7a67 on vitalii-pc:31010]
> (state=,code=0)
> {code}
> In drill Web UI the output is fine for all above cases.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (DRILL-6913) Exchessive error output
Vitalii Diravka created DRILL-6913:
--
Summary: Exchessive error output
Key: DRILL-6913
URL: https://issues.apache.org/jira/browse/DRILL-6913
Project: Apache Drill
Issue Type: Bug
Affects Versions: 1.14.0
Reporter: Vitalii Diravka
There are redundant and duplicate error messages in query outputs in case of
some mistake in query syntax or in case of any other error from Calcite:
{code:java}
0: jdbc:drill:zk=local> select * from dfs.`tpch/nation.parquet`;
19:23:09.335 [23e6d301-9bf4-2d4d-69e4-335a3674fd53:foreman] ERROR
o.a.calcite.runtime.CalciteException -
org.apache.calcite.sql.validate.SqlValidatorException: Object
'tpch/nation.parquet' not found within 'dfs'
19:23:09.336 [23e6d301-9bf4-2d4d-69e4-335a3674fd53:foreman] ERROR
o.a.calcite.runtime.CalciteException -
org.apache.calcite.runtime.CalciteContextException: From line 1, column 15 to
line 1, column 17: Object 'tpch/nation.parquet' not found within 'dfs'
19:23:09.411 [23e6d301-9bf4-2d4d-69e4-335a3674fd53:foreman] ERROR
o.a.calcite.runtime.CalciteException -
org.apache.calcite.sql.validate.SqlValidatorException: Object
'tpch/nation.parquet' not found within 'dfs'
19:23:09.411 [23e6d301-9bf4-2d4d-69e4-335a3674fd53:foreman] ERROR
o.a.calcite.runtime.CalciteException -
org.apache.calcite.runtime.CalciteContextException: From line 1, column 15 to
line 1, column 17: Object 'tpch/nation.parquet' not found within 'dfs'
19:23:09.432 [Client-1] ERROR o.a.calcite.runtime.CalciteException -
org.apache.calcite.sql.validate.SqlValidatorException: Object
'tpch/nation.parquet' not found within 'dfs'
19:23:09.432 [Client-1] ERROR o.a.calcite.runtime.CalciteException -
org.apache.calcite.runtime.CalciteContextException: From line 1, column 15 to
line 1, column 17: Object 'tpch/nation.parquet' not found within 'dfs': Object
'tpch/nation.parquet' not found within 'dfs'
Error: VALIDATION ERROR: From line 1, column 15 to line 1, column 17: Object
'tpch/nation.parquet' not found within 'dfs'
[Error Id: e3b6b9f6-1e8c-468f-954f-41b57defcf6a on vitalii-pc:31010]
(state=,code=0)
{code}
{code:java}
0: jdbc:drill:zk=local> slect * from cp.`tpch/nation.parquet` limit 1;
20:40:27.783 [23e6c0e4-6dd7-2f72-12dc-abdb9f2f7634:foreman] ERROR
o.a.calcite.runtime.CalciteException -
org.apache.calcite.runtime.CalciteException: Non-query expression encountered
in illegal context
20:40:27.783 [23e6c0e4-6dd7-2f72-12dc-abdb9f2f7634:foreman] ERROR
o.a.calcite.runtime.CalciteException -
org.apache.calcite.runtime.CalciteContextException: From line 1, column 1 to
line 1, column 5: Non-query expression encountered in illegal context
20:40:27.787 [Client-1] ERROR o.a.calcite.runtime.CalciteException -
org.apache.calcite.runtime.CalciteException: Non-query expression encountered
in illegal context
Error: PARSE ERROR: Non-query expression encountered in illegal context
SQL Query slect * from cp.`tpch/nation.parquet` limit 1
^
[Error Id: c1bf1800-6b70-420b-b95c-907d11889a6f on vitalii-pc:31010]
(state=,code=0)
0: jdbc:drill:zk=local>
{code}
Errors from drill code are fine:
{code}
0: jdbc:drill:zk=local> select count(4,5) from cp.`tpch/nation.parquet` limit 1;
Error: SYSTEM ERROR: SchemaChangeException: Failure while materializing
expression.
Error in expression at index -1. Error: Missing function implementation:
[count(INT-REQUIRED, INT-REQUIRED)]. Full expression: --UNKNOWN EXPRESSION--.
Fragment 0:0
Please, refer to logs for more information.
[Error Id: de0abc5a-cda9-4ac7-b99f-58f0ef0c7a67 on vitalii-pc:31010]
(state=,code=0)
{code}
In drill Web UI the output is fine for all above cases.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (DRILL-6912) NPE when other drillbit is already running
[
https://issues.apache.org/jira/browse/DRILL-6912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitalii Diravka updated DRILL-6912:
---
Description:
If user tries to run the second drillbit process, the following output will be
obtained:
{code:java}
vitalii@vitalii-pc:/tmp/apache-drill-1.15.0$ bin/drill-embedded
java.lang.NullPointerException
Apache Drill 1.15.0
"This isn't your grandfather's SQL."
sqlline> select * from (values(1));
No current connection
sqlline> !q
{code}
For 1.14.0 drill version the output was correct (but too long):
{code:java}
./bin/drill-embedded
Dec 18, 2018 7:58:47 PM org.glassfish.jersey.server.ApplicationHandler
initialize
INFO: Initiating Jersey application, version Jersey: 2.8 2014-04-29 01:25:26...
Error: Failure in starting embedded Drillbit: java.net.BindException: Address
already in use (state=,code=0)
java.sql.SQLException: Failure in starting embedded Drillbit:
java.net.BindException: Address already in use
at
org.apache.drill.jdbc.impl.DrillConnectionImpl.(DrillConnectionImpl.java:143)
at
org.apache.drill.jdbc.impl.DrillJdbc41Factory.newDrillConnection(DrillJdbc41Factory.java:72)
at org.apache.drill.jdbc.impl.DrillFactory.newConnection(DrillFactory.java:68)
at
org.apache.calcite.avatica.UnregisteredDriver.connect(UnregisteredDriver.java:138)
at org.apache.drill.jdbc.Driver.connect(Driver.java:72)
at sqlline.DatabaseConnection.connect(DatabaseConnection.java:167)
at sqlline.DatabaseConnection.getConnection(DatabaseConnection.java:213)
at sqlline.Commands.connect(Commands.java:1083)
at sqlline.Commands.connect(Commands.java:1015)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:36)
at sqlline.SqlLine.dispatch(SqlLine.java:742)
at sqlline.SqlLine.initArgs(SqlLine.java:528)
at sqlline.SqlLine.begin(SqlLine.java:596)
at sqlline.SqlLine.start(SqlLine.java:375)
at sqlline.SqlLine.main(SqlLine.java:268)
Caused by: java.net.BindException: Address already in use
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:433)
at sun.nio.ch.Net.bind(Net.java:425)
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:279)
at
org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:218)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.server.Server.doStart(Server.java:337)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.apache.drill.exec.server.rest.WebServer.start(WebServer.java:155)
at org.apache.drill.exec.server.Drillbit.run(Drillbit.java:200)
at
org.apache.drill.jdbc.impl.DrillConnectionImpl.(DrillConnectionImpl.java:134)
... 18 more
apache drill 1.14.0
"just drill it"
0: jdbc:drill:zk=local> !q{code}
Looks like it is fine to have a short message in console about the reason of
error, similar to:
{code:java}
java.sql.SQLException: Failure in starting embedded Drillbit:
java.net.BindException: Address already in use
{code}
was:
If user will try to run the second drillbit process, the following output is
obtained:
{code}
vitalii@vitalii-pc:/tmp/apache-drill-1.15.0$ bin/drill-embedded
java.lang.NullPointerException
Apache Drill 1.15.0
"This isn't your grandfather's SQL."
sqlline> select * from (values(1));
No current connection
sqlline> !q
{code}
For 1.14.0 drill version the output was correct (but too long):
{code}
./bin/drill-embedded
Dec 18, 2018 7:58:47 PM org.glassfish.jersey.server.ApplicationHandler
initialize
INFO: Initiating Jersey application, version Jersey: 2.8 2014-04-29 01:25:26...
Error: Failure in starting embedded Drillbit: java.net.BindException: Address
already in use (state=,code=0)
java.sql.SQLException: Failure in starting embedded Drillbit:
java.net.BindException: Address already in use
at
org.apache.drill.jdbc.impl.DrillConnectionImpl.(DrillConnectionImpl.java:143)
at
org.apache.drill.jdbc.impl.DrillJdbc41Factory.newDrillConnection(DrillJdbc41Factory.java:72)
at org.apache.drill.jdbc.impl.DrillFactory.newConnection(DrillFactory.java:68)
at
org.apache.calcite.avatica.UnregisteredDriver.connect(UnregisteredDriver.java:138)
at org.apache.drill.jdbc.Driver.connect(Driver.java:72)
at sqlline.DatabaseConnection.connect(DatabaseConnection.java:167)
at sqlline.DatabaseConnection.getConnection(DatabaseConnection.java:213)
at
[jira] [Commented] (DRILL-6912) NPE when other drillbit is already running
[
https://issues.apache.org/jira/browse/DRILL-6912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16724365#comment-16724365
]
Volodymyr Vysotskyi commented on DRILL-6912:
The NPE is thrown from [this
place|https://github.com/apache/drill/blob/master/exec/java-exec/src/main/java/org/apache/drill/exec/server/Drillbit.java#L308].
The problem is that {{BindException}} exception is thrown in
{{Drillbit.run()}} method before {{gracefulShutdownThread}} variable is
initialized, and it is used in the {{Drillbit.close()}} method.
This code was introduced in DRILL-6039.
> NPE when other drillbit is already running
> --
>
> Key: DRILL-6912
> URL: https://issues.apache.org/jira/browse/DRILL-6912
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Vitalii Diravka
>Priority: Critical
>
> If user will try to run the second drillbit process, the following output is
> obtained:
> {code}
> vitalii@vitalii-pc:/tmp/apache-drill-1.15.0$ bin/drill-embedded
> java.lang.NullPointerException
> Apache Drill 1.15.0
> "This isn't your grandfather's SQL."
> sqlline> select * from (values(1));
> No current connection
> sqlline> !q
> {code}
> For 1.14.0 drill version the output was correct (but too long):
> {code}
> ./bin/drill-embedded
> Dec 18, 2018 7:58:47 PM org.glassfish.jersey.server.ApplicationHandler
> initialize
> INFO: Initiating Jersey application, version Jersey: 2.8 2014-04-29
> 01:25:26...
> Error: Failure in starting embedded Drillbit: java.net.BindException: Address
> already in use (state=,code=0)
> java.sql.SQLException: Failure in starting embedded Drillbit:
> java.net.BindException: Address already in use
> at
> org.apache.drill.jdbc.impl.DrillConnectionImpl.(DrillConnectionImpl.java:143)
> at
> org.apache.drill.jdbc.impl.DrillJdbc41Factory.newDrillConnection(DrillJdbc41Factory.java:72)
> at
> org.apache.drill.jdbc.impl.DrillFactory.newConnection(DrillFactory.java:68)
> at
> org.apache.calcite.avatica.UnregisteredDriver.connect(UnregisteredDriver.java:138)
> at org.apache.drill.jdbc.Driver.connect(Driver.java:72)
> at sqlline.DatabaseConnection.connect(DatabaseConnection.java:167)
> at sqlline.DatabaseConnection.getConnection(DatabaseConnection.java:213)
> at sqlline.Commands.connect(Commands.java:1083)
> at sqlline.Commands.connect(Commands.java:1015)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:36)
> at sqlline.SqlLine.dispatch(SqlLine.java:742)
> at sqlline.SqlLine.initArgs(SqlLine.java:528)
> at sqlline.SqlLine.begin(SqlLine.java:596)
> at sqlline.SqlLine.start(SqlLine.java:375)
> at sqlline.SqlLine.main(SqlLine.java:268)
> Caused by: java.net.BindException: Address already in use
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
> at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:279)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
> at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:218)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at org.eclipse.jetty.server.Server.doStart(Server.java:337)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at org.apache.drill.exec.server.rest.WebServer.start(WebServer.java:155)
> at org.apache.drill.exec.server.Drillbit.run(Drillbit.java:200)
> at
> org.apache.drill.jdbc.impl.DrillConnectionImpl.(DrillConnectionImpl.java:134)
> ... 18 more
> apache drill 1.14.0
> "just drill it"
> 0: jdbc:drill:zk=local> !q{code}
> Looks like it is fine to have a short message in console about the reason of
> error, similar to:
> {code}
> java.sql.SQLException: Failure in starting embedded Drillbit:
> java.net.BindException: Address already in use
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (DRILL-6912) NPE when other drillbit is already running
Vitalii Diravka created DRILL-6912:
--
Summary: NPE when other drillbit is already running
Key: DRILL-6912
URL: https://issues.apache.org/jira/browse/DRILL-6912
Project: Apache Drill
Issue Type: Bug
Affects Versions: 1.14.0
Reporter: Vitalii Diravka
If user will try to run the second drillbit process, the following output is
obtained:
{code}
vitalii@vitalii-pc:/tmp/apache-drill-1.15.0$ bin/drill-embedded
java.lang.NullPointerException
Apache Drill 1.15.0
"This isn't your grandfather's SQL."
sqlline> select * from (values(1));
No current connection
sqlline> !q
{code}
For 1.14.0 drill version the output was correct (but too long):
{code}
./bin/drill-embedded
Dec 18, 2018 7:58:47 PM org.glassfish.jersey.server.ApplicationHandler
initialize
INFO: Initiating Jersey application, version Jersey: 2.8 2014-04-29 01:25:26...
Error: Failure in starting embedded Drillbit: java.net.BindException: Address
already in use (state=,code=0)
java.sql.SQLException: Failure in starting embedded Drillbit:
java.net.BindException: Address already in use
at
org.apache.drill.jdbc.impl.DrillConnectionImpl.(DrillConnectionImpl.java:143)
at
org.apache.drill.jdbc.impl.DrillJdbc41Factory.newDrillConnection(DrillJdbc41Factory.java:72)
at org.apache.drill.jdbc.impl.DrillFactory.newConnection(DrillFactory.java:68)
at
org.apache.calcite.avatica.UnregisteredDriver.connect(UnregisteredDriver.java:138)
at org.apache.drill.jdbc.Driver.connect(Driver.java:72)
at sqlline.DatabaseConnection.connect(DatabaseConnection.java:167)
at sqlline.DatabaseConnection.getConnection(DatabaseConnection.java:213)
at sqlline.Commands.connect(Commands.java:1083)
at sqlline.Commands.connect(Commands.java:1015)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:36)
at sqlline.SqlLine.dispatch(SqlLine.java:742)
at sqlline.SqlLine.initArgs(SqlLine.java:528)
at sqlline.SqlLine.begin(SqlLine.java:596)
at sqlline.SqlLine.start(SqlLine.java:375)
at sqlline.SqlLine.main(SqlLine.java:268)
Caused by: java.net.BindException: Address already in use
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:433)
at sun.nio.ch.Net.bind(Net.java:425)
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:279)
at
org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:218)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.server.Server.doStart(Server.java:337)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.apache.drill.exec.server.rest.WebServer.start(WebServer.java:155)
at org.apache.drill.exec.server.Drillbit.run(Drillbit.java:200)
at
org.apache.drill.jdbc.impl.DrillConnectionImpl.(DrillConnectionImpl.java:134)
... 18 more
apache drill 1.14.0
"just drill it"
0: jdbc:drill:zk=local> !q{code}
Looks like it is fine to have a short message in console about the reason of
error, similar to:
{code}
java.sql.SQLException: Failure in starting embedded Drillbit:
java.net.BindException: Address already in use
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-6662) Access AWS access key ID and secret access key using Credential Provider API for S3 storage plugin
[ https://issues.apache.org/jira/browse/DRILL-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16724177#comment-16724177 ] Denys Ordynskiy commented on DRILL-6662: Successfully tested on Drill storage plugin and Drill core-site.xml > Access AWS access key ID and secret access key using Credential Provider API > for S3 storage plugin > -- > > Key: DRILL-6662 > URL: https://issues.apache.org/jira/browse/DRILL-6662 > Project: Apache Drill > Issue Type: Improvement >Reporter: Bohdan Kazydub >Assignee: Bohdan Kazydub >Priority: Major > Labels: doc-impacting, ready-to-commit > Fix For: 1.15.0 > > > Hadoop provides [CredentialProvider > API|[https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-common/CredentialProviderAPI.html]] > which allows passwords and other sensitive secrets to be stored in an > external provider rather than in configuration files in plaintext. > Currently S3 storage plugin is accessing passwords, namely > 'fs.s3a.access.key' and 'fs.s3a.secret.key', stored in clear text in > Configuration with get() method. To give users an ability to remove clear > text passwords for S3 from configuration files Configuration.getPassword() > method should be used, given they configure > 'hadoop.security.credential.provider.path' property which points to a file > containing encrypted passwords instead of configuring two aforementioned > properties. > By using this approach, credential providers will be checked first and if the > secret is not provided or providers are not configured there will be a > fallback to secrets configured in clear text (unless > 'hadoop.security.credential.clear-text-fallback' is configured to be > "false"), thus making new change backwards-compatible. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DRILL-6910) A filtering column remains in scan when filter pruning happens
[
https://issues.apache.org/jira/browse/DRILL-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16724176#comment-16724176
]
Volodymyr Vysotskyi commented on DRILL-6910:
Currently, project can be pushed into the scan only at LOGICAL planning stage
using {{DrillPushProjectIntoScanRule}}, but filter pruning happens at PHYSICAL
stage, so {{DrillPushProjectIntoScanRule}} cannot be applied after filter is
pruned.
The solution is to add a new rule which may be applied at PHYSICAL stage.
> A filtering column remains in scan when filter pruning happens
> --
>
> Key: DRILL-6910
> URL: https://issues.apache.org/jira/browse/DRILL-6910
> Project: Apache Drill
> Issue Type: Improvement
>Affects Versions: 1.14.0
>Reporter: Anton Gozhiy
>Priority: Major
>
> *Data:*
> {code:sql}
> create table dfs.tmp.`nation` as select * from cp.`tpch/nation.parquet`;
> {code}
> *Query:*
> {code:sql}
> explain plan for select n_nationkey from dfs.tmp.`nation` where n_regionkey <
> 10;
> {code}
> *Expected result:*
> The filtering column (n_regionkey) should not be present in scan operator.
> *Actual result:*
> It remains in scan in spite of filter pruning.
> {noformat}
> 00-00Screen : rowType = RecordType(ANY n_nationkey): rowcount = 25.0,
> cumulative cost = {52.5 rows, 77.5 cpu, 50.0 io, 0.0 network, 0.0 memory}, id
> = 112988
> 00-01 Project(n_nationkey=[$1]) : rowType = RecordType(ANY n_nationkey):
> rowcount = 25.0, cumulative cost = {50.0 rows, 75.0 cpu, 50.0 io, 0.0
> network, 0.0 memory}, id = 112987
> 00-02Scan(table=[[dfs, tmp, nation]], groupscan=[ParquetGroupScan
> [entries=[ReadEntryWithPath [path=maprfs:///tmp/nation]],
> selectionRoot=maprfs:/tmp/nation, numFiles=1, numRowGroups=1,
> usedMetadataFile=false, columns=[`n_regionkey`, `n_nationkey`]]]) : rowType =
> RecordType(ANY n_regionkey, ANY n_nationkey): rowcount = 25.0, cumulative
> cost = {25.0 rows, 50.0 cpu, 50.0 io, 0.0 network, 0.0 memory}, id = 112986
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (DRILL-6910) A filtering column remains in scan when filter pruning happens.
[
https://issues.apache.org/jira/browse/DRILL-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arina Ielchiieva updated DRILL-6910:
Issue Type: Improvement (was: Bug)
> A filtering column remains in scan when filter pruning happens.
> ---
>
> Key: DRILL-6910
> URL: https://issues.apache.org/jira/browse/DRILL-6910
> Project: Apache Drill
> Issue Type: Improvement
>Affects Versions: 1.14.0
>Reporter: Anton Gozhiy
>Priority: Major
>
> *Data:*
> {code:sql}
> create table dfs.tmp.`nation` as select * from cp.`tpch/nation.parquet`;
> {code}
> *Query:*
> {code:sql}
> explain plan for select n_nationkey from dfs.tmp.`nation` where n_regionkey <
> 10;
> {code}
> *Expected result:*
> The filtering column (n_regionkey) should not be present in scan operator.
> *Actual result:*
> It remains in scan in spite of filter pruning.
> {noformat}
> 00-00Screen : rowType = RecordType(ANY n_nationkey): rowcount = 25.0,
> cumulative cost = {52.5 rows, 77.5 cpu, 50.0 io, 0.0 network, 0.0 memory}, id
> = 112988
> 00-01 Project(n_nationkey=[$1]) : rowType = RecordType(ANY n_nationkey):
> rowcount = 25.0, cumulative cost = {50.0 rows, 75.0 cpu, 50.0 io, 0.0
> network, 0.0 memory}, id = 112987
> 00-02Scan(table=[[dfs, tmp, nation]], groupscan=[ParquetGroupScan
> [entries=[ReadEntryWithPath [path=maprfs:///tmp/nation]],
> selectionRoot=maprfs:/tmp/nation, numFiles=1, numRowGroups=1,
> usedMetadataFile=false, columns=[`n_regionkey`, `n_nationkey`]]]) : rowType =
> RecordType(ANY n_regionkey, ANY n_nationkey): rowcount = 25.0, cumulative
> cost = {25.0 rows, 50.0 cpu, 50.0 io, 0.0 network, 0.0 memory}, id = 112986
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-6911) Documentation issue - Hadoop core-site.xml is not supported by Drill to read S3 credentials
[
https://issues.apache.org/jira/browse/DRILL-6911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16724171#comment-16724171
]
Denys Ordynskiy commented on DRILL-6911:
cc [~KazydubB]
> Documentation issue - Hadoop core-site.xml is not supported by Drill to read
> S3 credentials
> ---
>
> Key: DRILL-6911
> URL: https://issues.apache.org/jira/browse/DRILL-6911
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Denys Ordynskiy
>Assignee: Bridget Bevens
>Priority: Major
> Labels: doc-impacting
> Fix For: 1.16.0
>
>
> In the Drill S3 documentation https://drill.apache.org/docs/s3-storage-plugin/
> Section "Providing AWS Credentials" describing 3 ways to setup AWS S3
> credentials in Drill:
> - storage plugin;
> - Drill-specific core-site.xml;
> - existing S3 configuration for Hadoop.
> Third item is not supported by Drill. Hadoop core-site.xml config file may
> contains S3 credentials, but Drill doesn't read any S3 parameters directly
> from Hadoop config file.
> Third item
> {code:java}
> In a Hadoop environment, you can use the existing S3 configuration for
> Hadoop. The AWS credentials should already be defined. All you need to do is
> configure the S3 storage plugin.
> {code}
> should be removed from the document
> https://drill.apache.org/docs/s3-storage-plugin/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (DRILL-6911) Documentation issue - Hadoop core-site.xml is not supported by Drill to read S3 credentials
[
https://issues.apache.org/jira/browse/DRILL-6911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arina Ielchiieva updated DRILL-6911:
Labels: doc-impacting (was: )
> Documentation issue - Hadoop core-site.xml is not supported by Drill to read
> S3 credentials
> ---
>
> Key: DRILL-6911
> URL: https://issues.apache.org/jira/browse/DRILL-6911
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Denys Ordynskiy
>Assignee: Bridget Bevens
>Priority: Major
> Labels: doc-impacting
> Fix For: 1.16.0
>
>
> In the Drill S3 documentation https://drill.apache.org/docs/s3-storage-plugin/
> Section "Providing AWS Credentials" describing 3 ways to setup AWS S3
> credentials in Drill:
> - storage plugin;
> - Drill-specific core-site.xml;
> - existing S3 configuration for Hadoop.
> Third item is not supported by Drill. Hadoop core-site.xml config file may
> contains S3 credentials, but Drill doesn't read any S3 parameters directly
> from Hadoop config file.
> Third item
> {code:java}
> In a Hadoop environment, you can use the existing S3 configuration for
> Hadoop. The AWS credentials should already be defined. All you need to do is
> configure the S3 storage plugin.
> {code}
> should be removed from the document
> https://drill.apache.org/docs/s3-storage-plugin/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (DRILL-6911) Documentation issue - Hadoop core-site.xml is not supported by Drill to read S3 credentials
[
https://issues.apache.org/jira/browse/DRILL-6911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arina Ielchiieva updated DRILL-6911:
Fix Version/s: 1.16.0
> Documentation issue - Hadoop core-site.xml is not supported by Drill to read
> S3 credentials
> ---
>
> Key: DRILL-6911
> URL: https://issues.apache.org/jira/browse/DRILL-6911
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Denys Ordynskiy
>Assignee: Bridget Bevens
>Priority: Major
> Labels: doc-impacting
> Fix For: 1.16.0
>
>
> In the Drill S3 documentation https://drill.apache.org/docs/s3-storage-plugin/
> Section "Providing AWS Credentials" describing 3 ways to setup AWS S3
> credentials in Drill:
> - storage plugin;
> - Drill-specific core-site.xml;
> - existing S3 configuration for Hadoop.
> Third item is not supported by Drill. Hadoop core-site.xml config file may
> contains S3 credentials, but Drill doesn't read any S3 parameters directly
> from Hadoop config file.
> Third item
> {code:java}
> In a Hadoop environment, you can use the existing S3 configuration for
> Hadoop. The AWS credentials should already be defined. All you need to do is
> configure the S3 storage plugin.
> {code}
> should be removed from the document
> https://drill.apache.org/docs/s3-storage-plugin/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (DRILL-6910) A filtering column remains in scan when filter pruning happens
[
https://issues.apache.org/jira/browse/DRILL-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arina Ielchiieva updated DRILL-6910:
Summary: A filtering column remains in scan when filter pruning happens
(was: A filtering column remains in scan when filter pruning happens.)
> A filtering column remains in scan when filter pruning happens
> --
>
> Key: DRILL-6910
> URL: https://issues.apache.org/jira/browse/DRILL-6910
> Project: Apache Drill
> Issue Type: Improvement
>Affects Versions: 1.14.0
>Reporter: Anton Gozhiy
>Priority: Major
>
> *Data:*
> {code:sql}
> create table dfs.tmp.`nation` as select * from cp.`tpch/nation.parquet`;
> {code}
> *Query:*
> {code:sql}
> explain plan for select n_nationkey from dfs.tmp.`nation` where n_regionkey <
> 10;
> {code}
> *Expected result:*
> The filtering column (n_regionkey) should not be present in scan operator.
> *Actual result:*
> It remains in scan in spite of filter pruning.
> {noformat}
> 00-00Screen : rowType = RecordType(ANY n_nationkey): rowcount = 25.0,
> cumulative cost = {52.5 rows, 77.5 cpu, 50.0 io, 0.0 network, 0.0 memory}, id
> = 112988
> 00-01 Project(n_nationkey=[$1]) : rowType = RecordType(ANY n_nationkey):
> rowcount = 25.0, cumulative cost = {50.0 rows, 75.0 cpu, 50.0 io, 0.0
> network, 0.0 memory}, id = 112987
> 00-02Scan(table=[[dfs, tmp, nation]], groupscan=[ParquetGroupScan
> [entries=[ReadEntryWithPath [path=maprfs:///tmp/nation]],
> selectionRoot=maprfs:/tmp/nation, numFiles=1, numRowGroups=1,
> usedMetadataFile=false, columns=[`n_regionkey`, `n_nationkey`]]]) : rowType =
> RecordType(ANY n_regionkey, ANY n_nationkey): rowcount = 25.0, cumulative
> cost = {25.0 rows, 50.0 cpu, 50.0 io, 0.0 network, 0.0 memory}, id = 112986
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (DRILL-6911) Documentation issue - Hadoop core-site.xml is not supported by Drill to read S3 credentials
Denys Ordynskiy created DRILL-6911:
--
Summary: Documentation issue - Hadoop core-site.xml is not
supported by Drill to read S3 credentials
Key: DRILL-6911
URL: https://issues.apache.org/jira/browse/DRILL-6911
Project: Apache Drill
Issue Type: Bug
Affects Versions: 1.14.0
Reporter: Denys Ordynskiy
Assignee: Bridget Bevens
In the Drill S3 documentation https://drill.apache.org/docs/s3-storage-plugin/
Section "Providing AWS Credentials" describing 3 ways to setup AWS S3
credentials in Drill:
- storage plugin;
- Drill-specific core-site.xml;
- existing S3 configuration for Hadoop.
Third item is not supported by Drill. Hadoop core-site.xml config file may
contains S3 credentials, but Drill doesn't read any S3 parameters directly from
Hadoop config file.
Third item
{code:java}
In a Hadoop environment, you can use the existing S3 configuration for Hadoop.
The AWS credentials should already be defined. All you need to do is configure
the S3 storage plugin.
{code}
should be removed from the document
https://drill.apache.org/docs/s3-storage-plugin/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-6900) maven-release-plugin failure on the release:perform stage
[
https://issues.apache.org/jira/browse/DRILL-6900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16723969#comment-16723969
]
Vitalii Diravka commented on DRILL-6900:
Merged to Apache Drill master branch with commit id
b23ae6e02495f51a4dcd6fbbf1eb259b6207430b
> maven-release-plugin failure on the release:perform stage
> -
>
> Key: DRILL-6900
> URL: https://issues.apache.org/jira/browse/DRILL-6900
> Project: Apache Drill
> Issue Type: Bug
> Components: Tools, Build Test
>Affects Versions: 1.14.0
>Reporter: Vitalii Diravka
>Assignee: Vitalii Diravka
>Priority: Blocker
> Labels: ready-to-commit
> Fix For: 1.15.0
>
>
> {{release:perform}} stage fails on current master branch. It blocks to
> prepare the release candidate:
> {code:java}
> mvn release:perform
> -DconnectionUrl=scm:git:g...@github.com:vdiravka/drill.git -DskipTests
> -Darguments="-Dgpg.passphrase=${GPG_PASSPHRASE} -DskipTests=true
> -DconnectionUrl=scm:git:g...@github.com:vdiravka/drill.git"
> {code}
> {code:java}
> [INFO] [ERROR]
> /home/vitalii/src/release/drill/target/checkout/contrib/storage-hive/core/src/main/java/org/apache/drill/exec/expr/fn/impl/hive/AbstractDrillPrimitiveObjectInspector.java:[26,47]
> error: cannot find symbol
> [INFO] symbol: class PrimitiveTypeInfo
> [INFO] location: class AbstractDrillPrimitiveObjectInspector
> [INFO] [INFO] 100 errors
> [INFO] [INFO] -
> [INFO] [INFO]
>
> [INFO] [INFO] Reactor Summary for Apache Drill Root POM 1.15.0:
> [INFO] [INFO]
> [INFO] [INFO] Apache Drill Root POM .. SUCCESS [
> 37.579 s]
> [INFO] [INFO] tools/Parent Pom ... SUCCESS [
> 6.360 s]
> [INFO] [INFO] tools/freemarker codegen tooling ... SUCCESS [
> 26.726 s]
> [INFO] [INFO] Drill Protocol . SUCCESS [
> 41.030 s]
> [INFO] [INFO] Common (Logical Plan, Base expressions) SUCCESS [
> 27.754 s]
> [INFO] [INFO] Logical Plan, Base expressions . SUCCESS [
> 29.154 s]
> [INFO] [INFO] exec/Parent Pom SUCCESS [
> 6.252 s]
> [INFO] [INFO] exec/memory/Parent Pom . SUCCESS [
> 6.074 s]
> [INFO] [INFO] exec/memory/base ... SUCCESS [
> 24.909 s]
> [INFO] [INFO] exec/rpc ... SUCCESS [
> 24.191 s]
> [INFO] [INFO] exec/Vectors ... SUCCESS
> [01:50 min]
> [INFO] [INFO] contrib/Parent Pom . SUCCESS [
> 6.173 s]
> [INFO] [INFO] contrib/data/Parent Pom SUCCESS [
> 6.058 s]
> [INFO] [INFO] contrib/data/tpch-sample-data .. SUCCESS [
> 19.704 s]
> [INFO] [INFO] exec/Java Execution Engine . SUCCESS
> [01:57 min]
> [INFO] [INFO] exec/JDBC Driver using dependencies SUCCESS [
> 32.619 s]
> [INFO] [INFO] JDBC JAR with all dependencies . FAILURE
> [01:16 min]
> [INFO] [INFO] Drill-on-YARN .. SKIPPED
> [INFO] [INFO] contrib/kudu-storage-plugin SKIPPED
> [INFO] [INFO] contrib/opentsdb-storage-plugin SKIPPED
> [INFO] [INFO] contrib/mongo-storage-plugin ... SKIPPED
> [INFO] [INFO] contrib/hbase-storage-plugin ... SKIPPED
> [INFO] [INFO] contrib/jdbc-storage-plugin SKIPPED
> [INFO] [INFO] contrib/hive-storage-plugin/Parent Pom . SKIPPED
> [INFO] [INFO] contrib/hive-storage-plugin/hive-exec-shaded ... SKIPPED
> [INFO] [INFO] contrib/mapr-format-plugin . SKIPPED
> [INFO] [INFO] contrib/hive-storage-plugin/core ... SKIPPED
> [INFO] [INFO] contrib/kafka-storage-plugin ... SKIPPED
> [INFO] [INFO] contrib/drill-udfs . SKIPPED
> [INFO] [INFO] Packaging and Distribution Assembly SKIPPED
> [INFO] [INFO]
>
> [INFO] [INFO] BUILD FAILURE
> [INFO] [INFO]
>
> [INFO] [INFO] Total time: 09:58 min
> [INFO] [INFO] Finished at: 2018-12-12T19:18:08+02:00
> [INFO] [INFO]
>
> [INFO] [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile
> (default-compile) on project drill-storage-hive-core:
[jira] [Updated] (DRILL-6910) A filtering column remains in scan when filter pruning happens.
[
https://issues.apache.org/jira/browse/DRILL-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Gozhiy updated DRILL-6910:
Description:
*Data:*
{code:sql}
create table dfs.tmp.`nation` as select * from cp.`tpch/nation.parquet`;
{code}
*Query:*
{code:sql}
explain plan for select n_nationkey from dfs.tmp.`nation` where n_regionkey <
10;
{code}
*Expected result:*
The filtering column (n_regionkey) should not be present in scan operator.
*Actual result:*
It remains in scan in spite of filter pruning.
{noformat}
00-00Screen : rowType = RecordType(ANY n_nationkey): rowcount = 25.0,
cumulative cost = {52.5 rows, 77.5 cpu, 50.0 io, 0.0 network, 0.0 memory}, id =
112988
00-01 Project(n_nationkey=[$1]) : rowType = RecordType(ANY n_nationkey):
rowcount = 25.0, cumulative cost = {50.0 rows, 75.0 cpu, 50.0 io, 0.0 network,
0.0 memory}, id = 112987
00-02Scan(table=[[dfs, tmp, nation]], groupscan=[ParquetGroupScan
[entries=[ReadEntryWithPath [path=maprfs:///tmp/nation]],
selectionRoot=maprfs:/tmp/nation, numFiles=1, numRowGroups=1,
usedMetadataFile=false, columns=[`n_regionkey`, `n_nationkey`]]]) : rowType =
RecordType(ANY n_regionkey, ANY n_nationkey): rowcount = 25.0, cumulative cost
= {25.0 rows, 50.0 cpu, 50.0 io, 0.0 network, 0.0 memory}, id = 112986
{noformat}
was:
*Data:*
{code:sql}
create table dfs.tmp.`nation` as select * from cp.`tpch/nation.parquet`;
{code}
*Query:*
{code:sql}
explain plan for select n_nationkey from dfs.tmp.`nation` where n_regionkey < 10
{code}
*Expected result:*
The filtering column (n_regionkey) should not be present in scan operator.
*Actual result:*
It remains in scan in spite of filter pruning.
{noformat}
00-00Screen : rowType = RecordType(ANY n_nationkey): rowcount = 25.0,
cumulative cost = {52.5 rows, 77.5 cpu, 50.0 io, 0.0 network, 0.0 memory}, id =
112988
00-01 Project(n_nationkey=[$1]) : rowType = RecordType(ANY n_nationkey):
rowcount = 25.0, cumulative cost = {50.0 rows, 75.0 cpu, 50.0 io, 0.0 network,
0.0 memory}, id = 112987
00-02Scan(table=[[dfs, tmp, nation]], groupscan=[ParquetGroupScan
[entries=[ReadEntryWithPath [path=maprfs:///tmp/nation]],
selectionRoot=maprfs:/tmp/nation, numFiles=1, numRowGroups=1,
usedMetadataFile=false, columns=[`n_regionkey`, `n_nationkey`]]]) : rowType =
RecordType(ANY n_regionkey, ANY n_nationkey): rowcount = 25.0, cumulative cost
= {25.0 rows, 50.0 cpu, 50.0 io, 0.0 network, 0.0 memory}, id = 112986
{noformat}
> A filtering column remains in scan when filter pruning happens.
> ---
>
> Key: DRILL-6910
> URL: https://issues.apache.org/jira/browse/DRILL-6910
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Anton Gozhiy
>Priority: Major
>
> *Data:*
> {code:sql}
> create table dfs.tmp.`nation` as select * from cp.`tpch/nation.parquet`;
> {code}
> *Query:*
> {code:sql}
> explain plan for select n_nationkey from dfs.tmp.`nation` where n_regionkey <
> 10;
> {code}
> *Expected result:*
> The filtering column (n_regionkey) should not be present in scan operator.
> *Actual result:*
> It remains in scan in spite of filter pruning.
> {noformat}
> 00-00Screen : rowType = RecordType(ANY n_nationkey): rowcount = 25.0,
> cumulative cost = {52.5 rows, 77.5 cpu, 50.0 io, 0.0 network, 0.0 memory}, id
> = 112988
> 00-01 Project(n_nationkey=[$1]) : rowType = RecordType(ANY n_nationkey):
> rowcount = 25.0, cumulative cost = {50.0 rows, 75.0 cpu, 50.0 io, 0.0
> network, 0.0 memory}, id = 112987
> 00-02Scan(table=[[dfs, tmp, nation]], groupscan=[ParquetGroupScan
> [entries=[ReadEntryWithPath [path=maprfs:///tmp/nation]],
> selectionRoot=maprfs:/tmp/nation, numFiles=1, numRowGroups=1,
> usedMetadataFile=false, columns=[`n_regionkey`, `n_nationkey`]]]) : rowType =
> RecordType(ANY n_regionkey, ANY n_nationkey): rowcount = 25.0, cumulative
> cost = {25.0 rows, 50.0 cpu, 50.0 io, 0.0 network, 0.0 memory}, id = 112986
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (DRILL-6910) A filtering column remains in scan when filter pruning happens.
Anton Gozhiy created DRILL-6910:
---
Summary: A filtering column remains in scan when filter pruning
happens.
Key: DRILL-6910
URL: https://issues.apache.org/jira/browse/DRILL-6910
Project: Apache Drill
Issue Type: Bug
Affects Versions: 1.14.0
Reporter: Anton Gozhiy
*Data:*
{code:sql}
create table dfs.tmp.`nation` as select * from cp.`tpch/nation.parquet`;
{code}
*Query:*
{code:sql}
explain plan for select n_nationkey from dfs.tmp.`nation` where n_regionkey < 10
{code}
*Expected result:*
The filtering column (n_regionkey) should not be present in scan operator.
*Actual result:*
It remains in scan in spite of filter pruning.
{noformat}
00-00Screen : rowType = RecordType(ANY n_nationkey): rowcount = 25.0,
cumulative cost = {52.5 rows, 77.5 cpu, 50.0 io, 0.0 network, 0.0 memory}, id =
112988
00-01 Project(n_nationkey=[$1]) : rowType = RecordType(ANY n_nationkey):
rowcount = 25.0, cumulative cost = {50.0 rows, 75.0 cpu, 50.0 io, 0.0 network,
0.0 memory}, id = 112987
00-02Scan(table=[[dfs, tmp, nation]], groupscan=[ParquetGroupScan
[entries=[ReadEntryWithPath [path=maprfs:///tmp/nation]],
selectionRoot=maprfs:/tmp/nation, numFiles=1, numRowGroups=1,
usedMetadataFile=false, columns=[`n_regionkey`, `n_nationkey`]]]) : rowType =
RecordType(ANY n_regionkey, ANY n_nationkey): rowcount = 25.0, cumulative cost
= {25.0 rows, 50.0 cpu, 50.0 io, 0.0 network, 0.0 memory}, id = 112986
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (DRILL-6900) maven-release-plugin failure on the release:perform stage
[
https://issues.apache.org/jira/browse/DRILL-6900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arina Ielchiieva updated DRILL-6900:
Labels: ready-to-commit (was: )
> maven-release-plugin failure on the release:perform stage
> -
>
> Key: DRILL-6900
> URL: https://issues.apache.org/jira/browse/DRILL-6900
> Project: Apache Drill
> Issue Type: Bug
> Components: Tools, Build Test
>Affects Versions: 1.14.0
>Reporter: Vitalii Diravka
>Assignee: Vitalii Diravka
>Priority: Blocker
> Labels: ready-to-commit
> Fix For: 1.15.0
>
>
> {{release:perform}} stage fails on current master branch. It blocks to
> prepare the release candidate:
> {code:java}
> mvn release:perform
> -DconnectionUrl=scm:git:g...@github.com:vdiravka/drill.git -DskipTests
> -Darguments="-Dgpg.passphrase=${GPG_PASSPHRASE} -DskipTests=true
> -DconnectionUrl=scm:git:g...@github.com:vdiravka/drill.git"
> {code}
> {code:java}
> [INFO] [ERROR]
> /home/vitalii/src/release/drill/target/checkout/contrib/storage-hive/core/src/main/java/org/apache/drill/exec/expr/fn/impl/hive/AbstractDrillPrimitiveObjectInspector.java:[26,47]
> error: cannot find symbol
> [INFO] symbol: class PrimitiveTypeInfo
> [INFO] location: class AbstractDrillPrimitiveObjectInspector
> [INFO] [INFO] 100 errors
> [INFO] [INFO] -
> [INFO] [INFO]
>
> [INFO] [INFO] Reactor Summary for Apache Drill Root POM 1.15.0:
> [INFO] [INFO]
> [INFO] [INFO] Apache Drill Root POM .. SUCCESS [
> 37.579 s]
> [INFO] [INFO] tools/Parent Pom ... SUCCESS [
> 6.360 s]
> [INFO] [INFO] tools/freemarker codegen tooling ... SUCCESS [
> 26.726 s]
> [INFO] [INFO] Drill Protocol . SUCCESS [
> 41.030 s]
> [INFO] [INFO] Common (Logical Plan, Base expressions) SUCCESS [
> 27.754 s]
> [INFO] [INFO] Logical Plan, Base expressions . SUCCESS [
> 29.154 s]
> [INFO] [INFO] exec/Parent Pom SUCCESS [
> 6.252 s]
> [INFO] [INFO] exec/memory/Parent Pom . SUCCESS [
> 6.074 s]
> [INFO] [INFO] exec/memory/base ... SUCCESS [
> 24.909 s]
> [INFO] [INFO] exec/rpc ... SUCCESS [
> 24.191 s]
> [INFO] [INFO] exec/Vectors ... SUCCESS
> [01:50 min]
> [INFO] [INFO] contrib/Parent Pom . SUCCESS [
> 6.173 s]
> [INFO] [INFO] contrib/data/Parent Pom SUCCESS [
> 6.058 s]
> [INFO] [INFO] contrib/data/tpch-sample-data .. SUCCESS [
> 19.704 s]
> [INFO] [INFO] exec/Java Execution Engine . SUCCESS
> [01:57 min]
> [INFO] [INFO] exec/JDBC Driver using dependencies SUCCESS [
> 32.619 s]
> [INFO] [INFO] JDBC JAR with all dependencies . FAILURE
> [01:16 min]
> [INFO] [INFO] Drill-on-YARN .. SKIPPED
> [INFO] [INFO] contrib/kudu-storage-plugin SKIPPED
> [INFO] [INFO] contrib/opentsdb-storage-plugin SKIPPED
> [INFO] [INFO] contrib/mongo-storage-plugin ... SKIPPED
> [INFO] [INFO] contrib/hbase-storage-plugin ... SKIPPED
> [INFO] [INFO] contrib/jdbc-storage-plugin SKIPPED
> [INFO] [INFO] contrib/hive-storage-plugin/Parent Pom . SKIPPED
> [INFO] [INFO] contrib/hive-storage-plugin/hive-exec-shaded ... SKIPPED
> [INFO] [INFO] contrib/mapr-format-plugin . SKIPPED
> [INFO] [INFO] contrib/hive-storage-plugin/core ... SKIPPED
> [INFO] [INFO] contrib/kafka-storage-plugin ... SKIPPED
> [INFO] [INFO] contrib/drill-udfs . SKIPPED
> [INFO] [INFO] Packaging and Distribution Assembly SKIPPED
> [INFO] [INFO]
>
> [INFO] [INFO] BUILD FAILURE
> [INFO] [INFO]
>
> [INFO] [INFO] Total time: 09:58 min
> [INFO] [INFO] Finished at: 2018-12-12T19:18:08+02:00
> [INFO] [INFO]
>
> [INFO] [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile
> (default-compile) on project drill-storage-hive-core: Compilation failure:
> Compilation failure:
> [INFO] [ERROR]
>
[jira] [Updated] (DRILL-6879) Indicate a warning in the WebUI when a query makes little to no progress for a while
[
https://issues.apache.org/jira/browse/DRILL-6879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arina Ielchiieva updated DRILL-6879:
Labels: doc-impacting ready-to-commit (was: doc-impacting user-experience)
> Indicate a warning in the WebUI when a query makes little to no progress for
> a while
>
>
> Key: DRILL-6879
> URL: https://issues.apache.org/jira/browse/DRILL-6879
> Project: Apache Drill
> Issue Type: Improvement
> Components: Execution - Monitoring, Web Server
>Affects Versions: 1.14.0
>Reporter: Kunal Khatua
>Assignee: Kunal Khatua
>Priority: Major
> Labels: doc-impacting, ready-to-commit
> Fix For: 1.16.0
>
> Attachments: image-2018-12-04-11-54-54-247.png,
> image-2018-12-06-11-19-00-339.png, image-2018-12-06-11-27-14-719.png
>
>
> When running a very large query on a cluster with limited resource, we
> noticed that one of the node's VM thread freezes the fragment threads as it
> tries to do some work (GC perhaps?). This is a clear indication that the
> query is stuck in a weird state where it might not recover from.
> Under such circumstances, it makes sense to cancel or atleast warn the user
> on that page of the query exceeding a certain threshold.
> For detecting this, the user will find that the {{Last Progress}} column in
> the Fragments Overview section will show large times.
> !image-2018-12-04-11-54-54-247.png|width=969,height=336!
> In addition, there are instances where a query might have buffered operators
> spilling to disk, which also hits performance (and, subsequently, longer run
> times). Calling out this skew can be very useful.
> !image-2018-12-06-11-27-14-719.png|width=969,height=256!
> Or there might be cases where a single fragment takes much longer than the
> average (indicated by an extreme skew in the Gantt chart).
> !image-2018-12-06-11-19-00-339.png|width=969,height=150!
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (DRILL-6875) Drill doesn't try to update connection for S3 after session expired
[
https://issues.apache.org/jira/browse/DRILL-6875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bohdan Kazydub resolved DRILL-6875.
---
Resolution: Not A Bug
> Drill doesn't try to update connection for S3 after session expired
> ---
>
> Key: DRILL-6875
> URL: https://issues.apache.org/jira/browse/DRILL-6875
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Denys Ordynskiy
>Assignee: Bohdan Kazydub
>Priority: Major
> Fix For: 1.16.0
>
> Attachments: drillbit.log, not_a_bug_drillbit.log
>
>
> *Steps to reproduce:*
> - Drill has S3 storage plugin.
> - Open sqlline and run query to S3.
> - Leave sqlline opened for more than 12 hours.
> - In opened sqlline run query to S3.
> *Expected result:*
> Drill should update authorization session and successfully execute query.
> *Actual result:*
> Sqlline returns an error:
> *{color:#d04437}Error: VALIDATION ERROR: Forbidden (Service: Amazon S3;
> Status Code: 403; Error Code: 403 Forbidden; Request ID: 4A94DD331A035625; S3
> Extended Request ID:
> uy94YdRpQ3ZriCz9xbnDi0yinB4O9kGrH7XPAURhjh8WZoxsbawojQA6v7mfvu920yOYbEI5WP8=)
> [Error Id: 4b44a83b-0e47-45a4-92e3-75f94f5a70cb on maprhost:31010]
> (state=,code=0){color}*
> *Reopening sqlline doesn't help to get S3 access.*
> *Access problem can be solved only by restarting Drill.*
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-6875) Drill doesn't try to update connection for S3 after session expired
[
https://issues.apache.org/jira/browse/DRILL-6875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16723859#comment-16723859
]
Denys Ordynskiy commented on DRILL-6875:
When I actualized time on my virtual machine, bug was fixed.
Successfully log in the attachment "not_a_bug_drillbit.log"
> Drill doesn't try to update connection for S3 after session expired
> ---
>
> Key: DRILL-6875
> URL: https://issues.apache.org/jira/browse/DRILL-6875
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Denys Ordynskiy
>Assignee: Bohdan Kazydub
>Priority: Major
> Fix For: 1.16.0
>
> Attachments: drillbit.log, not_a_bug_drillbit.log
>
>
> *Steps to reproduce:*
> - Drill has S3 storage plugin.
> - Open sqlline and run query to S3.
> - Leave sqlline opened for more than 12 hours.
> - In opened sqlline run query to S3.
> *Expected result:*
> Drill should update authorization session and successfully execute query.
> *Actual result:*
> Sqlline returns an error:
> *{color:#d04437}Error: VALIDATION ERROR: Forbidden (Service: Amazon S3;
> Status Code: 403; Error Code: 403 Forbidden; Request ID: 4A94DD331A035625; S3
> Extended Request ID:
> uy94YdRpQ3ZriCz9xbnDi0yinB4O9kGrH7XPAURhjh8WZoxsbawojQA6v7mfvu920yOYbEI5WP8=)
> [Error Id: 4b44a83b-0e47-45a4-92e3-75f94f5a70cb on maprhost:31010]
> (state=,code=0){color}*
> *Reopening sqlline doesn't help to get S3 access.*
> *Access problem can be solved only by restarting Drill.*
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (DRILL-6875) Drill doesn't try to update connection for S3 after session expired
[
https://issues.apache.org/jira/browse/DRILL-6875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy updated DRILL-6875:
---
Attachment: not_a_bug_drillbit.log
> Drill doesn't try to update connection for S3 after session expired
> ---
>
> Key: DRILL-6875
> URL: https://issues.apache.org/jira/browse/DRILL-6875
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Denys Ordynskiy
>Assignee: Bohdan Kazydub
>Priority: Major
> Fix For: 1.16.0
>
> Attachments: drillbit.log, not_a_bug_drillbit.log
>
>
> *Steps to reproduce:*
> - Drill has S3 storage plugin.
> - Open sqlline and run query to S3.
> - Leave sqlline opened for more than 12 hours.
> - In opened sqlline run query to S3.
> *Expected result:*
> Drill should update authorization session and successfully execute query.
> *Actual result:*
> Sqlline returns an error:
> *{color:#d04437}Error: VALIDATION ERROR: Forbidden (Service: Amazon S3;
> Status Code: 403; Error Code: 403 Forbidden; Request ID: 4A94DD331A035625; S3
> Extended Request ID:
> uy94YdRpQ3ZriCz9xbnDi0yinB4O9kGrH7XPAURhjh8WZoxsbawojQA6v7mfvu920yOYbEI5WP8=)
> [Error Id: 4b44a83b-0e47-45a4-92e3-75f94f5a70cb on maprhost:31010]
> (state=,code=0){color}*
> *Reopening sqlline doesn't help to get S3 access.*
> *Access problem can be solved only by restarting Drill.*
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
