hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Shelukhin (JIRA)" <>
Subject [jira] [Updated] (HIVE-14990) run all tests for MM tables and fix the issues that are found
Date Fri, 24 Feb 2017 01:21:44 GMT


Sergey Shelukhin updated HIVE-14990:
    Attachment: HIVE-14990.14.patch

The patch again, after fixing a bug introduced during the recent merge

> run all tests for MM tables and fix the issues that are found
> -------------------------------------------------------------
>                 Key: HIVE-14990
>                 URL:
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>         Attachments: HIVE-14990.01.patch, HIVE-14990.02.patch, HIVE-14990.03.patch, HIVE-14990.04.patch,
HIVE-14990.04.patch, HIVE-14990.05.patch, HIVE-14990.05.patch, HIVE-14990.06.patch, HIVE-14990.06.patch,
HIVE-14990.07.patch, HIVE-14990.08.patch, HIVE-14990.09.patch, HIVE-14990.10.patch, HIVE-14990.10.patch,
HIVE-14990.10.patch, HIVE-14990.12.patch, HIVE-14990.13.patch, HIVE-14990.14.patch, HIVE-14990.patch
> Expected failures 
> 1) All HCat tests (cannot write MM tables via the HCat writer)
> 2) Almost all merge tests (alter .. concat is not supported).
> 3) Tests that run dfs commands with specific paths (path changes).
> 4) Truncate column (not supported).
> 5) Describe formatted will have the new table fields in the output (before merging MM
with ACID).
> 6) Many tests w/explain extended - diff in partition "base file name" (path changes).
> 7) TestTxnCommands - all the conversion tests, as they check for bucket count using file
lists (path changes).
> 8) HBase metastore tests cause methods are not implemented.
> 9) Some load and ExIm tests that export a table and then rely on specific path for load
(path changes).
> 10) Bucket map join/etc. - diffs; disabled the optimization for MM tables due to how
it accounts for buckets
> 11) rand - different results due to different sequence of processing.
> 12) many (not all i.e. not the ones with just one insert) tests that have stats output,
such as file count, for obvious reasons
> 13) materialized views, not handled by design - the test check erroneously makes them
"mm", no easy way to tell them apart, I don't want to plumb more stuff thru just for this
> I'm filing jiras for some test failures that are not obvious and need an investigation

This message was sent by Atlassian JIRA

View raw message