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 2014/06/20 00:19:24 UTC
[jira] [Updated] (DRILL-1037) TPCH Query 14 fails during
verification on a scal factor of 1GB
[ https://issues.apache.org/jira/browse/DRILL-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rahul Challapalli updated DRILL-1037:
-------------------------------------
Description:
git.commit.id.abbrev=894037a
Build # : 26145
The number of rows returned matches the expected value. However the actual data in the row does not match. Let me know if you need more information regarding data/baselines used. For scale factor 1GB, the difference seems to be ~0.1, however for scale factor 10GB the difference is more in the acceptable range (~0.0002). Below is the result from running the query against 1GB data.
****************************ACTUAL**************************
16.56229920583934
*************************EXPECTED*****************************
6.458363275377664
was:
git.commit.id.abbrev=894037a
Build # : 26145
The number of rows returned matches the expected value. However the actual data in the row does not match. Below are the failures. Let me know if you need more information regarding data/baselines used.
****************************ACTUAL**************************
TRUCK 57506 86188
REG AIR 57675 85976
*************************EXPECTED*****************************
TRUCK 62209 93246 (1 time(s))
REG AIR 62545 93026
> TPCH Query 14 fails during verification on a scal factor of 1GB
> ---------------------------------------------------------------
>
> Key: DRILL-1037
> URL: https://issues.apache.org/jira/browse/DRILL-1037
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - Flow
> Reporter: Rahul Challapalli
>
> git.commit.id.abbrev=894037a
> Build # : 26145
> The number of rows returned matches the expected value. However the actual data in the row does not match. Let me know if you need more information regarding data/baselines used. For scale factor 1GB, the difference seems to be ~0.1, however for scale factor 10GB the difference is more in the acceptable range (~0.0002). Below is the result from running the query against 1GB data.
> ****************************ACTUAL**************************
> 16.56229920583934
> *************************EXPECTED*****************************
> 6.458363275377664
--
This message was sent by Atlassian JIRA
(v6.2#6252)