[jira] [Commented] (DRILL-6937) sys.functions table needs a fix in the names column
[
https://issues.apache.org/jira/browse/DRILL-6937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16748442#comment-16748442
]
Kunal Khatua commented on DRILL-6937:
-
I think, everything is implemented as a function. So in this case, the function
is
{{bit Z = greater_than(bigint X, bigint Y)}}
However, the SQL language parser is (probably) providing us syntactic sugar by
making it easier to right
{{Z = X > Y}}
Both options are available to the user, we just tend to use what is more
intuitive.
{code}
0: jdbc:drill:drillbit=kk127> select 2 > 1 from (values(1));
+-+
| EXPR$0 |
+-+
| true|
+-+
1 row selected (0.862 seconds)
0: jdbc:drill:drillbit=kk127> select greater_than(2,1) from (values(1));
+-+
| EXPR$0 |
+-+
| true|
+-+
1 row selected (0.453 seconds)
{code}
> sys.functions table needs a fix in the names column
> ---
>
> Key: DRILL-6937
> URL: https://issues.apache.org/jira/browse/DRILL-6937
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - Flow
>Affects Versions: 1.15.0
>Reporter: Khurram Faraaz
>Assignee: Kunal Khatua
>Priority: Minor
> Fix For: 1.16.0
>
>
> The function names in the name column of sys.functions in some cases, are the
> operators, this is not the expected behavior, the name column should have
> actual names and not the operators.
> I am on Drill 1.15.0 commit : 8743e8f1e8d5bca4d67c94d07a8560ad356ff2b6
> {noformat}
> Apache Drill 1.15.0
> "Data is the new oil. Ready to Drill some?"
> 0: jdbc:drill:schema=dfs.tmp> select count(*) from sys.functions;
> +-+
> | EXPR$0 |
> +-+
> | 2846 |
> +-+
> 1 row selected (0.327 seconds)
> 0: jdbc:drill:schema=dfs.tmp>
> {noformat}
> {noformat}
> 0: jdbc:drill:schema=dfs.tmp> select distinct name from sys.functions limit
> 12;
> ++
> | name |
> ++
> | != |
> | $sum0 |
> | && |
> | - |
> | /int |
> | < |
> | <= |
> | <> |
> | = |
> | == |
> | > |
> | >= |
> ++
> 12 rows selected (0.175 seconds)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-6937) sys.functions table needs a fix in the names column
[
https://issues.apache.org/jira/browse/DRILL-6937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16748292#comment-16748292
]
Khurram Faraaz commented on DRILL-6937:
---
One question is, why do we have two different entries in the sys.functions
table, one with name being ">" and other with name being "greater_than", all
other columns for the two functions seem to have identical values, except for
the name.
{noformat}
| > | BIGINT-REQUIRED,BIGINT-REQUIRED | BIT | built-in | false |
| greater_than | BIGINT-REQUIRED,BIGINT-REQUIRED | BIT | built-in | false |
{noformat}
> sys.functions table needs a fix in the names column
> ---
>
> Key: DRILL-6937
> URL: https://issues.apache.org/jira/browse/DRILL-6937
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - Flow
>Affects Versions: 1.15.0
>Reporter: Khurram Faraaz
>Assignee: Kunal Khatua
>Priority: Minor
> Fix For: 1.16.0
>
>
> The function names in the name column of sys.functions in some cases, are the
> operators, this is not the expected behavior, the name column should have
> actual names and not the operators.
> I am on Drill 1.15.0 commit : 8743e8f1e8d5bca4d67c94d07a8560ad356ff2b6
> {noformat}
> Apache Drill 1.15.0
> "Data is the new oil. Ready to Drill some?"
> 0: jdbc:drill:schema=dfs.tmp> select count(*) from sys.functions;
> +-+
> | EXPR$0 |
> +-+
> | 2846 |
> +-+
> 1 row selected (0.327 seconds)
> 0: jdbc:drill:schema=dfs.tmp>
> {noformat}
> {noformat}
> 0: jdbc:drill:schema=dfs.tmp> select distinct name from sys.functions limit
> 12;
> ++
> | name |
> ++
> | != |
> | $sum0 |
> | && |
> | - |
> | /int |
> | < |
> | <= |
> | <> |
> | = |
> | == |
> | > |
> | >= |
> ++
> 12 rows selected (0.175 seconds)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (DRILL-6950) Row set-based scan framework
[ https://issues.apache.org/jira/browse/DRILL-6950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated DRILL-6950: --- Description: Next step in the ongoing "Result Set Loader" saga. Merge the enhanced scan operator framework Into master. Includes: * Projection add-ons for the "columns" column and file metadata columns. * Mechanisms to orchestrate the result set loader, projection framework, scan node and reader code. * Extensive unit tests. Given the number of test files to review, pushed the following to the next PR: * Extension to the "Easy" reader framework to handle the new structure. was: Next step in the ongoing "Result Set Loader" saga. Merge the enhanced scan node framework Into master. Includes: * Projection add-ons for the "columns" column and file metadata columns. * Extension to the "Easy" reader framework to handle the new structure. * Mechanisms to orchestrate the result set loader, projection framework, scan node and reader code. > Row set-based scan framework > > > Key: DRILL-6950 > URL: https://issues.apache.org/jira/browse/DRILL-6950 > Project: Apache Drill > Issue Type: Improvement >Affects Versions: 1.15.0 >Reporter: Paul Rogers >Assignee: Paul Rogers >Priority: Major > Fix For: 1.16.0 > > > Next step in the ongoing "Result Set Loader" saga. Merge the enhanced scan > operator framework Into master. Includes: > * Projection add-ons for the "columns" column and file metadata columns. > * Mechanisms to orchestrate the result set loader, projection framework, scan > node and reader code. > * Extensive unit tests. > Given the number of test files to review, pushed the following to the next PR: > * Extension to the "Easy" reader framework to handle the new structure. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DRILL-6950) Row set-based scan framework
[ https://issues.apache.org/jira/browse/DRILL-6950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated DRILL-6950: --- Summary: Row set-based scan framework (was: Pull request for row set-based scan framework) > Row set-based scan framework > > > Key: DRILL-6950 > URL: https://issues.apache.org/jira/browse/DRILL-6950 > Project: Apache Drill > Issue Type: Improvement >Affects Versions: 1.15.0 >Reporter: Paul Rogers >Assignee: Paul Rogers >Priority: Major > Fix For: 1.16.0 > > > Next step in the ongoing "Result Set Loader" saga. Merge the enhanced scan > node framework Into master. Includes: > * Projection add-ons for the "columns" column and file metadata columns. > * Extension to the "Easy" reader framework to handle the new structure. > * Mechanisms to orchestrate the result set loader, projection framework, scan > node and reader code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (DRILL-6937) sys.functions table needs a fix in the names column
[
https://issues.apache.org/jira/browse/DRILL-6937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16748280#comment-16748280
]
Kunal Khatua edited comment on DRILL-6937 at 1/22/19 12:02 AM:
---
[~khfaraaz] the {{/int}} function name is correct. See
https://github.com/apache/drill/blame/master/exec/java-exec/src/main/codegen/templates/DateIntervalFunctionTemplates/IntervalNumericArithmetic.java#L133
That said, I'm not sure if this is really a bug, since there have been other
functions, like {{$sum0}} around as well:
https://github.com/apache/drill/blame/master/exec/java-exec/src/main/codegen/templates/SumZeroAggr.java#L48
Not all functions in the {{sys.functions}} table are necessarily utilized by
users in their alphabetical representation, and are exposed to mathematical
symbols as operators, but Drill implicitly transforms it into the appropriate
function.
For example, the _equals_ , _less than_ or _greater than_ operator can be
seen here in multiple forms.
{code}
0: jdbc:drill:drillbit=kk127> select * from sys.functions where returnType =
'BIT' and signature = 'BIGINT-REQUIRED,BIGINT-REQUIRED' limit 15;
+---+--+-+---+---+
| name|signature | returnType |
source | internal |
+---+--+-+---+---+
| !=| BIGINT-REQUIRED,BIGINT-REQUIRED | BIT |
built-in | false |
| < | BIGINT-REQUIRED,BIGINT-REQUIRED | BIT |
built-in | false |
| <=| BIGINT-REQUIRED,BIGINT-REQUIRED | BIT |
built-in | false |
| <>| BIGINT-REQUIRED,BIGINT-REQUIRED | BIT |
built-in | false |
| = | BIGINT-REQUIRED,BIGINT-REQUIRED | BIT |
built-in | false |
| ==| BIGINT-REQUIRED,BIGINT-REQUIRED | BIT |
built-in | false |
| > | BIGINT-REQUIRED,BIGINT-REQUIRED | BIT |
built-in | false |
| >=| BIGINT-REQUIRED,BIGINT-REQUIRED | BIT |
built-in | false |
| equal | BIGINT-REQUIRED,BIGINT-REQUIRED | BIT |
built-in | false |
| greater_than | BIGINT-REQUIRED,BIGINT-REQUIRED | BIT |
built-in | false |
| greater_than_or_equal_to | BIGINT-REQUIRED,BIGINT-REQUIRED | BIT |
built-in | false |
| less_than | BIGINT-REQUIRED,BIGINT-REQUIRED | BIT |
built-in | false |
| less_than_or_equal_to | BIGINT-REQUIRED,BIGINT-REQUIRED | BIT |
built-in | false |
| not_equal | BIGINT-REQUIRED,BIGINT-REQUIRED | BIT |
built-in | false |
+---+--+-+---+---+
14 rows selected (0.282 seconds)
{code}
So, I'm not sure this would qualify as a bug.
[~arina] do you agree?
was (Author: kkhatua):
[~khfaraaz] the {{/int}} function name is correct. See
https://github.com/apache/drill/blame/master/exec/java-exec/src/main/codegen/templates/DateIntervalFunctionTemplates/IntervalNumericArithmetic.java#L133
That said, I'm not sure if this is really a bug, since there have been other
functions, like {{$sum0}} around as well:
https://github.com/apache/drill/blame/master/exec/java-exec/src/main/codegen/templates/SumZeroAggr.java#L48
Not all functions in the {{sys.functions}} table are necessarily utilized by
users in their alphabetical representation, and are exposed to mathematical
symbols as operators.
For example, the _less than_ or _greater than_ operator can be seen here in
multiple forms.
{code}
0: jdbc:drill:drillbit=kk127> select * from sys.functions where returnType =
'BIT' and signature = 'BIGINT-REQUIRED,BIGINT-REQUIRED' limit 15;
+---+--+-+---+---+
| name|signature | returnType |
source | internal |
+---+--+-+---+---+
| !=| BIGINT-REQUIRED,BIGINT-REQUIRED | BIT |
built-in | false |
| < | BIGINT-REQUIRED,BIGINT-REQUIRED | BIT |
built-in | false |
| <=| BIGINT-REQUIRED,BIGINT-REQUIRED | BIT |
built-in | false |
| <>| BIGINT-REQUIRED,BIGINT-REQUIRED | BIT |
built-in | false |
| = | BIGINT-REQUIRED,BIGINT-REQUIRED | BIT |
built-in | false |
| ==| BIGINT-REQUIRED,BIGINT-REQUIRED | BIT
[jira] [Updated] (DRILL-6956) Maintain a single entry for Drill Version in the pom file
[ https://issues.apache.org/jira/browse/DRILL-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kunal Khatua updated DRILL-6956: Due Date: 25/Feb/19 > Maintain a single entry for Drill Version in the pom file > - > > Key: DRILL-6956 > URL: https://issues.apache.org/jira/browse/DRILL-6956 > Project: Apache Drill > Issue Type: Improvement > Components: Tools, Build Test >Affects Versions: 1.15.0 >Reporter: Kunal Khatua >Assignee: Kunal Khatua >Priority: Major > Fix For: 1.16.0 > > > Currently, updating the version information for a Drill release involves > updating 30+ pom files. > The right way would be to use the Multi Module Setup for Maven CI. > https://maven.apache.org/maven-ci-friendly.html#Multi_Module_Setup -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DRILL-6937) sys.functions table needs a fix in the names column
[
https://issues.apache.org/jira/browse/DRILL-6937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16748280#comment-16748280
]
Kunal Khatua commented on DRILL-6937:
-
[~khfaraaz] the {{/int}} function name is correct. See
https://github.com/apache/drill/blame/master/exec/java-exec/src/main/codegen/templates/DateIntervalFunctionTemplates/IntervalNumericArithmetic.java#L133
That said, I'm not sure if this is really a bug, since there have been other
functions, like {{$sum0}} around as well:
https://github.com/apache/drill/blame/master/exec/java-exec/src/main/codegen/templates/SumZeroAggr.java#L48
Not all functions in the {{sys.functions}} table are necessarily utilized by
users in their alphabetical representation, and are exposed to mathematical
symbols as operators.
For example, the _less than_ or _greater than_ operator can be seen here in
multiple forms.
{code}
0: jdbc:drill:drillbit=kk127> select * from sys.functions where returnType =
'BIT' and signature = 'BIGINT-REQUIRED,BIGINT-REQUIRED' limit 15;
+---+--+-+---+---+
| name|signature | returnType |
source | internal |
+---+--+-+---+---+
| !=| BIGINT-REQUIRED,BIGINT-REQUIRED | BIT |
built-in | false |
| < | BIGINT-REQUIRED,BIGINT-REQUIRED | BIT |
built-in | false |
| <=| BIGINT-REQUIRED,BIGINT-REQUIRED | BIT |
built-in | false |
| <>| BIGINT-REQUIRED,BIGINT-REQUIRED | BIT |
built-in | false |
| = | BIGINT-REQUIRED,BIGINT-REQUIRED | BIT |
built-in | false |
| ==| BIGINT-REQUIRED,BIGINT-REQUIRED | BIT |
built-in | false |
| > | BIGINT-REQUIRED,BIGINT-REQUIRED | BIT |
built-in | false |
| >=| BIGINT-REQUIRED,BIGINT-REQUIRED | BIT |
built-in | false |
| equal | BIGINT-REQUIRED,BIGINT-REQUIRED | BIT |
built-in | false |
| greater_than | BIGINT-REQUIRED,BIGINT-REQUIRED | BIT |
built-in | false |
| greater_than_or_equal_to | BIGINT-REQUIRED,BIGINT-REQUIRED | BIT |
built-in | false |
| less_than | BIGINT-REQUIRED,BIGINT-REQUIRED | BIT |
built-in | false |
| less_than_or_equal_to | BIGINT-REQUIRED,BIGINT-REQUIRED | BIT |
built-in | false |
| not_equal | BIGINT-REQUIRED,BIGINT-REQUIRED | BIT |
built-in | false |
+---+--+-+---+---+
14 rows selected (0.282 seconds)
{code}
So, I'm not sure this would qualify as a bug.
[~arina] do you agree?
> sys.functions table needs a fix in the names column
> ---
>
> Key: DRILL-6937
> URL: https://issues.apache.org/jira/browse/DRILL-6937
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - Flow
>Affects Versions: 1.15.0
>Reporter: Khurram Faraaz
>Assignee: Kunal Khatua
>Priority: Minor
> Fix For: 1.16.0
>
>
> The function names in the name column of sys.functions in some cases, are the
> operators, this is not the expected behavior, the name column should have
> actual names and not the operators.
> I am on Drill 1.15.0 commit : 8743e8f1e8d5bca4d67c94d07a8560ad356ff2b6
> {noformat}
> Apache Drill 1.15.0
> "Data is the new oil. Ready to Drill some?"
> 0: jdbc:drill:schema=dfs.tmp> select count(*) from sys.functions;
> +-+
> | EXPR$0 |
> +-+
> | 2846 |
> +-+
> 1 row selected (0.327 seconds)
> 0: jdbc:drill:schema=dfs.tmp>
> {noformat}
> {noformat}
> 0: jdbc:drill:schema=dfs.tmp> select distinct name from sys.functions limit
> 12;
> ++
> | name |
> ++
> | != |
> | $sum0 |
> | && |
> | - |
> | /int |
> | < |
> | <= |
> | <> |
> | = |
> | == |
> | > |
> | >= |
> ++
> 12 rows selected (0.175 seconds)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (DRILL-6990) IllegalStateException: The current reader doesn't support getting next information
Khurram Faraaz created DRILL-6990:
-
Summary: IllegalStateException: The current reader doesn't support
getting next information
Key: DRILL-6990
URL: https://issues.apache.org/jira/browse/DRILL-6990
Project: Apache Drill
Issue Type: Bug
Affects Versions: 1.14.0
Reporter: Khurram Faraaz
Attachments: parqt_nestedArray.parquet.tar
Reading a parquet file created from Spark, returns IllegalStateException: The
current reader doesn't support getting next information
Drill 1.14.0, parquet file created from Spark is attached here.
//Steps to create parquet file from Spark 2.3.1
[root@ba102-495 ~]# cd /opt/mapr/spark/spark-2.3.1
[root@ba102-495 spark-2.3.1]# cd bin
[root@ba102-495 bin]# ./spark-shell
19/01/21 22:57:05 WARN NativeCodeLoader: Unable to load native-hadoop library
for your platform... using builtin-java classes where applicable
Spark context Web UI available at http://qa102-45.qa.lab:4040
Spark context available as 'sc' (master = local[*], app id =
local-1548111430809).
Spark session available as 'spark'.
Welcome to
__
/ __/__ ___ _/ /__
_\ \/ _ \/ _ `/ __/ '_/
/___/ .__/\_,_/_/ /_/\_\ version 2.3.1-mapr-SNAPSHOT
/_/
Using Scala version 2.11.8 (OpenJDK 64-Bit Server VM, Java 1.8.0_191)
Type in expressions to have them evaluated.
Type :help for more information.
scala> import spark.implicits._
import spark.implicits._
scala> val df = spark.read.json("/apps/nestedDataJson.json")
df: org.apache.spark.sql.DataFrame = [id: bigint, nested_array:
array>]
scala> df.write.parquet("/apps/parqt_nestedArray.parquet")
Data used in test
{noformat}
[root@ba102-495 ~]# cat nestedDataJson.json
{"id":19,"nested_array":[[1,2,3,4],[5,6,7,8],[9,10,12]]}
{"id":14121,"nested_array":[[1,3,4],[5,6,8],[9,11,12]]}
{"id":18894,"nested_array":[[1,3,4],[5,6,7,8],[9,10,11,12]]}
{"id":12499,"nested_array":[[1,4],[5,7,8],[9,11,12]]}
{"id":120,"nested_array":[[1,4],[5,7,8],[9,10,11,12]]}
{"id":12,"nested_array":[[1,2,3,4],[5,6,7,8],[11,12]]}
{"id":13,"nested_array":[[1,2,3,4],[5,8],[9,10,11,12]]}
{"id":14,"nested_array":[[1,2,3,4],[5,68],[9,10,11,12]]}
{"id":123,"nested_array":[[1,2,3,4],[5,8],[9,10,11,12]]}
{"id":124,"nested_array":[[1,2,4],[5,6,7,8],[9,10,11,12]]}
{"id":134,"nested_array":[[1,4],[5,8],[9,12]]}
{noformat}
>From drillbit.log
{noformat}
Query Failed: An Error Occurred
org.apache.drill.common.exceptions.UserRemoteException: SYSTEM ERROR:
IllegalStateException: The current reader doesn't support getting next
information. Fragment 0:0 [Error Id: c16c70dd-6565-463f-83a7-118ccd8442e2 on
ba102-495.qa.lab:31010]
...
...
2019-01-21 23:08:11,268 [23b9af24-10b9-ad11-5583-ecc3e0c562e6:frag:0:0] ERROR
o.a.d.e.w.fragment.FragmentExecutor - SYSTEM ERROR: IllegalStateException: The
current reader doesn't support getting next information.
Fragment 0:0
[Error Id: c16c70dd-6565-463f-83a7-118ccd8442e2 on ba102-495.qa.lab:31010]
org.apache.drill.common.exceptions.UserException: SYSTEM ERROR:
IllegalStateException: The current reader doesn't support getting next
information.
Fragment 0:0
[Error Id: c16c70dd-6565-463f-83a7-118ccd8442e2 on ba102-495.qa.lab:31010]
at
org.apache.drill.common.exceptions.UserException$Builder.build(UserException.java:633)
~[drill-common-1.14.0-mapr.jar:1.14.0-mapr]
at
org.apache.drill.exec.work.fragment.FragmentExecutor.sendFinalState(FragmentExecutor.java:361)
[drill-java-exec-1.14.0-mapr.jar:1.14.0-mapr]
at
org.apache.drill.exec.work.fragment.FragmentExecutor.cleanup(FragmentExecutor.java:216)
[drill-java-exec-1.14.0-mapr.jar:1.14.0-mapr]
at
org.apache.drill.exec.work.fragment.FragmentExecutor.run(FragmentExecutor.java:327)
[drill-java-exec-1.14.0-mapr.jar:1.14.0-mapr]
at
org.apache.drill.common.SelfCleaningRunnable.run(SelfCleaningRunnable.java:38)
[drill-common-1.14.0-mapr.jar:1.14.0-mapr]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[na:1.8.0_181]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[na:1.8.0_181]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_181]
Caused by: java.lang.IllegalStateException: The current reader doesn't support
getting next information.
at
org.apache.drill.exec.vector.complex.impl.AbstractBaseReader.next(AbstractBaseReader.java:64)
~[vector-1.14.0-mapr.jar:1.14.0-mapr]
at
org.apache.drill.exec.vector.complex.impl.SingleMapReaderImpl.next(SingleMapReaderImpl.java:31)
~[vector-1.14.0-mapr.jar:1.14.0-mapr]
at
org.apache.drill.exec.test.generated.ProjectorGen971.doEval(ProjectorTemplate.java:35)
~[na:na]
at
org.apache.drill.exec.test.generated.ProjectorGen971.projectRecords(ProjectorTemplate.java:67)
~[na:na]
at
org.apache.drill.exec.physical.impl.project.ProjectRecordBatch.doWork(ProjectRecordBatch.java:231)
~[drill-java-exec-1.14.0-mapr.jar:1.14.0-mapr]
at
[jira] [Updated] (DRILL-6533) (type|sqlType|drillType|mode)Of functions fail when used with constants
[
https://issues.apache.org/jira/browse/DRILL-6533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volodymyr Vysotskyi updated DRILL-6533:
---
Fix Version/s: 1.16.0
> (type|sqlType|drillType|mode)Of functions fail when used with constants
> ---
>
> Key: DRILL-6533
> URL: https://issues.apache.org/jira/browse/DRILL-6533
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Arina Ielchiieva
>Assignee: Volodymyr Vysotskyi
>Priority: Major
> Fix For: 1.16.0
>
>
> Affected functions: typeOf, sqlTypeOf, drillTypeOf, modeOf
> Example:
> {noformat}
> 0: jdbc:drill:drillbit=localhost> select typeOf(1) from (values(1));
> Error: SYSTEM ERROR: IllegalArgumentException: Can not set
> org.apache.drill.exec.vector.complex.reader.FieldReader field
> org.apache.drill.exec.expr.fn.impl.UnionFunctions$GetType.input to
> org.apache.drill.exec.expr.holders.IntHolder
> [Error Id: 709cf2f7-7396-4034-8c5a-e94d78504297 on cv1:31010]
> (org.apache.drill.exec.work.foreman.ForemanException) Unexpected exception
> during fragment initialization: Error while applying rule
> ReduceExpressionsRule(Project), args
> [rel#3945:LogicalProject.NONE.ANY([]).[](input=rel#3944:Subset#0.NONE.ANY([]).[0],EXPR$0=TYPEOF(1))]
> org.apache.drill.exec.work.foreman.Foreman.run():294
> java.util.concurrent.ThreadPoolExecutor.runWorker():1149
> java.util.concurrent.ThreadPoolExecutor$Worker.run():624
> java.lang.Thread.run():748
> Caused By (java.lang.RuntimeException) Error while applying rule
> ReduceExpressionsRule(Project), args
> [rel#3945:LogicalProject.NONE.ANY([]).[](input=rel#3944:Subset#0.NONE.ANY([]).[0],EXPR$0=TYPEOF(1))]
> org.apache.calcite.plan.volcano.VolcanoRuleCall.onMatch():236
> org.apache.calcite.plan.volcano.VolcanoPlanner.findBestExp():652
> org.apache.calcite.tools.Programs$RuleSetProgram.run():368
>
> org.apache.drill.exec.planner.sql.handlers.DefaultSqlHandler.transform():426
>
> org.apache.drill.exec.planner.sql.handlers.DefaultSqlHandler.transform():366
>
> org.apache.drill.exec.planner.sql.handlers.DefaultSqlHandler.convertToRawDrel():255
>
> org.apache.drill.exec.planner.sql.handlers.DefaultSqlHandler.convertToDrel():315
> org.apache.drill.exec.planner.sql.handlers.DefaultSqlHandler.getPlan():180
> org.apache.drill.exec.planner.sql.DrillSqlWorker.getQueryPlan():145
> org.apache.drill.exec.planner.sql.DrillSqlWorker.getPlan():83
> org.apache.drill.exec.work.foreman.Foreman.runSQL():567
> org.apache.drill.exec.work.foreman.Foreman.run():266
> java.util.concurrent.ThreadPoolExecutor.runWorker():1149
> java.util.concurrent.ThreadPoolExecutor$Worker.run():624
> java.lang.Thread.run():748
> Caused By (java.lang.RuntimeException) Error in evaluating function of
> typeof
>
> org.apache.drill.exec.expr.fn.interpreter.InterpreterEvaluator$EvalVisitor.visitFunctionHolderExpression():347
>
> org.apache.drill.exec.expr.fn.interpreter.InterpreterEvaluator$EvalVisitor.visitFunctionHolderExpression():194
> org.apache.drill.common.expression.FunctionHolderExpression.accept():53
>
> org.apache.drill.exec.expr.fn.interpreter.InterpreterEvaluator.evaluateConstantExpr():69
> org.apache.drill.exec.planner.logical.DrillConstExecutor.reduce():150
>
> org.apache.calcite.rel.rules.ReduceExpressionsRule.reduceExpressionsInternal():620
> org.apache.calcite.rel.rules.ReduceExpressionsRule.reduceExpressions():540
>
> org.apache.calcite.rel.rules.ReduceExpressionsRule$ProjectReduceExpressionsRule.onMatch():288
> org.apache.calcite.plan.volcano.VolcanoRuleCall.onMatch():212
> org.apache.calcite.plan.volcano.VolcanoPlanner.findBestExp():652
> org.apache.calcite.tools.Programs$RuleSetProgram.run():368
>
> org.apache.drill.exec.planner.sql.handlers.DefaultSqlHandler.transform():426
>
> org.apache.drill.exec.planner.sql.handlers.DefaultSqlHandler.transform():366
>
> org.apache.drill.exec.planner.sql.handlers.DefaultSqlHandler.convertToRawDrel():255
>
> org.apache.drill.exec.planner.sql.handlers.DefaultSqlHandler.convertToDrel():315
> org.apache.drill.exec.planner.sql.handlers.DefaultSqlHandler.getPlan():180
> org.apache.drill.exec.planner.sql.DrillSqlWorker.getQueryPlan():145
> org.apache.drill.exec.planner.sql.DrillSqlWorker.getPlan():83
> org.apache.drill.exec.work.foreman.Foreman.runSQL():567
> org.apache.drill.exec.work.foreman.Foreman.run():266
> java.util.concurrent.ThreadPoolExecutor.runWorker():1149
> java.util.concurrent.ThreadPoolExecutor$Worker.run():624
> java.lang.Thread.run():748
> Caused By (java.lang.IllegalArgumentException) Can not set
>
[jira] [Assigned] (DRILL-6533) (type|sqlType|drillType|mode)Of functions fail when used with constants
[
https://issues.apache.org/jira/browse/DRILL-6533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volodymyr Vysotskyi reassigned DRILL-6533:
--
Assignee: Volodymyr Vysotskyi
> (type|sqlType|drillType|mode)Of functions fail when used with constants
> ---
>
> Key: DRILL-6533
> URL: https://issues.apache.org/jira/browse/DRILL-6533
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Arina Ielchiieva
>Assignee: Volodymyr Vysotskyi
>Priority: Major
>
> Affected functions: typeOf, sqlTypeOf, drillTypeOf, modeOf
> Example:
> {noformat}
> 0: jdbc:drill:drillbit=localhost> select typeOf(1) from (values(1));
> Error: SYSTEM ERROR: IllegalArgumentException: Can not set
> org.apache.drill.exec.vector.complex.reader.FieldReader field
> org.apache.drill.exec.expr.fn.impl.UnionFunctions$GetType.input to
> org.apache.drill.exec.expr.holders.IntHolder
> [Error Id: 709cf2f7-7396-4034-8c5a-e94d78504297 on cv1:31010]
> (org.apache.drill.exec.work.foreman.ForemanException) Unexpected exception
> during fragment initialization: Error while applying rule
> ReduceExpressionsRule(Project), args
> [rel#3945:LogicalProject.NONE.ANY([]).[](input=rel#3944:Subset#0.NONE.ANY([]).[0],EXPR$0=TYPEOF(1))]
> org.apache.drill.exec.work.foreman.Foreman.run():294
> java.util.concurrent.ThreadPoolExecutor.runWorker():1149
> java.util.concurrent.ThreadPoolExecutor$Worker.run():624
> java.lang.Thread.run():748
> Caused By (java.lang.RuntimeException) Error while applying rule
> ReduceExpressionsRule(Project), args
> [rel#3945:LogicalProject.NONE.ANY([]).[](input=rel#3944:Subset#0.NONE.ANY([]).[0],EXPR$0=TYPEOF(1))]
> org.apache.calcite.plan.volcano.VolcanoRuleCall.onMatch():236
> org.apache.calcite.plan.volcano.VolcanoPlanner.findBestExp():652
> org.apache.calcite.tools.Programs$RuleSetProgram.run():368
>
> org.apache.drill.exec.planner.sql.handlers.DefaultSqlHandler.transform():426
>
> org.apache.drill.exec.planner.sql.handlers.DefaultSqlHandler.transform():366
>
> org.apache.drill.exec.planner.sql.handlers.DefaultSqlHandler.convertToRawDrel():255
>
> org.apache.drill.exec.planner.sql.handlers.DefaultSqlHandler.convertToDrel():315
> org.apache.drill.exec.planner.sql.handlers.DefaultSqlHandler.getPlan():180
> org.apache.drill.exec.planner.sql.DrillSqlWorker.getQueryPlan():145
> org.apache.drill.exec.planner.sql.DrillSqlWorker.getPlan():83
> org.apache.drill.exec.work.foreman.Foreman.runSQL():567
> org.apache.drill.exec.work.foreman.Foreman.run():266
> java.util.concurrent.ThreadPoolExecutor.runWorker():1149
> java.util.concurrent.ThreadPoolExecutor$Worker.run():624
> java.lang.Thread.run():748
> Caused By (java.lang.RuntimeException) Error in evaluating function of
> typeof
>
> org.apache.drill.exec.expr.fn.interpreter.InterpreterEvaluator$EvalVisitor.visitFunctionHolderExpression():347
>
> org.apache.drill.exec.expr.fn.interpreter.InterpreterEvaluator$EvalVisitor.visitFunctionHolderExpression():194
> org.apache.drill.common.expression.FunctionHolderExpression.accept():53
>
> org.apache.drill.exec.expr.fn.interpreter.InterpreterEvaluator.evaluateConstantExpr():69
> org.apache.drill.exec.planner.logical.DrillConstExecutor.reduce():150
>
> org.apache.calcite.rel.rules.ReduceExpressionsRule.reduceExpressionsInternal():620
> org.apache.calcite.rel.rules.ReduceExpressionsRule.reduceExpressions():540
>
> org.apache.calcite.rel.rules.ReduceExpressionsRule$ProjectReduceExpressionsRule.onMatch():288
> org.apache.calcite.plan.volcano.VolcanoRuleCall.onMatch():212
> org.apache.calcite.plan.volcano.VolcanoPlanner.findBestExp():652
> org.apache.calcite.tools.Programs$RuleSetProgram.run():368
>
> org.apache.drill.exec.planner.sql.handlers.DefaultSqlHandler.transform():426
>
> org.apache.drill.exec.planner.sql.handlers.DefaultSqlHandler.transform():366
>
> org.apache.drill.exec.planner.sql.handlers.DefaultSqlHandler.convertToRawDrel():255
>
> org.apache.drill.exec.planner.sql.handlers.DefaultSqlHandler.convertToDrel():315
> org.apache.drill.exec.planner.sql.handlers.DefaultSqlHandler.getPlan():180
> org.apache.drill.exec.planner.sql.DrillSqlWorker.getQueryPlan():145
> org.apache.drill.exec.planner.sql.DrillSqlWorker.getPlan():83
> org.apache.drill.exec.work.foreman.Foreman.runSQL():567
> org.apache.drill.exec.work.foreman.Foreman.run():266
> java.util.concurrent.ThreadPoolExecutor.runWorker():1149
> java.util.concurrent.ThreadPoolExecutor$Worker.run():624
> java.lang.Thread.run():748
> Caused By (java.lang.IllegalArgumentException) Can not set
> org.apache.drill.exec.vector.complex.reader.FieldReader field
[jira] [Updated] (DRILL-6985) Fix sqlline.bat issues on Windows
[
https://issues.apache.org/jira/browse/DRILL-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arina Ielchiieva updated DRILL-6985:
Description:
*For documentation*
{{drill-embedded.bat}} was added as handy script to Start Drill on Windows
without passing any params.
Please updated the following section:
https://drill.apache.org/docs/starting-drill-on-windows/
Other issues covered in this Jira:
{{sqlline.bat}} fails for the next cases:
1. Specified file in the argument:
{noformat}
apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -f /tmp/q.sql
DRILL_ARGS - " -u jdbc:drill:zk=local"
HADOOP_HOME not detected...
HBASE_HOME not detected...
Calculating Drill classpath...
Error: Could not find or load main class sqlline.SqlLine
{noformat}
2. Specified file path that contains spaces:
{noformat}
apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -f "/tmp/q q.sql"
DRILL_ARGS - " -u jdbc:drill:zk=local"
HADOOP_HOME not detected...
HBASE_HOME not detected...
Calculating Drill classpath...
q.sql""=="test" was unexpected at this time.
{noformat}
3. Specified query in the argument:
{noformat}
apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -e "select * from
sys.version"
DRILL_ARGS - " -u jdbc:drill:zk=local"
HADOOP_HOME not detected...
HBASE_HOME not detected...
Calculating Drill classpath...
* was unexpected at this time.
{noformat}
{noformat}
apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -q "select 'a'
from sys.version"
DRILL_ARGS - " -u jdbc:drill:zk=local"
HADOOP_HOME not detected...
HBASE_HOME not detected...
Calculating Drill classpath...
'a' was unexpected at this time.
{noformat}
4. Specified custom config location:
{noformat}
apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" --config=/tmp/conf
DRILL_ARGS - " -u jdbc:drill:zk=local"
HADOOP_HOME not detected...
HBASE_HOME not detected...
Calculating Drill classpath...
Error: Could not find or load main class sqlline.SqlLine
{noformat}
5. Specified custom config location with spaces in the path:
{noformat}
apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local"
--config="/tmp/conf test"
DRILL_ARGS - " -u jdbc:drill:zk=local"
test"" was unexpected at this time.
{noformat}
6. Sqlline was run from non-bin directory:
{noformat}
apache-drill-1.15.0>bin\sqlline.bat -u "jdbc:drill:zk=local"
DRILL_ARGS - " -u jdbc:drill:zk=local"
HADOOP_HOME not detected...
HBASE_HOME not detected...
Calculating Drill classpath...
Error: Could not find or load main class sqlline.SqlLine
{noformat}
was:
*For documentation*
{{drill-embedded.bat}} was added as handy script to Start Drill on Windows
without passing any params.
Please updated the following section:
https://drill.apache.org/docs/starting-drill-on-windows/
{{sqlline.bat}} fails for the next cases:
1. Specified file in the argument:
{noformat}
apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -f /tmp/q.sql
DRILL_ARGS - " -u jdbc:drill:zk=local"
HADOOP_HOME not detected...
HBASE_HOME not detected...
Calculating Drill classpath...
Error: Could not find or load main class sqlline.SqlLine
{noformat}
2. Specified file path that contains spaces:
{noformat}
apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -f "/tmp/q q.sql"
DRILL_ARGS - " -u jdbc:drill:zk=local"
HADOOP_HOME not detected...
HBASE_HOME not detected...
Calculating Drill classpath...
q.sql""=="test" was unexpected at this time.
{noformat}
3. Specified query in the argument:
{noformat}
apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -e "select * from
sys.version"
DRILL_ARGS - " -u jdbc:drill:zk=local"
HADOOP_HOME not detected...
HBASE_HOME not detected...
Calculating Drill classpath...
* was unexpected at this time.
{noformat}
{noformat}
apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -q "select 'a'
from sys.version"
DRILL_ARGS - " -u jdbc:drill:zk=local"
HADOOP_HOME not detected...
HBASE_HOME not detected...
Calculating Drill classpath...
'a' was unexpected at this time.
{noformat}
4. Specified custom config location:
{noformat}
apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" --config=/tmp/conf
DRILL_ARGS - " -u jdbc:drill:zk=local"
HADOOP_HOME not detected...
HBASE_HOME not detected...
Calculating Drill classpath...
Error: Could not find or load main class sqlline.SqlLine
{noformat}
5. Specified custom config location with spaces in the path:
{noformat}
apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local"
--config="/tmp/conf test"
DRILL_ARGS - " -u jdbc:drill:zk=local"
test"" was unexpected at this time.
{noformat}
6. Sqlline was run from non-bin directory:
{noformat}
apache-drill-1.15.0>bin\sqlline.bat -u "jdbc:drill:zk=local"
DRILL_ARGS - " -u jdbc:drill:zk=local"
HADOOP_HOME not detected...
HBASE_HOME not detected...
Calculating Drill classpath...
Error: Could not find or load main class sqlline.SqlLine
{noformat}
> Fix sqlline.bat issues on
[jira] [Updated] (DRILL-6985) Fix sqlline.bat issues on Windows
[
https://issues.apache.org/jira/browse/DRILL-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arina Ielchiieva updated DRILL-6985:
Description:
*For documentation*
{{drill-embedded.bat}} was added as handy script to Start Drill on Windows
without passing any params.
Please updated the following section:
https://drill.apache.org/docs/starting-drill-on-windows/
{{sqlline.bat}} fails for the next cases:
1. Specified file in the argument:
{noformat}
apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -f /tmp/q.sql
DRILL_ARGS - " -u jdbc:drill:zk=local"
HADOOP_HOME not detected...
HBASE_HOME not detected...
Calculating Drill classpath...
Error: Could not find or load main class sqlline.SqlLine
{noformat}
2. Specified file path that contains spaces:
{noformat}
apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -f "/tmp/q q.sql"
DRILL_ARGS - " -u jdbc:drill:zk=local"
HADOOP_HOME not detected...
HBASE_HOME not detected...
Calculating Drill classpath...
q.sql""=="test" was unexpected at this time.
{noformat}
3. Specified query in the argument:
{noformat}
apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -e "select * from
sys.version"
DRILL_ARGS - " -u jdbc:drill:zk=local"
HADOOP_HOME not detected...
HBASE_HOME not detected...
Calculating Drill classpath...
* was unexpected at this time.
{noformat}
{noformat}
apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -q "select 'a'
from sys.version"
DRILL_ARGS - " -u jdbc:drill:zk=local"
HADOOP_HOME not detected...
HBASE_HOME not detected...
Calculating Drill classpath...
'a' was unexpected at this time.
{noformat}
4. Specified custom config location:
{noformat}
apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" --config=/tmp/conf
DRILL_ARGS - " -u jdbc:drill:zk=local"
HADOOP_HOME not detected...
HBASE_HOME not detected...
Calculating Drill classpath...
Error: Could not find or load main class sqlline.SqlLine
{noformat}
5. Specified custom config location with spaces in the path:
{noformat}
apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local"
--config="/tmp/conf test"
DRILL_ARGS - " -u jdbc:drill:zk=local"
test"" was unexpected at this time.
{noformat}
6. Sqlline was run from non-bin directory:
{noformat}
apache-drill-1.15.0>bin\sqlline.bat -u "jdbc:drill:zk=local"
DRILL_ARGS - " -u jdbc:drill:zk=local"
HADOOP_HOME not detected...
HBASE_HOME not detected...
Calculating Drill classpath...
Error: Could not find or load main class sqlline.SqlLine
{noformat}
was:
{{sqlline.bat}} fails for the next cases:
1. Specified file in the argument:
{noformat}
apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -f /tmp/q.sql
DRILL_ARGS - " -u jdbc:drill:zk=local"
HADOOP_HOME not detected...
HBASE_HOME not detected...
Calculating Drill classpath...
Error: Could not find or load main class sqlline.SqlLine
{noformat}
2. Specified file path that contains spaces:
{noformat}
apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -f "/tmp/q q.sql"
DRILL_ARGS - " -u jdbc:drill:zk=local"
HADOOP_HOME not detected...
HBASE_HOME not detected...
Calculating Drill classpath...
q.sql""=="test" was unexpected at this time.
{noformat}
3. Specified query in the argument:
{noformat}
apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -e "select * from
sys.version"
DRILL_ARGS - " -u jdbc:drill:zk=local"
HADOOP_HOME not detected...
HBASE_HOME not detected...
Calculating Drill classpath...
* was unexpected at this time.
{noformat}
{noformat}
apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -q "select 'a'
from sys.version"
DRILL_ARGS - " -u jdbc:drill:zk=local"
HADOOP_HOME not detected...
HBASE_HOME not detected...
Calculating Drill classpath...
'a' was unexpected at this time.
{noformat}
4. Specified custom config location:
{noformat}
apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" --config=/tmp/conf
DRILL_ARGS - " -u jdbc:drill:zk=local"
HADOOP_HOME not detected...
HBASE_HOME not detected...
Calculating Drill classpath...
Error: Could not find or load main class sqlline.SqlLine
{noformat}
5. Specified custom config location with spaces in the path:
{noformat}
apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local"
--config="/tmp/conf test"
DRILL_ARGS - " -u jdbc:drill:zk=local"
test"" was unexpected at this time.
{noformat}
6. Sqlline was run from non-bin directory:
{noformat}
apache-drill-1.15.0>bin\sqlline.bat -u "jdbc:drill:zk=local"
DRILL_ARGS - " -u jdbc:drill:zk=local"
HADOOP_HOME not detected...
HBASE_HOME not detected...
Calculating Drill classpath...
Error: Could not find or load main class sqlline.SqlLine
{noformat}
> Fix sqlline.bat issues on Windows
> -
>
> Key: DRILL-6985
> URL: https://issues.apache.org/jira/browse/DRILL-6985
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.15.0
>
[jira] [Updated] (DRILL-6985) Fix sqlline.bat issues on Windows and add drill-embedded.bat
[
https://issues.apache.org/jira/browse/DRILL-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arina Ielchiieva updated DRILL-6985:
Issue Type: Improvement (was: Bug)
> Fix sqlline.bat issues on Windows and add drill-embedded.bat
>
>
> Key: DRILL-6985
> URL: https://issues.apache.org/jira/browse/DRILL-6985
> Project: Apache Drill
> Issue Type: Improvement
>Affects Versions: 1.15.0
> Environment: Windows 10
>Reporter: Volodymyr Vysotskyi
>Assignee: Volodymyr Vysotskyi
>Priority: Major
> Labels: doc-impacting, ready-to-commit
> Fix For: 1.16.0
>
>
> *For documentation*
> {{drill-embedded.bat}} was added as handy script to Start Drill on Windows
> without passing any params.
> Please updated the following section:
> https://drill.apache.org/docs/starting-drill-on-windows/
> Other issues covered in this Jira:
> {{sqlline.bat}} fails for the next cases:
> 1. Specified file in the argument:
> {noformat}
> apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -f /tmp/q.sql
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> HADOOP_HOME not detected...
> HBASE_HOME not detected...
> Calculating Drill classpath...
> Error: Could not find or load main class sqlline.SqlLine
> {noformat}
> 2. Specified file path that contains spaces:
> {noformat}
> apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -f "/tmp/q q.sql"
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> HADOOP_HOME not detected...
> HBASE_HOME not detected...
> Calculating Drill classpath...
> q.sql""=="test" was unexpected at this time.
> {noformat}
> 3. Specified query in the argument:
> {noformat}
> apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -e "select *
> from sys.version"
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> HADOOP_HOME not detected...
> HBASE_HOME not detected...
> Calculating Drill classpath...
> * was unexpected at this time.
> {noformat}
> {noformat}
> apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -q "select 'a'
> from sys.version"
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> HADOOP_HOME not detected...
> HBASE_HOME not detected...
> Calculating Drill classpath...
> 'a' was unexpected at this time.
> {noformat}
> 4. Specified custom config location:
> {noformat}
> apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local"
> --config=/tmp/conf
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> HADOOP_HOME not detected...
> HBASE_HOME not detected...
> Calculating Drill classpath...
> Error: Could not find or load main class sqlline.SqlLine
> {noformat}
> 5. Specified custom config location with spaces in the path:
> {noformat}
> apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local"
> --config="/tmp/conf test"
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> test"" was unexpected at this time.
> {noformat}
> 6. Sqlline was run from non-bin directory:
> {noformat}
> apache-drill-1.15.0>bin\sqlline.bat -u "jdbc:drill:zk=local"
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> HADOOP_HOME not detected...
> HBASE_HOME not detected...
> Calculating Drill classpath...
> Error: Could not find or load main class sqlline.SqlLine
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (DRILL-6985) Fix sqlline.bat issues on Windows and add drill-embedded.bat
[
https://issues.apache.org/jira/browse/DRILL-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arina Ielchiieva updated DRILL-6985:
Summary: Fix sqlline.bat issues on Windows and add drill-embedded.bat
(was: Fix sqlline.bat issues on Windows)
> Fix sqlline.bat issues on Windows and add drill-embedded.bat
>
>
> Key: DRILL-6985
> URL: https://issues.apache.org/jira/browse/DRILL-6985
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.15.0
> Environment: Windows 10
>Reporter: Volodymyr Vysotskyi
>Assignee: Volodymyr Vysotskyi
>Priority: Major
> Labels: doc-impacting, ready-to-commit
> Fix For: 1.16.0
>
>
> *For documentation*
> {{drill-embedded.bat}} was added as handy script to Start Drill on Windows
> without passing any params.
> Please updated the following section:
> https://drill.apache.org/docs/starting-drill-on-windows/
> Other issues covered in this Jira:
> {{sqlline.bat}} fails for the next cases:
> 1. Specified file in the argument:
> {noformat}
> apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -f /tmp/q.sql
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> HADOOP_HOME not detected...
> HBASE_HOME not detected...
> Calculating Drill classpath...
> Error: Could not find or load main class sqlline.SqlLine
> {noformat}
> 2. Specified file path that contains spaces:
> {noformat}
> apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -f "/tmp/q q.sql"
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> HADOOP_HOME not detected...
> HBASE_HOME not detected...
> Calculating Drill classpath...
> q.sql""=="test" was unexpected at this time.
> {noformat}
> 3. Specified query in the argument:
> {noformat}
> apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -e "select *
> from sys.version"
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> HADOOP_HOME not detected...
> HBASE_HOME not detected...
> Calculating Drill classpath...
> * was unexpected at this time.
> {noformat}
> {noformat}
> apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -q "select 'a'
> from sys.version"
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> HADOOP_HOME not detected...
> HBASE_HOME not detected...
> Calculating Drill classpath...
> 'a' was unexpected at this time.
> {noformat}
> 4. Specified custom config location:
> {noformat}
> apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local"
> --config=/tmp/conf
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> HADOOP_HOME not detected...
> HBASE_HOME not detected...
> Calculating Drill classpath...
> Error: Could not find or load main class sqlline.SqlLine
> {noformat}
> 5. Specified custom config location with spaces in the path:
> {noformat}
> apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local"
> --config="/tmp/conf test"
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> test"" was unexpected at this time.
> {noformat}
> 6. Sqlline was run from non-bin directory:
> {noformat}
> apache-drill-1.15.0>bin\sqlline.bat -u "jdbc:drill:zk=local"
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> HADOOP_HOME not detected...
> HBASE_HOME not detected...
> Calculating Drill classpath...
> Error: Could not find or load main class sqlline.SqlLine
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (DRILL-6985) Fix sqlline.bat issues on Windows
[
https://issues.apache.org/jira/browse/DRILL-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arina Ielchiieva updated DRILL-6985:
Labels: doc-impacting ready-to-commit (was: ready-to-commit)
> Fix sqlline.bat issues on Windows
> -
>
> Key: DRILL-6985
> URL: https://issues.apache.org/jira/browse/DRILL-6985
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.15.0
> Environment: Windows 10
>Reporter: Volodymyr Vysotskyi
>Assignee: Volodymyr Vysotskyi
>Priority: Major
> Labels: doc-impacting, ready-to-commit
> Fix For: 1.16.0
>
>
> {{sqlline.bat}} fails for the next cases:
> 1. Specified file in the argument:
> {noformat}
> apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -f /tmp/q.sql
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> HADOOP_HOME not detected...
> HBASE_HOME not detected...
> Calculating Drill classpath...
> Error: Could not find or load main class sqlline.SqlLine
> {noformat}
> 2. Specified file path that contains spaces:
> {noformat}
> apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -f "/tmp/q q.sql"
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> HADOOP_HOME not detected...
> HBASE_HOME not detected...
> Calculating Drill classpath...
> q.sql""=="test" was unexpected at this time.
> {noformat}
> 3. Specified query in the argument:
> {noformat}
> apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -e "select *
> from sys.version"
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> HADOOP_HOME not detected...
> HBASE_HOME not detected...
> Calculating Drill classpath...
> * was unexpected at this time.
> {noformat}
> {noformat}
> apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -q "select 'a'
> from sys.version"
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> HADOOP_HOME not detected...
> HBASE_HOME not detected...
> Calculating Drill classpath...
> 'a' was unexpected at this time.
> {noformat}
> 4. Specified custom config location:
> {noformat}
> apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local"
> --config=/tmp/conf
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> HADOOP_HOME not detected...
> HBASE_HOME not detected...
> Calculating Drill classpath...
> Error: Could not find or load main class sqlline.SqlLine
> {noformat}
> 5. Specified custom config location with spaces in the path:
> {noformat}
> apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local"
> --config="/tmp/conf test"
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> test"" was unexpected at this time.
> {noformat}
> 6. Sqlline was run from non-bin directory:
> {noformat}
> apache-drill-1.15.0>bin\sqlline.bat -u "jdbc:drill:zk=local"
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> HADOOP_HOME not detected...
> HBASE_HOME not detected...
> Calculating Drill classpath...
> Error: Could not find or load main class sqlline.SqlLine
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-6980) --run regression - error when empty line or command at end of the file
[
https://issues.apache.org/jira/browse/DRILL-6980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16748033#comment-16748033
]
Volodymyr Vysotskyi commented on DRILL-6980:
[~benj641], the problem is in SqlLine:
[https://github.com/julianhyde/sqlline/issues/232.] It was fixed there and it
will be fixed for Drill after upgrade to SqlLine 1.7.0
> --run regression - error when empty line or command at end of the file
> --
>
> Key: DRILL-6980
> URL: https://issues.apache.org/jira/browse/DRILL-6980
> Project: Apache Drill
> Issue Type: Bug
> Components: SQL Parser
>Affects Versions: 1.15.0
>Reporter: benj
>Priority: Minor
>
> When using --run like
> {code:java}
> bin/drill-embedded --run="myfile.req"
> {code}
> If "myfile.req" contains extra lines (empty or comment) after the last SQL
> DRILL request, an error appear.
> {code:java}
> Error: PARSE ERROR: Encountered "" at line 1, column 4.
> {code}
> Note that empty lines or comment lines in the middle of the file (ie between
> 2 DRILL requests or at the beginning of the file) don't make any problem.
> This problem appeared in 1.15.0 did not exists in 1.14.0
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (DRILL-6989) Upgrade to SqlLine 1.7.0
Arina Ielchiieva created DRILL-6989: --- Summary: Upgrade to SqlLine 1.7.0 Key: DRILL-6989 URL: https://issues.apache.org/jira/browse/DRILL-6989 Project: Apache Drill Issue Type: Task Affects Versions: 1.15.0 Reporter: Arina Ielchiieva Fix For: 1.16.0 Upgrade to SqlLine 1.7.0 after its officially released. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DRILL-6987) sqlline - simple semicolon ";" with no command produce error
[
https://issues.apache.org/jira/browse/DRILL-6987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16748026#comment-16748026
]
Arina Ielchiieva commented on DRILL-6987:
-
[~benj641] you should mind that SqlLine is a framework that Drill uses. If you
find bugs in SqlLine, it's better to report them to SqlLine community rather
than to Drill project.
Link to issues in SqlLine - https://github.com/julianhyde/sqlline/issues
> sqlline - simple semicolon ";" with no command produce error
>
>
> Key: DRILL-6987
> URL: https://issues.apache.org/jira/browse/DRILL-6987
> Project: Apache Drill
> Issue Type: Bug
> Components: SQL Parser
>Affects Versions: 1.15.0
>Reporter: benj
>Priority: Minor
>
> In sqlline, a single semicolon (or space(s) followed by semicolon) - "*[
> ]*;*" - produce an error
> {code:java}
> ;
> Error: PARSE ERROR: Encountered "" at line 0, column 0.
> {code}
> It's not necessary a real bug, but I think it can produce "too much" error
> for nothing.
> Don't need/want an error for an empty command.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (DRILL-6988) Utility of the too long error message when syntax error
benj created DRILL-6988:
---
Summary: Utility of the too long error message when syntax error
Key: DRILL-6988
URL: https://issues.apache.org/jira/browse/DRILL-6988
Project: Apache Drill
Issue Type: Improvement
Components: SQL Parser
Affects Versions: 1.15.0
Reporter: benj
When executing query with syntax error, the too long and useless error message
pollute log/screen and doesn't give any useful information.
Maybe a more concise error message (1-3 line max) should be enough.
{code:java}
SELECT FROM (VALUES(1));
Error: PARSE ERROR: Encountered "FROM" at line 1, column 8.
Was expecting one of:
"UNION" ...
"INTERSECT" ...
"EXCEPT" ...
"MINUS" ...
"ORDER" ...
"LIMIT" ...
"OFFSET" ...
"FETCH" ...
"STREAM" ...
"DISTINCT" ...
"ALL" ...
"*" ...
"+" ...
"-" ...
"NOT" ...
"EXISTS" ...
...
...
...
...
...
...
...
"TRUE" ...
"FALSE" ...
"UNKNOWN" ...
"NULL" ...
...
...
...
"DATE" ...
"TIME" ...
"TIMESTAMP" ...
"INTERVAL" ...
"?" ...
"CAST" ...
"EXTRACT" ...
"POSITION" ...
"CONVERT" ...
"TRANSLATE" ...
"OVERLAY" ...
"FLOOR" ...
"CEIL" ...
"CEILING" ...
"SUBSTRING" ...
"TRIM" ...
"CLASSIFIER" ...
"MATCH_NUMBER" ...
"RUNNING" ...
"PREV" ...
"NEXT" ...
...
"MULTISET" ...
"ARRAY" ...
"PERIOD" ...
"SPECIFIC" ...
...
...
...
...
...
"ABS" ...
"AVG" ...
"CARDINALITY" ...
"CHAR_LENGTH" ...
"CHARACTER_LENGTH" ...
"COALESCE" ...
"COLLECT" ...
"COVAR_POP" ...
"COVAR_SAMP" ...
"CUME_DIST" ...
"COUNT" ...
"CURRENT_DATE" ...
"CURRENT_TIME" ...
"CURRENT_TIMESTAMP" ...
"DENSE_RANK" ...
"ELEMENT" ...
"EXP" ...
"FIRST_VALUE" ...
"FUSION" ...
"GROUPING" ...
"HOUR" ...
"LAG" ...
"LEAD" ...
"LAST_VALUE" ...
"LN" ...
"LOCALTIME" ...
"LOCALTIMESTAMP" ...
"LOWER" ...
"MAX" ...
"MIN" ...
"MINUTE" ...
"MOD" ...
"MONTH" ...
"NTH_VALUE" ...
"NTILE" ...
"NULLIF" ...
"OCTET_LENGTH" ...
"PERCENT_RANK" ...
"POWER" ...
"RANK" ...
"REGR_SXX" ...
"REGR_SYY" ...
"ROW_NUMBER" ...
"SECOND" ...
"SQRT" ...
"STDDEV_POP" ...
"STDDEV_SAMP" ...
"SUM" ...
"UPPER" ...
"TRUNCATE" ...
"USER" ...
"VAR_POP" ...
"VAR_SAMP" ...
"YEAR" ...
"CURRENT_CATALOG" ...
"CURRENT_DEFAULT_TRANSFORM_GROUP" ...
"CURRENT_PATH" ...
"CURRENT_ROLE" ...
"CURRENT_SCHEMA" ...
"CURRENT_USER" ...
"SESSION_USER" ...
"SYSTEM_USER" ...
"NEW" ...
"CASE" ...
"CURRENT" ...
"CURSOR" ...
"ROW" ...
"(" ...
SQL Query SELECT FROM VALUES(1)
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (DRILL-6987) sqlline - simple semicolon ";" with no command produce error
benj created DRILL-6987:
---
Summary: sqlline - simple semicolon ";" with no command produce
error
Key: DRILL-6987
URL: https://issues.apache.org/jira/browse/DRILL-6987
Project: Apache Drill
Issue Type: Bug
Components: SQL Parser
Affects Versions: 1.15.0
Reporter: benj
In sqlline, a single semicolon (or space(s) followed by semicolon) - "*[ ]*;*"
- produce an error
{code:java}
;
Error: PARSE ERROR: Encountered "" at line 0, column 0.
{code}
It's not necessary a real bug, but I think it can produce "too much" error for
nothing.
Don't need/want an error for an empty command.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-6973) Improve --run (ability to run query and get result in a good format from command line)
[
https://issues.apache.org/jira/browse/DRILL-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16747988#comment-16747988
]
benj commented on DRILL-6973:
-
Yes, I have missed this new option of 1.15.0
(https://drill.apache.org/docs/apache-drill-1-15-0-release-notes/). Thanks.
With
{code:java}
ALTER SESSION SET `exec.query.return_result_set_for_ddl` = false;
{code}
and
{code:java}
bin/sqlline -u "..." --run="..." --silent=true --showHeader=false
--outputformat=csv
{code}
There are still the quote to manage but It already improves the possibilities
and potential.
> Improve --run (ability to run query and get result in a good format from
> command line)
> ---
>
> Key: DRILL-6973
> URL: https://issues.apache.org/jira/browse/DRILL-6973
> Project: Apache Drill
> Issue Type: Wish
>Affects Versions: 1.15.0
>Reporter: benj
>Priority: Major
>
> For a more flexible and minimalist use of DRILL, it would be useful/practical
> to have more "options" on the --run part.
> * The formatting of the output : the vertical/csv/json/table/xml... are cool
> but not simple enough to be simply piped in a shell
> * The possibility to display only the last query in the output, or at least
> the possibility to not display the output of command like ALTER
> SESSION/SYSTEM...
> * The formatting of the csv should allow NO QuoteCharacter (in
> --csvQuoteCharacter) and why not a possibility to allow QuoteCharacter in
> terms of the type or even of the data itself
> {noformat}
> Currently :
> '1','foo','Drill,baby,drill'
> Still currently (we can change the QuoteCharacter)
> @1@,@foo@,@Drill,baby,drill@
> NEW option 1 - With not quote
> 1,foo,Drill,baby,drill => Ok the third field is problematic here a problem
> but it's the responsibility of the user and he can use this option when it's
> appropriate
> NEW option 2 - function of the type
> 1,'foo','Drill,baby,drill'
> NEW option 3 - function of the data
> 1,foo,'Drill,baby,drill' => (foo doesn't need quote because it does not
> contain a separator or endofline, but the third field contain separator)
> {noformat}
> * Maybe some other ideas could be taken up from tools like psql
> Few improvements of the --run would allow more practical use case in a simple
> way
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (DRILL-6986) Table function improvements / issues (UMBRELLA JIRA)
Arina Ielchiieva created DRILL-6986: --- Summary: Table function improvements / issues (UMBRELLA JIRA) Key: DRILL-6986 URL: https://issues.apache.org/jira/browse/DRILL-6986 Project: Apache Drill Issue Type: Task Reporter: Arina Ielchiieva Umbrella Jira to keep track of all table function improvements / issues. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (DRILL-3698) Expose Show Files Command As SQL for sorting/filtering
[ https://issues.apache.org/jira/browse/DRILL-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arina Ielchiieva reassigned DRILL-3698: --- Assignee: Arina Ielchiieva > Expose Show Files Command As SQL for sorting/filtering > -- > > Key: DRILL-3698 > URL: https://issues.apache.org/jira/browse/DRILL-3698 > Project: Apache Drill > Issue Type: Improvement > Components: SQL Parser >Affects Versions: Future > Environment: All >Reporter: John Omernik >Assignee: Arina Ielchiieva >Priority: Major > Labels: features > Fix For: 1.15.0 > > > When using drill, I had a workspace setup, and I found myself using the show > files command often to find my directories etc. The thing is, the return of > show files is not ordered. And when looking at file system data there are > many possible ways to order the results for efficiency as a user. > Consider the ls command in unix; the ability to specify different sorting is > built in there. I checked out > http://drill.apache.org/docs/show-files-command/ as well as tried the > "obvious" show files order by name and that didn't work nor did I see how I > could in the documentation. > Based on a mailing list discussion there is no way to do that currently in > Drill, hence this JIRA I think just adding ORDER BY SQL methodology would be > perfect here, you have 8 fields (seen below) and ordering by any one of them, > or group of them, with ASC/DESC just like standard SQL order by would be a > huge win. > I suppose one could potentially ask for WHERE clause (filtering)too, and > maybe a select (which fieldsto display) however I am more concerned with the > order, but if I had to implement all there I could see examples below: > (All Three, select, where, and order) (I.e. after "Files" if the token isn't > WHERE or ORDER then check for the fields, if it's not a valid field list > error) > SHOW FILES name, accessTime WHERE name like '%.csv' ORDER BY name; > (Where clause and order, note the token after FILES is WHERE) > SHOW FILES WHERE name like '%.csv' ORDER BY length ASC, name DESC; > (Only Order, ORDER Is the first token after FILES) > SHOW FILES ORDER BY length ASC, name DESC > I don't think we have to grant full SQL functionality here (i.e. aggregates), > just the ability to display various fields, filter on criteria, and ordering. > If you wanted to get fancy, I suppose you could take the table and make it a > full on table, i.e. take the results make it a quick inmemory table and then > utilize the whole drill stack on it. Lots of options. I just wanted to get > this down in an email/JIRA as it was something I found myself wishing I had > over and over during data exploration. > Fields Currently Returned: > |name| isDirectory|isFile|length|owner > group|permissions|accessTime|modificationTime| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (DRILL-3698) Expose Show Files Command As SQL for sorting/filtering
[ https://issues.apache.org/jira/browse/DRILL-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arina Ielchiieva resolved DRILL-3698. - Resolution: Fixed Implemented in the scope of DRILL-6858. > Expose Show Files Command As SQL for sorting/filtering > -- > > Key: DRILL-3698 > URL: https://issues.apache.org/jira/browse/DRILL-3698 > Project: Apache Drill > Issue Type: Improvement > Components: SQL Parser >Affects Versions: Future > Environment: All >Reporter: John Omernik >Assignee: Arina Ielchiieva >Priority: Major > Labels: features > Fix For: 1.15.0 > > > When using drill, I had a workspace setup, and I found myself using the show > files command often to find my directories etc. The thing is, the return of > show files is not ordered. And when looking at file system data there are > many possible ways to order the results for efficiency as a user. > Consider the ls command in unix; the ability to specify different sorting is > built in there. I checked out > http://drill.apache.org/docs/show-files-command/ as well as tried the > "obvious" show files order by name and that didn't work nor did I see how I > could in the documentation. > Based on a mailing list discussion there is no way to do that currently in > Drill, hence this JIRA I think just adding ORDER BY SQL methodology would be > perfect here, you have 8 fields (seen below) and ordering by any one of them, > or group of them, with ASC/DESC just like standard SQL order by would be a > huge win. > I suppose one could potentially ask for WHERE clause (filtering)too, and > maybe a select (which fieldsto display) however I am more concerned with the > order, but if I had to implement all there I could see examples below: > (All Three, select, where, and order) (I.e. after "Files" if the token isn't > WHERE or ORDER then check for the fields, if it's not a valid field list > error) > SHOW FILES name, accessTime WHERE name like '%.csv' ORDER BY name; > (Where clause and order, note the token after FILES is WHERE) > SHOW FILES WHERE name like '%.csv' ORDER BY length ASC, name DESC; > (Only Order, ORDER Is the first token after FILES) > SHOW FILES ORDER BY length ASC, name DESC > I don't think we have to grant full SQL functionality here (i.e. aggregates), > just the ability to display various fields, filter on criteria, and ordering. > If you wanted to get fancy, I suppose you could take the table and make it a > full on table, i.e. take the results make it a quick inmemory table and then > utilize the whole drill stack on it. Lots of options. I just wanted to get > this down in an email/JIRA as it was something I found myself wishing I had > over and over during data exploration. > Fields Currently Returned: > |name| isDirectory|isFile|length|owner > group|permissions|accessTime|modificationTime| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DRILL-3698) Expose Show Files Command As SQL for sorting/filtering
[ https://issues.apache.org/jira/browse/DRILL-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arina Ielchiieva updated DRILL-3698: Fix Version/s: (was: Future) 1.15.0 > Expose Show Files Command As SQL for sorting/filtering > -- > > Key: DRILL-3698 > URL: https://issues.apache.org/jira/browse/DRILL-3698 > Project: Apache Drill > Issue Type: Improvement > Components: SQL Parser >Affects Versions: Future > Environment: All >Reporter: John Omernik >Priority: Major > Labels: features > Fix For: 1.15.0 > > > When using drill, I had a workspace setup, and I found myself using the show > files command often to find my directories etc. The thing is, the return of > show files is not ordered. And when looking at file system data there are > many possible ways to order the results for efficiency as a user. > Consider the ls command in unix; the ability to specify different sorting is > built in there. I checked out > http://drill.apache.org/docs/show-files-command/ as well as tried the > "obvious" show files order by name and that didn't work nor did I see how I > could in the documentation. > Based on a mailing list discussion there is no way to do that currently in > Drill, hence this JIRA I think just adding ORDER BY SQL methodology would be > perfect here, you have 8 fields (seen below) and ordering by any one of them, > or group of them, with ASC/DESC just like standard SQL order by would be a > huge win. > I suppose one could potentially ask for WHERE clause (filtering)too, and > maybe a select (which fieldsto display) however I am more concerned with the > order, but if I had to implement all there I could see examples below: > (All Three, select, where, and order) (I.e. after "Files" if the token isn't > WHERE or ORDER then check for the fields, if it's not a valid field list > error) > SHOW FILES name, accessTime WHERE name like '%.csv' ORDER BY name; > (Where clause and order, note the token after FILES is WHERE) > SHOW FILES WHERE name like '%.csv' ORDER BY length ASC, name DESC; > (Only Order, ORDER Is the first token after FILES) > SHOW FILES ORDER BY length ASC, name DESC > I don't think we have to grant full SQL functionality here (i.e. aggregates), > just the ability to display various fields, filter on criteria, and ordering. > If you wanted to get fancy, I suppose you could take the table and make it a > full on table, i.e. take the results make it a quick inmemory table and then > utilize the whole drill stack on it. Lots of options. I just wanted to get > this down in an email/JIRA as it was something I found myself wishing I had > over and over during data exploration. > Fields Currently Returned: > |name| isDirectory|isFile|length|owner > group|permissions|accessTime|modificationTime| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (DRILL-4408) re-written query projecting an aggregate on a boolean not supported by Postgres
[
https://issues.apache.org/jira/browse/DRILL-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arina Ielchiieva reassigned DRILL-4408:
---
Assignee: (was: Taras Supyk)
> re-written query projecting an aggregate on a boolean not supported by
> Postgres
> ---
>
> Key: DRILL-4408
> URL: https://issues.apache.org/jira/browse/DRILL-4408
> Project: Apache Drill
> Issue Type: Bug
> Components: Storage - JDBC
>Affects Versions: 1.5.0
>Reporter: N Campbell
>Priority: Major
>
> select rnum, c1, c2 from postgres.public.tset1 as t1 where exists ( select c1
> from postgres.public.tset2 where c1 = t1.c1 )
> Error: DATA_READ ERROR: The JDBC storage plugin failed while trying setup the
> SQL query.
> sql SELECT *
> FROM "public"."tset1"
> INNER JOIN (SELECT "c10", MIN("$f0") AS "$f1"
> FROM (SELECT "t0"."c1" AS "c10", TRUE AS "$f0"
> FROM "public"."tset2"
> INNER JOIN (SELECT "c1"
> FROM (SELECT "c1"
> FROM "public"."tset1") AS "t"
> GROUP BY "c1") AS "t0" ON "tset2"."c1" = "t0"."c1") AS "t1"
> GROUP BY "c10") AS "t2" ON "tset1"."c1" = "t2"."c10"
> plugin postgres
> Fragment 0:0
> [Error Id: a00cd446-f168-463c-b2b9-bb3d6b43e729 on centos1:31010]
> (org.postgresql.util.PSQLException) ERROR: function min(boolean) does not
> exist
> Hint: No function matches the given name and argument types. You might need
> to add explicit type casts.
> Position: 58
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse():2182
> org.postgresql.core.v3.QueryExecutorImpl.processResults():1911
> org.postgresql.core.v3.QueryExecutorImpl.execute():173
> org.postgresql.jdbc.PgStatement.execute():622
> org.postgresql.jdbc.PgStatement.executeWithFlags():458
> org.postgresql.jdbc.PgStatement.executeQuery():374
> org.apache.commons.dbcp.DelegatingStatement.executeQuery():208
> org.apache.commons.dbcp.DelegatingStatement.executeQuery():208
> org.apache.drill.exec.store.jdbc.JdbcRecordReader.setup():177
> org.apache.drill.exec.physical.impl.ScanBatch.():108
> org.apache.drill.exec.physical.impl.ScanBatch.():136
> org.apache.drill.exec.store.jdbc.JdbcBatchCreator.getBatch():40
> org.apache.drill.exec.store.jdbc.JdbcBatchCreator.getBatch():33
> org.apache.drill.exec.physical.impl.ImplCreator.getRecordBatch():147
> org.apache.drill.exec.physical.impl.ImplCreator.getChildren():170
> org.apache.drill.exec.physical.impl.ImplCreator.getRecordBatch():127
> org.apache.drill.exec.physical.impl.ImplCreator.getChildren():170
> org.apache.drill.exec.physical.impl.ImplCreator.getRecordBatch():127
> org.apache.drill.exec.physical.impl.ImplCreator.getChildren():170
> org.apache.drill.exec.physical.impl.ImplCreator.getRootExec():101
> org.apache.drill.exec.physical.impl.ImplCreator.getExec():79
> org.apache.drill.exec.work.fragment.FragmentExecutor.run():230
> org.apache.drill.common.SelfCleaningRunnable.run():38
> java.util.concurrent.ThreadPoolExecutor.runWorker():1142
> java.util.concurrent.ThreadPoolExecutor$Worker.run():617
> java.lang.Thread.run():745
> SQLState: null
> ErrorCode: 0
> create table TSET1 (RNUM integer not null , C1 integer, C2 char(3));
> create table TSET2 (RNUM integer not null , C1 integer, C2 char(3));
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-6973) Improve --run (ability to run query and get result in a good format from command line)
[
https://issues.apache.org/jira/browse/DRILL-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16747926#comment-16747926
]
Arina Ielchiieva commented on DRILL-6973:
-
{quote}
The possibility to display only the last query in the output, or at least the
possibility to not display the output of command like ALTER SESSION/SYSTEM...
{quote}
Output for DML commands can be controlled via
{{exec.query.return_result_set_for_ddl}} option.
> Improve --run (ability to run query and get result in a good format from
> command line)
> ---
>
> Key: DRILL-6973
> URL: https://issues.apache.org/jira/browse/DRILL-6973
> Project: Apache Drill
> Issue Type: Wish
>Affects Versions: 1.15.0
>Reporter: benj
>Priority: Major
>
> For a more flexible and minimalist use of DRILL, it would be useful/practical
> to have more "options" on the --run part.
> * The formatting of the output : the vertical/csv/json/table/xml... are cool
> but not simple enough to be simply piped in a shell
> * The possibility to display only the last query in the output, or at least
> the possibility to not display the output of command like ALTER
> SESSION/SYSTEM...
> * The formatting of the csv should allow NO QuoteCharacter (in
> --csvQuoteCharacter) and why not a possibility to allow QuoteCharacter in
> terms of the type or even of the data itself
> {noformat}
> Currently :
> '1','foo','Drill,baby,drill'
> Still currently (we can change the QuoteCharacter)
> @1@,@foo@,@Drill,baby,drill@
> NEW option 1 - With not quote
> 1,foo,Drill,baby,drill => Ok the third field is problematic here a problem
> but it's the responsibility of the user and he can use this option when it's
> appropriate
> NEW option 2 - function of the type
> 1,'foo','Drill,baby,drill'
> NEW option 3 - function of the data
> 1,foo,'Drill,baby,drill' => (foo doesn't need quote because it does not
> contain a separator or endofline, but the third field contain separator)
> {noformat}
> * Maybe some other ideas could be taken up from tools like psql
> Few improvements of the --run would allow more practical use case in a simple
> way
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-6974) SET/SHOW
[
https://issues.apache.org/jira/browse/DRILL-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16747923#comment-16747923
]
Arina Ielchiieva commented on DRILL-6974:
-
I think more common use case would be to have set syntax (similar as done in
SqlLine):
set `drill.exec.hashagg.fallback.enabled` -> shows current value
set `drill.exec.hashagg.fallback.enabled` = true -> updates property value
> SET/SHOW
>
>
> Key: DRILL-6974
> URL: https://issues.apache.org/jira/browse/DRILL-6974
> Project: Apache Drill
> Issue Type: Improvement
> Components: SQL Parser
>Affects Versions: 1.15.0
>Reporter: benj
>Priority: Major
>
> It's currently possible to define options with the SQL command SET
> {code:java}
> ALTER SESSION SET `drill.exec.hashagg.fallback.enabled` = true;
> {code}
> But it's not possible to simply visualize the current value of one option
> with SHOW, we have to query like
> {code:java}
> SELECT * FROM sys.options WHERE `name` =
> 'drill.exec.hashagg.fallback.enabled';
> {code}
> Why not allow a simple
> {code:java}
> SHOW 'drill.exec.hashagg.fallback.enabled';
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-6963) create/aggregate/work with array
[
https://issues.apache.org/jira/browse/DRILL-6963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16747905#comment-16747905
]
benj commented on DRILL-6963:
-
Sure, for example, PostgreSQL has these kind of functionality
* Work with array : [https://www.postgresql.org/docs/11/arrays.html]
* Aggregate in array => array_agg(exp) :
[https://www.postgresql.org/docs/11/functions-aggregate.html]
* Some array function and operators :
[https://www.postgresql.org/docs/9.1/functions-array.html]
* Some other functions like :
** {{regexp_split_to_array}}(text, pattern, flags) :
[https://www.postgresql.org/docs/current/functions-string.html]
array_agg() is useful, particularly when you group by an item and would like to
keep some information from another that has variable length / number of line
concerned in the original table is different for each group.
Example :
{code:java}
With table records
alice;1
alice;2
bob;1
bob;2
bob;3
charles;5
SELECT firstname, array_agg(DISTINCT score ORDER BY score) AS dist_scores
FROM records
GROUP BY firstname;
firstname | dist_score
- | --
alice | {1,2}
bob | {1,2,3}
charles | {5}
{code}
> create/aggregate/work with array
>
>
> Key: DRILL-6963
> URL: https://issues.apache.org/jira/browse/DRILL-6963
> Project: Apache Drill
> Issue Type: Wish
> Components: Functions - Drill
>Reporter: benj
>Priority: Major
>
> * Add the possibility to build array (like : SELECT array[a1,a2,a3...]) -
> ideally work with all types
> * Add a default array_agg (like : SELECT col1, array_agg(col2),
> array_agg(DISTINCT col2) FROM ... GROUP BY col1) ; - ideally work with all
> types
> * Add function/facilities/operator to work with array
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (DRILL-6972) Error: Could not find or load main class sqlline.SqlLine
[ https://issues.apache.org/jira/browse/DRILL-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arina Ielchiieva updated DRILL-6972: Fix Version/s: 1.16.0 > Error: Could not find or load main class sqlline.SqlLine > > > Key: DRILL-6972 > URL: https://issues.apache.org/jira/browse/DRILL-6972 > Project: Apache Drill > Issue Type: Bug > Components: Functions - Drill >Affects Versions: 1.15.0 > Environment: Windows 10 Education > 64-bit OS >Reporter: Elena Campean >Assignee: Volodymyr Vysotskyi >Priority: Major > Labels: apache, drill, start > Fix For: 1.16.0 > > > I am running in cmd, the command: sqlline.bat -u "jdbc:drill:zk=local", in > order to start drill, but I get the result: > _DRILL_ARGS - " -u jdbc:drill:zk=local"_ > _The system cannot find the path specified._ > _HADOOP_HOME not detected..._ > _HBASE_HOME not detected..._ > _Calculating Drill classpath..._ > _Error: Could not find or load main class sqlline.SqlLine_ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DRILL-6985) Fix sqlline.bat issues on Windows
[
https://issues.apache.org/jira/browse/DRILL-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arina Ielchiieva updated DRILL-6985:
Reviewer: Arina Ielchiieva
> Fix sqlline.bat issues on Windows
> -
>
> Key: DRILL-6985
> URL: https://issues.apache.org/jira/browse/DRILL-6985
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.15.0
> Environment: Windows 10
>Reporter: Volodymyr Vysotskyi
>Assignee: Volodymyr Vysotskyi
>Priority: Major
> Fix For: 1.16.0
>
>
> {{sqlline.bat}} fails for the next cases:
> 1. Specified file in the argument:
> {noformat}
> apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -f /tmp/q.sql
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> HADOOP_HOME not detected...
> HBASE_HOME not detected...
> Calculating Drill classpath...
> Error: Could not find or load main class sqlline.SqlLine
> {noformat}
> 2. Specified file path that contains spaces:
> {noformat}
> apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -f "/tmp/q q.sql"
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> HADOOP_HOME not detected...
> HBASE_HOME not detected...
> Calculating Drill classpath...
> q.sql""=="test" was unexpected at this time.
> {noformat}
> 3. Specified query in the argument:
> {noformat}
> apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -e "select *
> from sys.version"
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> HADOOP_HOME not detected...
> HBASE_HOME not detected...
> Calculating Drill classpath...
> * was unexpected at this time.
> {noformat}
> {noformat}
> apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -q "select 'a'
> from sys.version"
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> HADOOP_HOME not detected...
> HBASE_HOME not detected...
> Calculating Drill classpath...
> 'a' was unexpected at this time.
> {noformat}
> 4. Specified custom config location:
> {noformat}
> apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local"
> --config=/tmp/conf
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> HADOOP_HOME not detected...
> HBASE_HOME not detected...
> Calculating Drill classpath...
> Error: Could not find or load main class sqlline.SqlLine
> {noformat}
> 5. Specified custom config location with spaces in the path:
> {noformat}
> apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local"
> --config="/tmp/conf test"
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> test"" was unexpected at this time.
> {noformat}
> 6. Sqlline was run from non-bin directory:
> {noformat}
> apache-drill-1.15.0>bin\sqlline.bat -u "jdbc:drill:zk=local"
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> HADOOP_HOME not detected...
> HBASE_HOME not detected...
> Calculating Drill classpath...
> Error: Could not find or load main class sqlline.SqlLine
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (DRILL-6962) Function coalesce returns an Error when none of the columns in coalesce exist in a parquet file
[
https://issues.apache.org/jira/browse/DRILL-6962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arina Ielchiieva updated DRILL-6962:
Reviewer: Volodymyr Vysotskyi
> Function coalesce returns an Error when none of the columns in coalesce exist
> in a parquet file
> ---
>
> Key: DRILL-6962
> URL: https://issues.apache.org/jira/browse/DRILL-6962
> Project: Apache Drill
> Issue Type: Improvement
>Affects Versions: 1.13.0
>Reporter: Bohdan Kazydub
>Assignee: Bohdan Kazydub
>Priority: Major
> Fix For: 1.16.0
>
>
> As Drill is schema-free, COALESCE function is expected to return a result and
> not error out even if none of the columns being referred to exists in files
> being queried.
> Here is an example for 2 columns, `unk_col` and `unk_col2`, which do not
> exist in the parquet files
> {code:java}
> select coalesce(unk_col, unk_col2) from dfs.`/tmp/parquetfiles`;
> java.lang.IndexOutOfBoundsException: index (0) must be less than size (0)
> at
> org.apache.drill.shaded.guava.com.google.common.base.Preconditions.checkElementIndex(Preconditions.java:1196)
> Fragment 1:0
> [Error Id: 7b9193fb-289b-4fbf-a52a-2b93b01f0cd0 on dkvm2c:31010]
> (state=,code=0)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (DRILL-6985) Fix sqlline.bat issues on Windows
[
https://issues.apache.org/jira/browse/DRILL-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arina Ielchiieva updated DRILL-6985:
Labels: ready-to-commit (was: )
> Fix sqlline.bat issues on Windows
> -
>
> Key: DRILL-6985
> URL: https://issues.apache.org/jira/browse/DRILL-6985
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.15.0
> Environment: Windows 10
>Reporter: Volodymyr Vysotskyi
>Assignee: Volodymyr Vysotskyi
>Priority: Major
> Labels: ready-to-commit
> Fix For: 1.16.0
>
>
> {{sqlline.bat}} fails for the next cases:
> 1. Specified file in the argument:
> {noformat}
> apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -f /tmp/q.sql
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> HADOOP_HOME not detected...
> HBASE_HOME not detected...
> Calculating Drill classpath...
> Error: Could not find or load main class sqlline.SqlLine
> {noformat}
> 2. Specified file path that contains spaces:
> {noformat}
> apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -f "/tmp/q q.sql"
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> HADOOP_HOME not detected...
> HBASE_HOME not detected...
> Calculating Drill classpath...
> q.sql""=="test" was unexpected at this time.
> {noformat}
> 3. Specified query in the argument:
> {noformat}
> apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -e "select *
> from sys.version"
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> HADOOP_HOME not detected...
> HBASE_HOME not detected...
> Calculating Drill classpath...
> * was unexpected at this time.
> {noformat}
> {noformat}
> apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local" -q "select 'a'
> from sys.version"
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> HADOOP_HOME not detected...
> HBASE_HOME not detected...
> Calculating Drill classpath...
> 'a' was unexpected at this time.
> {noformat}
> 4. Specified custom config location:
> {noformat}
> apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local"
> --config=/tmp/conf
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> HADOOP_HOME not detected...
> HBASE_HOME not detected...
> Calculating Drill classpath...
> Error: Could not find or load main class sqlline.SqlLine
> {noformat}
> 5. Specified custom config location with spaces in the path:
> {noformat}
> apache-drill-1.15.0\bin>sqlline.bat -u "jdbc:drill:zk=local"
> --config="/tmp/conf test"
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> test"" was unexpected at this time.
> {noformat}
> 6. Sqlline was run from non-bin directory:
> {noformat}
> apache-drill-1.15.0>bin\sqlline.bat -u "jdbc:drill:zk=local"
> DRILL_ARGS - " -u jdbc:drill:zk=local"
> HADOOP_HOME not detected...
> HBASE_HOME not detected...
> Calculating Drill classpath...
> Error: Could not find or load main class sqlline.SqlLine
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (DRILL-6972) Error: Could not find or load main class sqlline.SqlLine
[ https://issues.apache.org/jira/browse/DRILL-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arina Ielchiieva reassigned DRILL-6972: --- Assignee: Arina Ielchiieva (was: Volodymyr Vysotskyi) > Error: Could not find or load main class sqlline.SqlLine > > > Key: DRILL-6972 > URL: https://issues.apache.org/jira/browse/DRILL-6972 > Project: Apache Drill > Issue Type: Bug > Components: Functions - Drill >Affects Versions: 1.15.0 > Environment: Windows 10 Education > 64-bit OS >Reporter: Elena Campean >Assignee: Arina Ielchiieva >Priority: Major > Labels: apache, drill, start > Fix For: 1.16.0 > > > I am running in cmd, the command: sqlline.bat -u "jdbc:drill:zk=local", in > order to start drill, but I get the result: > _DRILL_ARGS - " -u jdbc:drill:zk=local"_ > _The system cannot find the path specified._ > _HADOOP_HOME not detected..._ > _HBASE_HOME not detected..._ > _Calculating Drill classpath..._ > _Error: Could not find or load main class sqlline.SqlLine_ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (DRILL-6972) Error: Could not find or load main class sqlline.SqlLine
[ https://issues.apache.org/jira/browse/DRILL-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arina Ielchiieva reassigned DRILL-6972: --- Assignee: Volodymyr Vysotskyi (was: Arina Ielchiieva) > Error: Could not find or load main class sqlline.SqlLine > > > Key: DRILL-6972 > URL: https://issues.apache.org/jira/browse/DRILL-6972 > Project: Apache Drill > Issue Type: Bug > Components: Functions - Drill >Affects Versions: 1.15.0 > Environment: Windows 10 Education > 64-bit OS >Reporter: Elena Campean >Assignee: Volodymyr Vysotskyi >Priority: Major > Labels: apache, drill, start > Fix For: 1.16.0 > > > I am running in cmd, the command: sqlline.bat -u "jdbc:drill:zk=local", in > order to start drill, but I get the result: > _DRILL_ARGS - " -u jdbc:drill:zk=local"_ > _The system cannot find the path specified._ > _HADOOP_HOME not detected..._ > _HBASE_HOME not detected..._ > _Calculating Drill classpath..._ > _Error: Could not find or load main class sqlline.SqlLine_ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DRILL-6972) Error: Could not find or load main class sqlline.SqlLine
[ https://issues.apache.org/jira/browse/DRILL-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16747735#comment-16747735 ] Arina Ielchiieva commented on DRILL-6972: - We need to fix Windows bat script be able to run from any directory. > Error: Could not find or load main class sqlline.SqlLine > > > Key: DRILL-6972 > URL: https://issues.apache.org/jira/browse/DRILL-6972 > Project: Apache Drill > Issue Type: Bug > Components: Functions - Drill >Affects Versions: 1.15.0 > Environment: Windows 10 Education > 64-bit OS >Reporter: Elena Campean >Assignee: Volodymyr Vysotskyi >Priority: Major > Labels: apache, drill, start > Fix For: 1.16.0 > > > I am running in cmd, the command: sqlline.bat -u "jdbc:drill:zk=local", in > order to start drill, but I get the result: > _DRILL_ARGS - " -u jdbc:drill:zk=local"_ > _The system cannot find the path specified._ > _HADOOP_HOME not detected..._ > _HBASE_HOME not detected..._ > _Calculating Drill classpath..._ > _Error: Could not find or load main class sqlline.SqlLine_ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (DRILL-6972) Error: Could not find or load main class sqlline.SqlLine
[ https://issues.apache.org/jira/browse/DRILL-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arina Ielchiieva reopened DRILL-6972: - Assignee: Volodymyr Vysotskyi > Error: Could not find or load main class sqlline.SqlLine > > > Key: DRILL-6972 > URL: https://issues.apache.org/jira/browse/DRILL-6972 > Project: Apache Drill > Issue Type: Bug > Components: Functions - Drill >Affects Versions: 1.15.0 > Environment: Windows 10 Education > 64-bit OS >Reporter: Elena Campean >Assignee: Volodymyr Vysotskyi >Priority: Major > Labels: apache, drill, start > > I am running in cmd, the command: sqlline.bat -u "jdbc:drill:zk=local", in > order to start drill, but I get the result: > _DRILL_ARGS - " -u jdbc:drill:zk=local"_ > _The system cannot find the path specified._ > _HADOOP_HOME not detected..._ > _HBASE_HOME not detected..._ > _Calculating Drill classpath..._ > _Error: Could not find or load main class sqlline.SqlLine_ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
