[jira] [Created] (DRILL-6414) Allow Case Insensitive Comparisons in Drill
Volodymyr Tkach created DRILL-6414: -- Summary: Allow Case Insensitive Comparisons in Drill Key: DRILL-6414 URL: https://issues.apache.org/jira/browse/DRILL-6414 Project: Apache Drill Issue Type: Improvement Reporter: Volodymyr Tkach Assignee: Volodymyr Tkach Lets take a case: Table t1 with column c1 having a value 'abc' For a query like below drill should treat the comparison as case insensitive and return 1 row. This is not an issue but we need to know if we can set case insensitivity at system level. select * from t1 where c1 = 'ABC' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (DRILL-6345) DRILL Query fails on Function LOG10
Volodymyr Tkach created DRILL-6345: -- Summary: DRILL Query fails on Function LOG10 Key: DRILL-6345 URL: https://issues.apache.org/jira/browse/DRILL-6345 Project: Apache Drill Issue Type: Bug Reporter: Volodymyr Tkach Assignee: Volodymyr Tkach SQL Error: SYSTEM ERROR: UnsupportedOperationException: Only Drill simple UDF can be used in interpreter mode! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (DRILL-6270) Add debug startup option flag for drill in embedded and server mode
Volodymyr Tkach created DRILL-6270: -- Summary: Add debug startup option flag for drill in embedded and server mode Key: DRILL-6270 URL: https://issues.apache.org/jira/browse/DRILL-6270 Project: Apache Drill Issue Type: Task Reporter: Volodymyr Tkach Assignee: Anton Gozhiy Add possibility to run sqlline.sh and drillbit.sh scripts with -- with standard java remote debug options with the ability to override port. Example: drillbit.sh start - 50001 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (DRILL-6257) Sqlline start command with password appears in the sqlline.log
Volodymyr Tkach created DRILL-6257:
--
Summary: Sqlline start command with password appears in the
sqlline.log
Key: DRILL-6257
URL: https://issues.apache.org/jira/browse/DRILL-6257
Project: Apache Drill
Issue Type: Bug
Reporter: Volodymyr Tkach
Assignee: Volodymyr Tkach
*Prerequisites:*
*1.* Log level is set to "all" in the conf/logback.xml:
{code:xml}
{code}
*2.* PLAIN authentication mechanism is configured:
{code:java}
security.user.auth: {
enabled: true,
packages += "org.apache.drill.exec.rpc.user.security",
impl: "pam",
pam_profiles: [ "sudo", "login" ]
}
{code}
*Steps:*
*1.* Start the drillbits
*2.* Connect by sqlline:
{noformat}
/opt/mapr/drill/drill-1.13.0/bin/sqlline -u "jdbc:drill:zk=node1:5181;" -n
user1 -p 1234
{noformat}
*3.* Use check the sqlline logs:
{noformat}
tail -F log/sqlline.log|grep 1234 -a5 -b5
{noformat}
*Expected result:* Logs shouldn't contain clear-text passwords
*Actual result:* The logs contain the sqlline start command with password:
{noformat}
# system properties
35333-"java" : {
35352-# system properties
35384:"command" : "sqlline.SqlLine -d org.apache.drill.jdbc.Driver
--maxWidth=1 --color=true -u jdbc:drill:zk=node1:5181; -n user1 -p 1234",
35535-# system properties
35567-"launcher" : "SUN_STANDARD"
35607-}
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (DRILL-6256) Remove references to java 7 from readme and other files
Volodymyr Tkach created DRILL-6256: -- Summary: Remove references to java 7 from readme and other files Key: DRILL-6256 URL: https://issues.apache.org/jira/browse/DRILL-6256 Project: Apache Drill Issue Type: Bug Reporter: Volodymyr Tkach Assignee: Volodymyr Tkach Since master branch uses jdk 8 we should remove all references to java 7. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (DRILL-6241) Saffron properties config has the excessive permissions
Volodymyr Tkach created DRILL-6241:
--
Summary: Saffron properties config has the excessive permissions
Key: DRILL-6241
URL: https://issues.apache.org/jira/browse/DRILL-6241
Project: Apache Drill
Issue Type: Bug
Reporter: Volodymyr Tkach
Assignee: Volodymyr Tkach
Current Drill config permissions:
{noformat}
ls -al ./drill-1.13.0/conf/saffron.properties
-rw-rw-r-- 1 mapr mapr 1191 Mar 12 09:36 saffron.properties
{noformat}
*Expected result:*
It should have permissions 0640
*Actual result:*
It has the permissions 0664
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (DRILL-6233) Flattening an Array column (JSON file) return no rows
Volodymyr Tkach created DRILL-6233:
--
Summary: Flattening an Array column (JSON file) return no rows
Key: DRILL-6233
URL: https://issues.apache.org/jira/browse/DRILL-6233
Project: Apache Drill
Issue Type: Bug
Affects Versions: 1.13.0
Reporter: Volodymyr Tkach
Assignee: Volodymyr Tkach
Flatten return no rows if array is empty.
{noformat}
flat.json
{
"x" : 5,
"y" : "a string",
"z" : []
}
{noformat}
folowing query returns no results:
{noformat}
0: jdbc:drill:zk=local> select flatten(z) from dfs.tmp.`flat.json`;
+-+
| EXPR$0 |
+-+
+-+
{noformat}
but has to return one row with null for flatten function
{noformat}
++---+-+
| x | y | z | EXPR$1 |
++---+-+
| 5 | a string | [] | null |
++---+-+
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (DRILL-6228) Random failures of
Volodymyr Tkach created DRILL-6228:
--
Summary: Random failures of
Key: DRILL-6228
URL: https://issues.apache.org/jira/browse/DRILL-6228
Project: Apache Drill
Issue Type: Bug
Reporter: Volodymyr Tkach
When running on jdk8 enviroment two unit tests randomly fails. To reproduce:
change @Repeat(count = 10) to 10 or more on both of them and run tests from
command line:
mvn -Dtest=TestDrillbitResilience -pl exec/java-exec test
TestDrillbitResilience.cancelAfterAllResultsProduced
TestDrillbitResilience.cancelInMiddleOfFetchingResults
{noformat}
cancelInMiddleOfFetchingResults(org.apache.drill.exec.server.TestDrillbitResilience)
Time elapsed: 10.498 sec <<< FAILURE!
java.lang.AssertionError: Query state is incorrect (expected: CANCELED, actual:
COMPLETED) AND/OR
Exception thrown: none.
at
org.apache.drill.exec.server.TestDrillbitResilience.assertStateCompleted(TestDrillbitResilience.java:543)
at
org.apache.drill.exec.server.TestDrillbitResilience.assertCancelledWithoutException(TestDrillbitResilience.java:557)
at
org.apache.drill.exec.server.TestDrillbitResilience.assertCancelledWithoutException(TestDrillbitResilience.java:564)
at
org.apache.drill.exec.server.TestDrillbitResilience.cancelInMiddleOfFetchingResults(TestDrillbitResilience.java:644)
{noformat}
{noformat}
Failed tests:
TestDrillbitResilience.cancelAfterAllResultsProduced:672->assertCancelledWithoutException:564->assertCancelledWithoutException:557->assertStateCompleted:543
Query state is incorrect (expected: CANCELED, actual: COMPLETED) AND/OR
Exception thrown: none
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (DRILL-6217) NaN/Inf: NestedLoopJoin processes NaN values incorrectly
Volodymyr Tkach created DRILL-6217:
--
Summary: NaN/Inf: NestedLoopJoin processes NaN values incorrectly
Key: DRILL-6217
URL: https://issues.apache.org/jira/browse/DRILL-6217
Project: Apache Drill
Issue Type: Bug
Reporter: Volodymyr Tkach
Assignee: Volodymyr Tkach
Attachments: ObjsX.json
*AFFECTED_FUNCTIONALITY:* INNER JOIN (nestedloopjoin)
*ISSUE_DESCRIPTION:* according to *nestedloopjoin* query result NaN != NaN,
however hashjoin / mergejoin behaves another way - NaN = NaN. As far as I
understand, nestedloopjoin should behave like hashjoin / mergejoin. *STEPS*:
- Upload the attached file to Hadoop fs (ObjsX.json);
- Setup the following system settings:
*set planner.enable_nljoin_for_scalar_only = false*
*set planner.enable_hashjoin = false*
*set planner.enable_mergejoin = false*
*set planner.enable_nestedloopjoin = true*
- Run the following sql query {code} select distinct t.name from
dfs.tmp.`ObjsX.json` t inner join dfs.tmp.`ObjsX.json` tt on t.attr4 = tt.attr4
{code}
*EXPECTED_RESULT:* It was expected to get the following result:
{code}
object1
object2
object3
object4
{code}
*ACTUAL_RESULT:* The actual result is:
{code}
object2
object3
object4
{code}
Please investigate and fix
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (DRILL-6192) Drill is vulnerable to CVE-2017-12197
Volodymyr Tkach created DRILL-6192: -- Summary: Drill is vulnerable to CVE-2017-12197 Key: DRILL-6192 URL: https://issues.apache.org/jira/browse/DRILL-6192 Project: Apache Drill Issue Type: Bug Reporter: Volodymyr Tkach Assignee: Volodymyr Tkach The current version of libpam4j bundled with MCS does not perform any authorization check. Any user with valid password could access the cluster even if the user account is disabled/password expired/'not allowed to access the service(pam_access ..)' etc.. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (DRILL-6189) Security: passwords logging and file permisions
Volodymyr Tkach created DRILL-6189:
--
Summary: Security: passwords logging and file permisions
Key: DRILL-6189
URL: https://issues.apache.org/jira/browse/DRILL-6189
Project: Apache Drill
Issue Type: Bug
Reporter: Volodymyr Tkach
Assignee: Volodymyr Tkach
*Prerequisites:*
*1.* Log level is set to "all" in the conf/logback.xml:
{code:xml}
{code}
*2.* PLAIN authentication mechanism is configured:
{code:java}
security.user.auth: {
enabled: true,
packages += "org.apache.drill.exec.rpc.user.security",
impl: "pam",
pam_profiles: [ "sudo", "login" ]
}
{code}
*Steps:*
*1.* Start the drillbits
*2.* Connect by sqlline:
{noformat}
/opt/mapr/drill/drill-1.13.0/bin/sqlline -u "jdbc:drill:zk=node1:5181;" -n
user1 -p
{noformat}
*Expected result:* Logs shouldn't contain clear-text passwords
*Actual results:* During the drillbit startup or establishing connections via
the jdbc or odbc, the following lines appear in the drillbit.log:
{noformat}
properties {
key: "password"
value: ""
}
{noformat}
Same thing happens with storage configuration data, everything, including
passwords is being logged to file.
*Another issue:*
Currently Drill config files has the permissions 0644:
{noformat}
-rw-r--r--. 1 mapr mapr 1081 Nov 16 14:42 core-site-example.xml
-rwxr-xr-x. 1 mapr mapr 1807 Dec 19 11:55 distrib-env.sh
-rw-r--r--. 1 mapr mapr 1424 Nov 16 14:42 distrib-env.sh.prejmx
-rw-r--r--. 1 mapr mapr 1942 Nov 16 14:42 drill-am-log.xml
-rw-r--r--. 1 mapr mapr 1279 Dec 19 11:55 drill-distrib.conf
-rw-r--r--. 1 mapr mapr 117 Nov 16 14:50 drill-distrib-mem-qs.conf
-rw-r--r--. 1 mapr mapr 6016 Nov 16 14:42 drill-env.sh
-rw-r--r--. 1 mapr mapr 1855 Nov 16 14:50 drill-on-yarn.conf
-rw-r--r--. 1 mapr mapr 6913 Nov 16 14:42 drill-on-yarn-example.conf
-rw-r--r--. 1 mapr mapr 1135 Dec 19 11:55 drill-override.conf
-rw-r--r--. 1 mapr mapr 7820 Nov 16 14:42 drill-override-example.conf
-rw-r--r--. 1 mapr mapr 3136 Nov 16 14:42 logback.xml
-rw-r--r--. 1 mapr mapr 668 Nov 16 14:51 warden.drill-bits.conf
-rw-r--r--. 1 mapr mapr 1581 Nov 16 14:42 yarn-client-log.xml
{noformat}
As they may contain some sensitive information, like passwords or secret keys,
they cannot be viewable to everyone. So I suggest to reduce the permissions at
least to 0640.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (DRILL-6154) NaN, Infinity issues
Volodymyr Tkach created DRILL-6154:
--
Summary: NaN, Infinity issues
Key: DRILL-6154
URL: https://issues.apache.org/jira/browse/DRILL-6154
Project: Apache Drill
Issue Type: Bug
Reporter: Volodymyr Tkach
Assignee: Volodymyr Tkach
1.Issue
*AFFECTED_VERSION:* drill-1.13.0-SNAPSHOT
*AFFECTED_FUNCTIONS:*
- *sqrt*
- *trunc*
*ISSUE_DESCRIPTION:* According to DRILL-5919/MD-2745, new json number literals
were added: *NaN, Infinity, -Infinity*. The new data types must be processed
properly by existing functions. There are a few issues:
*1. SQRT function*. Run the following test query: {code}select sqrt(Nan) NaN,
sqrt(Positive_Infinity) POS_INF, sqrt(Negative_Infinity) NEG_INF from
dfs.tmp.`PN_Inf_NaN.json`{code}
- EXPECTED_RESULT: it was expected to get the following result: _NaN, Infinity,
NaN_ (expected result is based on java Math.sqrt() method)
- ACTUAL_RESULT: the test query returned: _NaN, Infinity, Infinity_
*2. TRUNC function*. According to DRILL docs
(https://drill.apache.org/docs/math-and-trig/): _TRUNC(x, y) : Truncates x to y
decimal places. *Specifying y is optional. Default is 1*_. So, the function
must work properly without specifying *y*
However an error message appears. Run test_query: {code}select trunc(Nan) NaN,
trunc(Positive_Infinity) POS_INF, trunc(Negative_Infinity) NEG_INF from
dfs.tmp.`PN_Inf_NaN.json`{code}
- EXPECTED_RESULT: it was expected to get the following result *NaN, NaN, NaN*
- ACTUAL_RESULT: it appears the following error message: *Query Failed: An
Error Occurred org.apache.drill.common.exceptions.UserRemoteException: SYSTEM
ERROR: NumberFormatException Fragment 0:0 [Error Id:
95e01fee-7433-4b0b-b913-32358b4a8f55 on node1:31010]*
Please investigate and fix, test file attached PN_Inf_NaN.json
2. Issue
*AFFECTED_VERSION:* drill-1.13.0-SNAPSHOT
*AFFECTED_FUNCTIONALITY:* INNER JOIN
*ISSUE_DESCRIPTION:* There were added new Json data types in
MD-2745/DRILL-5919: *NaN, Infinity, -Infinity*.
During testing activities, it was detected a bit strange behavior of INNER JOIN
operator - different query results in almost the same queries.
*Query1* {code} select distinct t.name, tt.name from dfs.tmp.`ObjsX.json` t
inner join dfs.tmp.`ObjsX.json` tt on t.attr4 = tt.attr4 {code}
*Query2* {code} select distinct t.name from dfs.tmp.`ObjsX.json` t inner join
dfs.tmp.`ObjsX.json` tt on t.attr4 = tt.attr4 {code}
*Query1* differs from *Query2* by 1 columns only:
- In *Query1* - 2 columns are selected - t.name, tt.name
- In *Query2* - 1 column is selected - t.name
However *Query1*/*Query2* return completely different results:
- *Query1* returns
{code}
name name0
object2 object2
object2 object3
object2 object4
object3 object2
object3 object3
object3 object4
object4 object2
object4 object3
object4 object4
{code}
This result seems to be correct.
- *Query2* returns _*No result found*_, not expected:
*EXPECTED_RESULT:*
{code}
name
object2
object3
object4
{code}
*ACTUAL_RESULT*: {code}No result found{code}
*NB!:* the issue appears only if tables are _*JOINed by a column which contains
newly-added data types (NaN, Infinity, -Infinity)*_. The issue is not
reproducible is a user is JOINing tables by a column containing other data types
3. Issue
*AFFECTED_VERSION:* drill-1.13.0-SNAPSHOT
*AFFECTED_FUNCTIONALITY:* ORDER BY, DESC
*THIS ISSUE REFERS TO:* MD-2745
*ISSUE_DESCRIPTION:* 'ORDER BY/DESC' clause behaves in different ways when
sorting columns containing NaN values. In one case it considers NaN to be the
largest value, in another - the smallest one.
*Steps:*
- Select from the attached test file (orderBy.json, attached)
{code}SELECT name, attr4 from dfs.tmp.`orderBy.json` order by name,
attr4{code}
- Check the attached screen shot (orderByIssue.jpg):
*EXPECTED_RESULT:* It was expected the 'ORDER BY' clause to sort attr4
columns data in the same way (most probably NaN should be the largest, see *NB*)
*ACTUAL_RESULT:* attr4 column's values were sorted in different ways:
for 'obj1'/'obj3' NaN is the largest, for 'obj2'/'obj4' NaN is the smallest.
*NB:* Postgres as well as Java's sorting (Collection.sort() / Arrays.sort()
methods) treats NaN as the largest value
4. Issue
*AFFECTED_VERSION:* drill-1.13.0-SNAPSHOT
*AFFECTED_FUNCTIONALITY:* max(column_name), min(column_name),
*ISSUE_DESCRIPTION:* min/max aggregation functions return the same result if
the selected column contains NaN value.
{code}SELECT name, max(attr4), min(attr4) from dfs.tmp.`minMax.json` group by
name{code}
Result
{code}
nameMin Max
obj1NaN NaN
obj2NaN NaN
obj3NaN
[jira] [Created] (DRILL-6018) Drill can't handle NaN, Infinity literals
Volodymyr Tkach created DRILL-6018:
--
Summary: Drill can't handle NaN, Infinity literals
Key: DRILL-6018
URL: https://issues.apache.org/jira/browse/DRILL-6018
Project: Apache Drill
Issue Type: Bug
Reporter: Volodymyr Tkach
Assignee: Volodymyr Tkach
Queries like:
select sin(cast('NaN' as double)) from (values(1))
select cast('Infinity' as double)+1 from (values(1))
end up with NumberFormatException, because Drill and Calcite use BigDecimal to
handle double literals. As a solution we can add special symbols NAN, POS_INF,
NEG_INF which will represent not numeric literals.
Created [calcite jira | https://issues.apache.org/jira/browse/CALCITE-2067] for
this functionality.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (DRILL-5939) NullPointerException in convert_toJSON function
Volodymyr Tkach created DRILL-5939:
--
Summary: NullPointerException in convert_toJSON function
Key: DRILL-5939
URL: https://issues.apache.org/jira/browse/DRILL-5939
Project: Apache Drill
Issue Type: Bug
Reporter: Volodymyr Tkach
Priority: Minor
The query: `select convert_toJSON(convert_fromJSON('\{"key": "value"\}')) from
(values(1));` fails with exception.
Although, when we apply it for the data from the file from disk it succeeds.
select convert_toJSON(convert_fromJSON(columns\[0\])) from dfs.tmp.`some.csv`;
Some.csv
\{"key":"val"\},val2
{noformat}
Fragment 0:0
[Error Id: 016ca995-16f9-4eab-83c2-7679071faad4 on userf206-pc:31010]
org.apache.drill.common.exceptions.UserException: SYSTEM ERROR:
NullPointerException
Fragment 0:0
[Error Id: 016ca995-16f9-4eab-83c2-7679071faad4 on userf206-pc:31010]
at
org.apache.drill.common.exceptions.UserException$Builder.build(UserException.java:586)
~[drill-common-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at
org.apache.drill.exec.work.fragment.FragmentExecutor.sendFinalState(FragmentExecutor.java:298)
[drill-java-exec-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at
org.apache.drill.exec.work.fragment.FragmentExecutor.cleanup(FragmentExecutor.java:160)
[drill-java-exec-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at
org.apache.drill.exec.work.fragment.FragmentExecutor.run(FragmentExecutor.java:267)
[drill-java-exec-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at
org.apache.drill.common.SelfCleaningRunnable.run(SelfCleaningRunnable.java:38)
[drill-common-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[na:1.7.0_80]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[na:1.7.0_80]
at java.lang.Thread.run(Thread.java:745) [na:1.7.0_80]
Caused by: java.lang.NullPointerException: null
at
org.apache.drill.exec.expr.fn.DrillFuncHolder.addProtectedBlock(DrillFuncHolder.java:183)
~[drill-java-exec-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at
org.apache.drill.exec.expr.fn.DrillFuncHolder.generateBody(DrillFuncHolder.java:169)
~[drill-java-exec-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at
org.apache.drill.exec.expr.fn.DrillSimpleFuncHolder.renderEnd(DrillSimpleFuncHolder.java:86)
~[drill-java-exec-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at
org.apache.drill.exec.expr.EvaluationVisitor$EvalVisitor.visitFunctionHolderExpression(EvaluationVisitor.java:205)
~[drill-java-exec-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at
org.apache.drill.exec.expr.EvaluationVisitor$ConstantFilter.visitFunctionHolderExpression(EvaluationVisitor.java:1089)
~[drill-java-exec-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at
org.apache.drill.exec.expr.EvaluationVisitor$CSEFilter.visitFunctionHolderExpression(EvaluationVisitor.java:827)
~[drill-java-exec-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at
org.apache.drill.exec.expr.EvaluationVisitor$CSEFilter.visitFunctionHolderExpression(EvaluationVisitor.java:807)
~[drill-java-exec-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at
org.apache.drill.common.expression.FunctionHolderExpression.accept(FunctionHolderExpression.java:53)
~[drill-logical-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at
org.apache.drill.exec.expr.EvaluationVisitor$EvalVisitor.visitValueVectorWriteExpression(EvaluationVisitor.java:362)
~[drill-java-exec-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at
org.apache.drill.exec.expr.EvaluationVisitor$EvalVisitor.visitUnknown(EvaluationVisitor.java:344)
~[drill-java-exec-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at
org.apache.drill.exec.expr.EvaluationVisitor$ConstantFilter.visitUnknown(EvaluationVisitor.java:1339)
~[drill-java-exec-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at
org.apache.drill.exec.expr.EvaluationVisitor$CSEFilter.visitUnknown(EvaluationVisitor.java:1038)
~[drill-java-exec-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at
org.apache.drill.exec.expr.EvaluationVisitor$CSEFilter.visitUnknown(EvaluationVisitor.java:807)
~[drill-java-exec-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at
org.apache.drill.exec.expr.ValueVectorWriteExpression.accept(ValueVectorWriteExpression.java:64)
~[drill-java-exec-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at
org.apache.drill.exec.expr.EvaluationVisitor.addExpr(EvaluationVisitor.java:104)
~[drill-java-exec-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at
org.apache.drill.exec.expr.ClassGenerator.addExpr(ClassGenerator.java:335)
~[drill-java-exec-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at
org.apache.drill.exec.physical.impl.project.ProjectRecordBatch.setupNewSchemaFromInput(ProjectRecordBatch.java:476)
~[drill-java-exec-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at
[jira] [Created] (DRILL-5938) Write unit tests for math function with NaN and Infinity numbers
Volodymyr Tkach created DRILL-5938: -- Summary: Write unit tests for math function with NaN and Infinity numbers Key: DRILL-5938 URL: https://issues.apache.org/jira/browse/DRILL-5938 Project: Apache Drill Issue Type: Test Reporter: Volodymyr Tkach Priority: Minor Fix For: Future Drill math function needs to be covered with test cases when input is non-numeric numbers: NaN or Infinity. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (DRILL-5919) Add session option to allow json reader/writer to work with NaN,INF
Volodymyr Tkach created DRILL-5919: -- Summary: Add session option to allow json reader/writer to work with NaN,INF Key: DRILL-5919 URL: https://issues.apache.org/jira/browse/DRILL-5919 Project: Apache Drill Issue Type: Improvement Components: Storage - JSON Affects Versions: 1.12.0 Reporter: Volodymyr Tkach Assignee: Volodymyr Tkach Priority: Minor Add session options to allow drill working with non standard json strings number literals like: NaN, Infinity, -Infinity. By default these options will be switched off, the user will be able to toggle them during working session. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (DRILL-5910) ClassNotFoundException message enhancement
Volodymyr Tkach created DRILL-5910: -- Summary: ClassNotFoundException message enhancement Key: DRILL-5910 URL: https://issues.apache.org/jira/browse/DRILL-5910 Project: Apache Drill Issue Type: Bug Affects Versions: 1.11.0 Reporter: Volodymyr Tkach Assignee: Volodymyr Tkach -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (DRILL-5895) Fix unit tests for mongo storage plugin
Volodymyr Tkach created DRILL-5895:
--
Summary: Fix unit tests for mongo storage plugin
Key: DRILL-5895
URL: https://issues.apache.org/jira/browse/DRILL-5895
Project: Apache Drill
Issue Type: Bug
Reporter: Volodymyr Tkach
Assignee: Volodymyr Tkach
Fix For: Future
All tests pass but run fails with:
{noformat}
[mongod output] Exception in thread "Thread-25"
java.lang.IllegalStateException: Couldn't kill mongod process!
Something bad happend. We couldn't kill mongod process, and tried a lot.
If you want this problem solved you can help us if you open a new issue.
Follow this link:
https://github.com/flapdoodle-oss/de.flapdoodle.embed.mongo/issues
Thank you:)
at
de.flapdoodle.embed.process.runtime.ProcessControl.waitForProcessGotKilled(ProcessControl.java:192)
at
de.flapdoodle.embed.process.runtime.ProcessControl.stop(ProcessControl.java:76)
at
de.flapdoodle.embed.process.runtime.AbstractProcess.stopProcess(AbstractProcess.java:189)
at
de.flapdoodle.embed.mongo.AbstractMongoProcess.stopInternal(AbstractMongoProcess.java:117)
at
de.flapdoodle.embed.process.runtime.AbstractProcess.stop(AbstractProcess.java:170)
at
de.flapdoodle.embed.process.runtime.Executable.stop(Executable.java:73)
at
de.flapdoodle.embed.process.runtime.Executable$JobKiller.run(Executable.java:90)
at java.lang.Thread.run(Thread.java:745)
Exception in thread "Thread-13" java.lang.IllegalStateException: Couldn't kill
mongod process!
Something bad happend. We couldn't kill mongod process, and tried a lot.
If you want this problem solved you can help us if you open a new issue.
Follow this link:
https://github.com/flapdoodle-oss/de.flapdoodle.embed.mongo/issues
Thank you:)
at
de.flapdoodle.embed.process.runtime.ProcessControl.waitForProcessGotKilled(ProcessControl.java:192)
at
de.flapdoodle.embed.process.runtime.ProcessControl.stop(ProcessControl.java:76)
at
de.flapdoodle.embed.process.runtime.AbstractProcess.stopProcess(AbstractProcess.java:189)
at
de.flapdoodle.embed.mongo.AbstractMongoProcess.stopInternal(AbstractMongoProcess.java:117)
at
de.flapdoodle.embed.process.runtime.AbstractProcess.stop(AbstractProcess.java:170)
at
de.flapdoodle.embed.process.runtime.Executable.stop(Executable.java:73)
at
de.flapdoodle.embed.process.runtime.Executable$JobKiller.run(Executable.java:90)
at java.lang.Thread.run(Thread.java:745)
Results :
Tests in error:
MongoTestSuit.tearDownCluster:260 » IllegalState Couldn't kill mongod
process!...
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
