You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Rahul Challapalli (JIRA)" <ji...@apache.org> on 2016/09/29 21:03:20 UTC
[jira] [Updated] (DRILL-4918) Adding 2 dates results in
AssertionError: Multiple functions with best cost found
[ https://issues.apache.org/jira/browse/DRILL-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rahul Challapalli updated DRILL-4918:
-------------------------------------
Description:
git.commit.id.abbrev=2295715
The below query fails
{code}
select l_commitdate+l_receiptdate from cp.`tpch/lineitem.parquet`;
Error: SYSTEM ERROR: AssertionError: Multiple functions with best cost found
Fragment 0:0
[Error Id: 983983bd-73e3-45c8-a377-e7022a5899c7 on qa-node182.qa.lab:31010] (state=,code=0)
{code}
The more likely scenario is that this operation is not supported. Atleast we should throw a proper error message. I attached the error from the logs
was:
git.commit.id.abbrev=2295715
The below query fails
{code}
select l_commitdate+l_receiptdate from cp.`tpch/lineitem.parquet`;
Error: SYSTEM ERROR: AssertionError: Multiple functions with best cost found
Fragment 0:0
[Error Id: 983983bd-73e3-45c8-a377-e7022a5899c7 on qa-node182.qa.lab:31010] (state=,code=0)
{code}
I attached the error from the logs
> Adding 2 dates results in AssertionError: Multiple functions with best cost found
> ---------------------------------------------------------------------------------
>
> Key: DRILL-4918
> URL: https://issues.apache.org/jira/browse/DRILL-4918
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - Data Types, Functions - Drill
> Reporter: Rahul Challapalli
>
> git.commit.id.abbrev=2295715
> The below query fails
> {code}
> select l_commitdate+l_receiptdate from cp.`tpch/lineitem.parquet`;
> Error: SYSTEM ERROR: AssertionError: Multiple functions with best cost found
> Fragment 0:0
> [Error Id: 983983bd-73e3-45c8-a377-e7022a5899c7 on qa-node182.qa.lab:31010] (state=,code=0)
> {code}
> The more likely scenario is that this operation is not supported. Atleast we should throw a proper error message. I attached the error from the logs
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)