[
https://issues.apache.org/jira/browse/HIVE-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Sichi updated HIVE-1600:
-----------------------------
Summary: need to sort hook input/output lists for test result
determinism (was: need to support hook input/output lists for test result
determinism)
Description:
Begin forwarded message:
From: Ning Zhang <nzh...@facebook.com>
Date: August 26, 2010 2:47:26 PM PDT
To: John Sichi <jsi...@facebook.com>
Cc: "hive-dev@hadoop.apache.org" <hive-dev@hadoop.apache.org>
Subject: Re: failure in load_dyn_part1.q
Yes I saw this error before but if it does not repro. So it's probably an
ordering issue in POSTHOOK.
On Aug 26, 2010, at 2:39 PM, John Sichi wrote:
I'm seeing this failure due to a result diff when running tests on latest trunk:
POSTHOOK: Input: defa...@srcpart@ds=2008-04-08/hr=12
POSTHOOK: Input: defa...@srcpart@ds=2008-04-09/hr=11
POSTHOOK: Input: defa...@srcpart@ds=2008-04-09/hr=12
-POSTHOOK: Output: defa...@nzhang_part2@ds=2008-12-31/hr=11
-POSTHOOK: Output: defa...@nzhang_part2@ds=2008-12-31/hr=12
POSTHOOK: Output: defa...@nzhang_part1@ds=2008-04-08/hr=11
POSTHOOK: Output: defa...@nzhang_part1@ds=2008-04-08/hr=12
+POSTHOOK: Output: defa...@nzhang_part2@ds=2008-12-31/hr=11
+POSTHOOK: Output: defa...@nzhang_part2@ds=2008-12-31/hr=12
Did something change recently? Or are we missing a Java-level sort on the
input/output list for determinism?
JVS
was:
Begin forwarded message:
From: Ning Zhang <nzh...@facebook.com>
Date: August 26, 2010 2:47:26 PM PDT
To: John Sichi <jsi...@facebook.com>
Cc: "hive-dev@hadoop.apache.org" <hive-dev@hadoop.apache.org>
Subject: Re: failure in load_dyn_part1.q
Yes I saw this error before but if it does not repro. So it's probably an
ordering issue in POSTHOOK.
On Aug 26, 2010, at 2:39 PM, John Sichi wrote:
I'm seeing this failure due to a result diff when running tests on latest trunk:
POSTHOOK: Input: defa...@srcpart@ds=2008-04-08/hr=12
POSTHOOK: Input: defa...@srcpart@ds=2008-04-09/hr=11
POSTHOOK: Input: defa...@srcpart@ds=2008-04-09/hr=12
-POSTHOOK: Output: defa...@nzhang_part2@ds=2008-12-31/hr=11
-POSTHOOK: Output: defa...@nzhang_part2@ds=2008-12-31/hr=12
POSTHOOK: Output: defa...@nzhang_part1@ds=2008-04-08/hr=11
POSTHOOK: Output: defa...@nzhang_part1@ds=2008-04-08/hr=12
+POSTHOOK: Output: defa...@nzhang_part2@ds=2008-12-31/hr=11
+POSTHOOK: Output: defa...@nzhang_part2@ds=2008-12-31/hr=12
Did something change recently? Or are we missing a Java-level sort on the
input/output list for determinism?
JVS
> need to sort hook input/output lists for test result determinism
> ----------------------------------------------------------------
>
> Key: HIVE-1600
> URL: https://issues.apache.org/jira/browse/HIVE-1600
> Project: Hadoop Hive
> Issue Type: Bug
> Components: Testing Infrastructure
> Affects Versions: 0.6.0
> Reporter: John Sichi
> Assignee: John Sichi
> Fix For: 0.7.0
>
>
> Begin forwarded message:
> From: Ning Zhang <nzh...@facebook.com>
> Date: August 26, 2010 2:47:26 PM PDT
> To: John Sichi <jsi...@facebook.com>
> Cc: "hive-dev@hadoop.apache.org" <hive-dev@hadoop.apache.org>
> Subject: Re: failure in load_dyn_part1.q
> Yes I saw this error before but if it does not repro. So it's probably an
> ordering issue in POSTHOOK.
> On Aug 26, 2010, at 2:39 PM, John Sichi wrote:
> I'm seeing this failure due to a result diff when running tests on latest
> trunk:
> POSTHOOK: Input: defa...@srcpart@ds=2008-04-08/hr=12
> POSTHOOK: Input: defa...@srcpart@ds=2008-04-09/hr=11
> POSTHOOK: Input: defa...@srcpart@ds=2008-04-09/hr=12
> -POSTHOOK: Output: defa...@nzhang_part2@ds=2008-12-31/hr=11
> -POSTHOOK: Output: defa...@nzhang_part2@ds=2008-12-31/hr=12
> POSTHOOK: Output: defa...@nzhang_part1@ds=2008-04-08/hr=11
> POSTHOOK: Output: defa...@nzhang_part1@ds=2008-04-08/hr=12
> +POSTHOOK: Output: defa...@nzhang_part2@ds=2008-12-31/hr=11
> +POSTHOOK: Output: defa...@nzhang_part2@ds=2008-12-31/hr=12
> Did something change recently? Or are we missing a Java-level sort on the
> input/output list for determinism?
> JVS
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
