[jira] [Updated] (HIVE-784) Support uncorrelated subqueries in the WHERE clause
[ https://issues.apache.org/jira/browse/HIVE-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew Weaver updated HIVE-784: Attachment: HIVE-784.1.patch.txt Initival version. On Phabricator at https://reviews.facebook.net/D11541. > Support uncorrelated subqueries in the WHERE clause > --- > > Key: HIVE-784 > URL: https://issues.apache.org/jira/browse/HIVE-784 > Project: Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Ning Zhang >Assignee: Matthew Weaver > Attachments: HIVE-784.1.patch.txt > > > Hive currently only support views in the FROM-clause, some Facebook use cases > suggest that Hive should support subqueries such as those connected by > IN/EXISTS in the WHERE-clause. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-784) Support uncorrelated subqueries in the WHERE clause
[ https://issues.apache.org/jira/browse/HIVE-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew Weaver updated HIVE-784: Status: Open (was: Patch Available) > Support uncorrelated subqueries in the WHERE clause > --- > > Key: HIVE-784 > URL: https://issues.apache.org/jira/browse/HIVE-784 > Project: Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Ning Zhang >Assignee: Matthew Weaver > > Hive currently only support views in the FROM-clause, some Facebook use cases > suggest that Hive should support subqueries such as those connected by > IN/EXISTS in the WHERE-clause. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-784) Support uncorrelated subqueries in the WHERE clause
[ https://issues.apache.org/jira/browse/HIVE-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew Weaver updated HIVE-784: Release Note: Not ready for release Status: Patch Available (was: In Progress) Support subqueries for 'WHERE IN ()', initial version. This is an initial implementation, not ready for submission (details below). Nevertheless I would welcome comments on the approach. - ASTRewriter.inSubqueryToJoin(). Currently is called right after parsing, but will probably have to move later for proper alias generation. - This early version hard-codes a generated alias "t2" for subquery. To fix, with guarantee of unique alias, will require moving the rewrite into SemanticAnalyzer.analyzeInternal() after getMetaData(). - Currently only handles a top-level occurrence of WHERE IN (). Any nested occurrences will fail. > Support uncorrelated subqueries in the WHERE clause > --- > > Key: HIVE-784 > URL: https://issues.apache.org/jira/browse/HIVE-784 > Project: Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Ning Zhang >Assignee: Matthew Weaver > > Hive currently only support views in the FROM-clause, some Facebook use cases > suggest that Hive should support subqueries such as those connected by > IN/EXISTS in the WHERE-clause. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work started] (HIVE-784) Support uncorrelated subqueries in the WHERE clause
[ https://issues.apache.org/jira/browse/HIVE-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HIVE-784 started by Matthew Weaver. > Support uncorrelated subqueries in the WHERE clause > --- > > Key: HIVE-784 > URL: https://issues.apache.org/jira/browse/HIVE-784 > Project: Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Ning Zhang >Assignee: Matthew Weaver > > Hive currently only support views in the FROM-clause, some Facebook use cases > suggest that Hive should support subqueries such as those connected by > IN/EXISTS in the WHERE-clause. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HIVE-784) Support uncorrelated subqueries in the WHERE clause
[ https://issues.apache.org/jira/browse/HIVE-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew Weaver reassigned HIVE-784: --- Assignee: Matthew Weaver (was: Ning Zhang) > Support uncorrelated subqueries in the WHERE clause > --- > > Key: HIVE-784 > URL: https://issues.apache.org/jira/browse/HIVE-784 > Project: Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Ning Zhang >Assignee: Matthew Weaver > > Hive currently only support views in the FROM-clause, some Facebook use cases > suggest that Hive should support subqueries such as those connected by > IN/EXISTS in the WHERE-clause. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-784) Support uncorrelated subqueries in the WHERE clause
[
https://issues.apache.org/jira/browse/HIVE-784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679907#comment-13679907
]
Matthew Weaver commented on HIVE-784:
-
I'm looking into uncorrelated subqueries. Will pick this up unless someone
else is actively working it.
h5. Functional Requirements
* Support {{WHERE x IN ();}}
** {{}} returns one column, any number of rows.
* Support {{WHERE x NOT IN ()}};
* Support same types of subqueries in {{HAVING}}.
** E.g.
{code:sql}
SELECT key FROM t1 GROUP BY key
HAVING COUNT(value) IN (SELECT p FROM t2); {code}
* Correlated subqueries not supported, for now at least
** But still need to check for correlation, and bail if it occurs.
** Correlated subquery:
*** A subquery that references a table that appears in a containing query
([MySQL|http://dev.mysql.com/doc/refman/5.7/en/correlated-subqueries.html]),
thus requiring subquery evaluation to look outside its scope.
*** The subquery depends on the outer query for its values, so the subquery
must be executed once for each row of the outer query. Also known as
_repeating Subqueries_.
h5. Tasks
* Rewrite {{IN ()}} as a {{LEFT SEMI JOIN}}.
** Not ready for public consumption. In particular, no check for correlated
terms.
** With test queries.
* Add check for correlated terms, return informative error message.
* Rewrite {{WHERE NOT IN ()}} as a {{LEFT OUTER JOIN}}.
** Return rows that don't match the right side
* Rewrite subqueries in {{HAVING}}, using {{LEFT SEMI JOIN}} and {{LEFT OUTER
JOIN}} as above.
> Support uncorrelated subqueries in the WHERE clause
> ---
>
> Key: HIVE-784
> URL: https://issues.apache.org/jira/browse/HIVE-784
> Project: Hive
> Issue Type: New Feature
> Components: Query Processor
>Reporter: Ning Zhang
>Assignee: Matthew Weaver
>
> Hive currently only support views in the FROM-clause, some Facebook use cases
> suggest that Hive should support subqueries such as those connected by
> IN/EXISTS in the WHERE-clause.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-4697) Subqueries with IN and NOT IN
[
https://issues.apache.org/jira/browse/HIVE-4697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew Weaver resolved HIVE-4697.
--
Resolution: Duplicate
You're right Brock, thanks for catching. I'll resolve this as duplicate and,
assuming no one else claims hive-784, pick that up.
> Subqueries with IN and NOT IN
> -
>
> Key: HIVE-4697
> URL: https://issues.apache.org/jira/browse/HIVE-4697
> Project: Hive
> Issue Type: New Feature
> Components: Query Processor
>Reporter: Matthew Weaver
>Assignee: Matthew Weaver
> Original Estimate: 840h
> Remaining Estimate: 840h
>
> h5. Functional Requirements
> * Support {{WHERE x IN ();}}
> ** {{}} returns one column, any number of rows.
> * Support {{WHERE x NOT IN ()}};
> * Support same types of subqueries in {{HAVING}}.
> ** E.g.
> {code:sql}
> SELECT key FROM t1 GROUP BY key
> HAVING COUNT(value) IN (SELECT p FROM t2); {code}
> * Correlated subqueries not supported, for now at least
> ** But still need to check for correlation, and bail if it occurs.
> ** Correlated subquery:
> *** A subquery that references a table that appears in a containing query
> ([MySQL|http://dev.mysql.com/doc/refman/5.7/en/correlated-subqueries.html]),
> thus requiring subquery evaluation to look outside its scope.
> *** The subquery depends on the outer query for its values, so the subquery
> must be executed once for each row of the outer query. Also known as
> _repeating Subqueries_.
> h5. Tasks
> * Rewrite {{IN ()}} as a {{LEFT SEMI JOIN}}.
> ** Not ready for public consumption. In particular, no check for correlated
> terms.
> ** With test queries.
> * Add check for correlated terms, return informative error message.
> * Rewrite {{WHERE NOT IN ()}} as a {{LEFT OUTER JOIN}}.
> ** Return rows that don't match the right side
> * Rewrite subqueries in {{HAVING}}, using {{LEFT SEMI JOIN}} and {{LEFT OUTER
> JOIN}} as above.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-4697) Subqueries with IN and NOT IN
Matthew Weaver created HIVE-4697:
Summary: Subqueries with IN and NOT IN
Key: HIVE-4697
URL: https://issues.apache.org/jira/browse/HIVE-4697
Project: Hive
Issue Type: New Feature
Components: Query Processor
Reporter: Matthew Weaver
Assignee: Matthew Weaver
h5. Functional Requirements
* Support {{WHERE x IN ();}}
** {{}} returns one column, any number of rows.
* Support {{WHERE x NOT IN ()}};
* Support same types of subqueries in {{HAVING}}.
** E.g.
{code:sql}
SELECT key FROM t1 GROUP BY key
HAVING COUNT(value) IN (SELECT p FROM t2); {code}
* Correlated subqueries not supported, for now at least
** But still need to check for correlation, and bail if it occurs.
** Correlated subquery:
*** A subquery that references a table that appears in a containing query
([MySQL|http://dev.mysql.com/doc/refman/5.7/en/correlated-subqueries.html]),
thus requiring subquery evaluation to look outside its scope.
*** The subquery depends on the outer query for its values, so the subquery
must be executed once for each row of the outer query. Also known as
_repeating Subqueries_.
h5. Tasks
* Rewrite {{IN ()}} as a {{LEFT SEMI JOIN}}.
** Not ready for public consumption. In particular, no check for correlated
terms.
** With test queries.
* Add check for correlated terms, return informative error message.
* Rewrite {{WHERE NOT IN ()}} as a {{LEFT OUTER JOIN}}.
** Return rows that don't match the right side
* Rewrite subqueries in {{HAVING}}, using {{LEFT SEMI JOIN}} and {{LEFT OUTER
JOIN}} as above.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HIVE-4455) HCatalog build directories get included in tar file produced by "ant tar"
[ https://issues.apache.org/jira/browse/HIVE-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew Weaver reassigned HIVE-4455: Assignee: Alan Gates (was: Matthew Weaver) Sorry, student driver. > HCatalog build directories get included in tar file produced by "ant tar" > - > > Key: HIVE-4455 > URL: https://issues.apache.org/jira/browse/HIVE-4455 > Project: Hive > Issue Type: Bug > Components: Build Infrastructure, HCatalog >Affects Versions: 0.11.0 >Reporter: Alan Gates >Assignee: Alan Gates >Priority: Blocker > Fix For: 0.11.0 > > Attachments: buildbloat.patch, HIVE-4455.patch > > > The excludes in the tar target aren't properly excluding the build > directories in HCatalog -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HIVE-4455) HCatalog build directories get included in tar file produced by "ant tar"
[ https://issues.apache.org/jira/browse/HIVE-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew Weaver reassigned HIVE-4455: Assignee: Matthew Weaver (was: Alan Gates) > HCatalog build directories get included in tar file produced by "ant tar" > - > > Key: HIVE-4455 > URL: https://issues.apache.org/jira/browse/HIVE-4455 > Project: Hive > Issue Type: Bug > Components: Build Infrastructure, HCatalog >Affects Versions: 0.11.0 >Reporter: Alan Gates >Assignee: Matthew Weaver >Priority: Blocker > Fix For: 0.11.0 > > Attachments: buildbloat.patch, HIVE-4455.patch > > > The excludes in the tar target aren't properly excluding the build > directories in HCatalog -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work stopped] (HIVE-4350) support AS keyword for table alias
[ https://issues.apache.org/jira/browse/HIVE-4350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HIVE-4350 stopped by Matthew Weaver. > support AS keyword for table alias > -- > > Key: HIVE-4350 > URL: https://issues.apache.org/jira/browse/HIVE-4350 > Project: Hive > Issue Type: Bug > Components: SQL >Affects Versions: 0.10.0, 0.11.0 >Reporter: Thejas M Nair >Assignee: Matthew Weaver > Attachments: HIVE-4350.D10503.1.patch, HIVE-4350.D10503.2.patch, > HIVE-4350.D10503.3.patch > > > SQL standard supports AS optional keyword, while creating an table alias. > http://savage.net.au/SQL/sql-92.bnf.html#table reference > Hive gives a error when the optional keyword is used - > select * from tiny as t1; > org.apache.hive.service.cli.HiveSQLException: Error while processing > statement: FAILED: ParseException line 1:19 mismatched input 'as' expecting > EOF near 'tiny' -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-4350) support AS keyword for table alias
[ https://issues.apache.org/jira/browse/HIVE-4350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13643031#comment-13643031 ] Matthew Weaver commented on HIVE-4350: -- Can you give more detail. All TestNegativeCliDriver queries pass in my runs. > support AS keyword for table alias > -- > > Key: HIVE-4350 > URL: https://issues.apache.org/jira/browse/HIVE-4350 > Project: Hive > Issue Type: Bug > Components: SQL >Affects Versions: 0.10.0, 0.11.0 >Reporter: Thejas M Nair >Assignee: Matthew Weaver > Attachments: HIVE-4350.D10503.1.patch, HIVE-4350.D10503.2.patch, > HIVE-4350.D10503.3.patch > > > SQL standard supports AS optional keyword, while creating an table alias. > http://savage.net.au/SQL/sql-92.bnf.html#table reference > Hive gives a error when the optional keyword is used - > select * from tiny as t1; > org.apache.hive.service.cli.HiveSQLException: Error while processing > statement: FAILED: ParseException line 1:19 mismatched input 'as' expecting > EOF near 'tiny' -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work started] (HIVE-4350) support AS keyword for table alias
[ https://issues.apache.org/jira/browse/HIVE-4350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HIVE-4350 started by Matthew Weaver. > support AS keyword for table alias > -- > > Key: HIVE-4350 > URL: https://issues.apache.org/jira/browse/HIVE-4350 > Project: Hive > Issue Type: Bug > Components: SQL >Affects Versions: 0.10.0, 0.11.0 >Reporter: Thejas M Nair >Assignee: Matthew Weaver > Attachments: HIVE-4350.D10503.1.patch, HIVE-4350.D10503.2.patch, > HIVE-4350.D10503.3.patch > > > SQL standard supports AS optional keyword, while creating an table alias. > http://savage.net.au/SQL/sql-92.bnf.html#table reference > Hive gives a error when the optional keyword is used - > select * from tiny as t1; > org.apache.hive.service.cli.HiveSQLException: Error while processing > statement: FAILED: ParseException line 1:19 mismatched input 'as' expecting > EOF near 'tiny' -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-4350) support AS keyword for table alias
[ https://issues.apache.org/jira/browse/HIVE-4350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew Weaver updated HIVE-4350: - Affects Version/s: 0.11.0 Release Note: Support AS keyword for table alias. Status: Patch Available (was: In Progress) > support AS keyword for table alias > -- > > Key: HIVE-4350 > URL: https://issues.apache.org/jira/browse/HIVE-4350 > Project: Hive > Issue Type: Bug > Components: SQL >Affects Versions: 0.10.0, 0.11.0 >Reporter: Thejas M Nair >Assignee: Matthew Weaver > Attachments: HIVE-4350.D10503.1.patch, HIVE-4350.D10503.2.patch, > HIVE-4350.D10503.3.patch > > > SQL standard supports AS optional keyword, while creating an table alias. > http://savage.net.au/SQL/sql-92.bnf.html#table reference > Hive gives a error when the optional keyword is used - > select * from tiny as t1; > org.apache.hive.service.cli.HiveSQLException: Error while processing > statement: FAILED: ParseException line 1:19 mismatched input 'as' expecting > EOF near 'tiny' -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work started] (HIVE-4350) support AS keyword for table alias
[ https://issues.apache.org/jira/browse/HIVE-4350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HIVE-4350 started by Matthew Weaver. > support AS keyword for table alias > -- > > Key: HIVE-4350 > URL: https://issues.apache.org/jira/browse/HIVE-4350 > Project: Hive > Issue Type: Bug > Components: SQL >Affects Versions: 0.10.0 >Reporter: Thejas M Nair >Assignee: Matthew Weaver > Attachments: HIVE-4350.D10503.1.patch > > > SQL standard supports AS optional keyword, while creating an table alias. > http://savage.net.au/SQL/sql-92.bnf.html#table reference > Hive gives a error when the optional keyword is used - > select * from tiny as t1; > org.apache.hive.service.cli.HiveSQLException: Error while processing > statement: FAILED: ParseException line 1:19 mismatched input 'as' expecting > EOF near 'tiny' -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HIVE-4333) most windowing tests fail on hadoop 2
[ https://issues.apache.org/jira/browse/HIVE-4333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew Weaver reassigned HIVE-4333: Assignee: Harish Butani (was: Matthew Weaver) > most windowing tests fail on hadoop 2 > - > > Key: HIVE-4333 > URL: https://issues.apache.org/jira/browse/HIVE-4333 > Project: Hive > Issue Type: Bug > Components: PTF-Windowing >Affects Versions: 0.11.0 >Reporter: Gunther Hagleitner >Assignee: Harish Butani > Attachments: HIVE-4333.1.patch.txt, HIVE-4333.D10389.1.patch > > > Problem is different order of results on hadoop 2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-4333) most windowing tests fail on hadoop 2
[ https://issues.apache.org/jira/browse/HIVE-4333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13634570#comment-13634570 ] Matthew Weaver commented on HIVE-4333: -- The OVER clauses don't fully specify the ordering, causing different ordering of results and different values for FIRST and LAST. The fix is just to add enough fields to guarantee an unambiguous ordering in the window. This will fix many of the queries, maybe all. > most windowing tests fail on hadoop 2 > - > > Key: HIVE-4333 > URL: https://issues.apache.org/jira/browse/HIVE-4333 > Project: Hive > Issue Type: Bug >Reporter: Gunther Hagleitner >Assignee: Matthew Weaver > > Problem is different order of results on hadoop 2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HIVE-4333) most windowing tests fail on hadoop 2
[ https://issues.apache.org/jira/browse/HIVE-4333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew Weaver reassigned HIVE-4333: Assignee: Matthew Weaver (was: Gunther Hagleitner) > most windowing tests fail on hadoop 2 > - > > Key: HIVE-4333 > URL: https://issues.apache.org/jira/browse/HIVE-4333 > Project: Hive > Issue Type: Bug >Reporter: Gunther Hagleitner >Assignee: Matthew Weaver > > Problem is different order of results on hadoop 2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3473) testNegativeCliDriver_stats_aggregator_error_1 fails
[
https://issues.apache.org/jira/browse/HIVE-3473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13621478#comment-13621478
]
Matthew Weaver commented on HIVE-3473:
--
Unable to reproduce this failure in isolation. Ashutosh reports no repros when
running the full suite, nor has this failure been seen in the last ~dozen
jenkins builds, since build #2028.
Will keep watching for another occurrence, but otherwise not actively
investigating.
> testNegativeCliDriver_stats_aggregator_error_1 fails
>
>
> Key: HIVE-3473
> URL: https://issues.apache.org/jira/browse/HIVE-3473
> Project: Hive
> Issue Type: Bug
> Components: Tests
>Reporter: Ivan Gorbachev
>Assignee: Matthew Weaver
> Labels: test-fail
>
> testNegativeCliDriver_stats_aggregator_error_1 fails with the below trace:
> {quote}
> junit.framework.AssertionFailedError: Forked Java VM exited abnormally.
> Please note the time in the report does not reflect the time until the VM
> exit.
> at
> net.sf.antcontrib.logic.ForTask.doSequentialIteration(ForTask.java:259)
> at net.sf.antcontrib.logic.ForTask.doToken(ForTask.java:268)
> at net.sf.antcontrib.logic.ForTask.doTheTasks(ForTask.java:324)
> at net.sf.antcontrib.logic.ForTask.execute(ForTask.java:244)
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HIVE-3473) testNegativeCliDriver_stats_aggregator_error_1 fails
[
https://issues.apache.org/jira/browse/HIVE-3473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew Weaver reassigned HIVE-3473:
Assignee: Matthew Weaver
> testNegativeCliDriver_stats_aggregator_error_1 fails
>
>
> Key: HIVE-3473
> URL: https://issues.apache.org/jira/browse/HIVE-3473
> Project: Hive
> Issue Type: Bug
> Components: Tests
>Reporter: Ivan Gorbachev
>Assignee: Matthew Weaver
> Labels: test-fail
>
> testNegativeCliDriver_stats_aggregator_error_1 fails with the below trace:
> {quote}
> junit.framework.AssertionFailedError: Forked Java VM exited abnormally.
> Please note the time in the report does not reflect the time until the VM
> exit.
> at
> net.sf.antcontrib.logic.ForTask.doSequentialIteration(ForTask.java:259)
> at net.sf.antcontrib.logic.ForTask.doToken(ForTask.java:268)
> at net.sf.antcontrib.logic.ForTask.doTheTasks(ForTask.java:324)
> at net.sf.antcontrib.logic.ForTask.execute(ForTask.java:244)
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3971) testNegativeCliDriver_stats_aggregator_error_1 fails transiently
[ https://issues.apache.org/jira/browse/HIVE-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619308#comment-13619308 ] Matthew Weaver commented on HIVE-3971: -- ... at HIVE-3473, linked above. > testNegativeCliDriver_stats_aggregator_error_1 fails transiently > - > > Key: HIVE-3971 > URL: https://issues.apache.org/jira/browse/HIVE-3971 > Project: Hive > Issue Type: Bug >Reporter: Gang Tim Liu >Assignee: Gang Tim Liu > Attachments: error.rtf, HIVE-3971.patch.2 > > > testNegativeCliDriver_stats_aggregator_error_1 fails transiently. > In one case (not reproducible), it fails consistently. The root-cause is > ClassNotFoundException for DummyStatsPublisher. please see attachment. > In the environment, i did a test: move DummyStatsPublisher from src/test to > src/java and the error is gone. this shows packaging is the issue. > DummyStatsPublisher is in src/test package. ClassNotFoundException is thrown > in MR task. This shows it's possible src/test package is not available in > server side build path in some cases. > Not sure it is the real and/or only root-cause since it's not always > reproducible. If all tests pass, feel it's worthy to try. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
