[
https://issues.apache.org/jira/browse/DRILL-2943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aman Sinha updated DRILL-2943:
------------------------------
Attachment: 0002-DRILL-2943-Parse-uppercase-E-for-scientific-notation.patch
Thanks for the review. Fixed the precedence bug and added expr parser specific
unit tests. Took out the order-by test but will suggest QA add some functional
tests.
> Drill parsing error during deserialization for an Order-By
> ----------------------------------------------------------
>
> Key: DRILL-2943
> URL: https://issues.apache.org/jira/browse/DRILL-2943
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - RPC
> Affects Versions: 0.9.0
> Reporter: Aman Sinha
> Assignee: Aman Sinha
> Fix For: 1.0.0
>
> Attachments:
> 0001-DRILL-2943-Parse-uppercase-E-for-scientific-notation.patch,
> 0002-DRILL-2943-Parse-uppercase-E-for-scientific-notation.patch
>
>
> When doing an order-by of values that have a multiplicative floating-point
> constant, the jackson deserialization errors out due to the 'E' in the
> exponent representation.
> {code}
> alter session set `planner.slice_target` = 1;
> select c_acctbal * 0.0001 as x from cp.`tpch/customer.parquet` order by x;
> {code}
> {code}
> Caused by: com.fasterxml.jackson.databind.JsonMappingException: Expression
> has syntax error! line 1:25:mismatched input 'E' expecting CParen (through
> reference chain: java.util.ArrayList[0])
>
> com.fasterxml.jackson.databind.JsonMappingException.wrapWithPath(JsonMappingException.java:210)
> ~[jackson-databind-2.4.3.jar:2.4.3]
>
> com.fasterxml.jackson.databind.JsonMappingException.wrapWithPath(JsonMappingException.java:189)
> ~[jackson-databind-2.4.3.jar:2.4.3]
>
> com.fasterxml.jackson.databind.deser.std.CollectionDeserializer.deserialize(CollectionDeserializer.java:249)
> ~[jackson-databind-2.4.3.jar:2.4.3]
>
> com.fasterxml.jackson.databind.deser.std.CollectionDeserializer.deserialize(CollectionDeserializer.java:206)
> ~[jackson-databind-2.4.3.jar:2.4.3]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)