[jira] [Created] (DRILL-3225) SQL parser seems to ignore specified
Daniel Barclay (Drill) created DRILL-3225: - Summary: SQL parser seems to ignore specified Key: DRILL-3225 URL: https://issues.apache.org/jira/browse/DRILL-3225 Project: Apache Drill Issue Type: Bug Components: SQL Parser Reporter: Daniel Barclay (Drill) Assignee: Aman Sinha Drill's SQL parser and/or type processing seem to ignore the fractional seconds precision value specified in a for a datetime or interval type. In one case, a type descriptor of TIME(5) yields a RelDataType whose getFullTypeString() returns "TIME(0)". In another, a type descriptor of "INTERVAL HOUR TO SECOND(3)" yields a RelDataType whose getFullTypeString() returns "INTERVAL HOUR TO SECOND". Additionally, calling .getIntervalQualifier().getFractionalSecondPrecision( DrillRelDataTypeSystem.DRILL_REL_DATATYPE_SYSTEM ) yield 6 (a default value?) instead of 3. (This behavior was seen in INFORMATION_SCHEMA code listing data for a view created using casts with the above type descriptors.) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (DRILL-3224) DrillTestWrapper test-failure message doesn't show actual values
Daniel Barclay (Drill) created DRILL-3224:
-
Summary: DrillTestWrapper test-failure message doesn't show actual
values
Key: DRILL-3224
URL: https://issues.apache.org/jira/browse/DRILL-3224
Project: Apache Drill
Issue Type: Bug
Components: Tools, Build & Test
Reporter: Daniel Barclay (Drill)
Assignee: Steven Phillips
For at least one of the test-failure (validation) error messages from
DrillTestWrapper, the message does not include the actual values.
Note how the message below does tell you what was expected (redundant with
what's in the test source code, but still convenient), but doesn't tell you
what the test actually got (not available elsewhere (before/without debugging)).
{noformat}
java.lang.Exception: Did not find expected record in result set:
`CHARACTER_MAXIMUM_LENGTH` : -1, `COLUMN_NAME` : inttype, `NUMERIC_SCALE` : -1,
`DATA_TYPE` : INTEGER, `NUMERIC_PRECISION` : -1,
at
org.apache.drill.DrillTestWrapper.compareResults(DrillTestWrapper.java:541)
at
org.apache.drill.DrillTestWrapper.compareUnorderedResults(DrillTestWrapper.java:295)
at org.apache.drill.DrillTestWrapper.run(DrillTestWrapper.java:119)
at org.apache.drill.TestBuilder.go(TestBuilder.java:125)
at
org.apache.drill.exec.hive.TestInfoSchemaOnHiveStorage.varCharMaxLengthAndDecimalPrecisionInInfoSchema(TestInfoSchemaOnHiveStorage.java:94)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.lang.reflect.Method.invoke(Method.java:606)
at java.lang.reflect.Method.invoke(Method.java:606)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (DRILL-3223) Logical plan deserializer for a join node is broken
Piotr Sokólski created DRILL-3223:
-
Summary: Logical plan deserializer for a join node is broken
Key: DRILL-3223
URL: https://issues.apache.org/jira/browse/DRILL-3223
Project: Apache Drill
Issue Type: Bug
Reporter: Piotr Sokólski
Trying to submit a logical query through the web interface or ./bin/submit_plan
fails with an exception
bq. java.lang.IllegalArgumentException: Conflicting property-based creators:
already had [constructor for org.apache.drill.common.logical.data.Join,
annotations: {interface
com.fasterxml.jackson.annotation.JsonCreator=@com.fasterxml.jackson.annotation.JsonCreator()}],
encountered [constructor for org.apache.drill.common.logical.data.Join,
annotations: {interface
com.fasterxml.jackson.annotation.JsonCreator=@com.fasterxml.jackson.annotation.JsonCreator()}]
(Full queried plan and error message:
https://gist.github.com/pyetras/bf625b6697de62284996)
This is most likely due to the JsonCreator annotation being used in two places
in
https://github.com/apache/drill/blob/master/common/src/main/java/org/apache/drill/common/logical/data/Join.java#L52-52
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (DRILL-3222) Need a zip function to combine coordinated lists
Ted Dunning created DRILL-3222: -- Summary: Need a zip function to combine coordinated lists Key: DRILL-3222 URL: https://issues.apache.org/jira/browse/DRILL-3222 Project: Apache Drill Issue Type: Bug Reporter: Ted Dunning It is often very useful to be able to turn a pair (or more) of lists into a single list of pairs. Thus zip([a,b], [1,2]) => [[a,1], [b,2]]. The handling of short lists, more than two lists and so on is TBD, but the base function is an important one. One use case is in time series where storing times as one list and values as another is very handy but processing these results would be much better done by using flatten(zip(times, values)). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
