Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
I am running the tests with isMmTable returning true for most tables (except ACID, temporary tables, views, etc.).
Many tests will fail because of various expected issues with such an approach; however we can find issues in MM tables from other failures.
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 test
I'm filing jiras for some test failures that are not obvious and need an investigation later
Attachments
Attachments
Issue Links
- is depended upon by
-
-
- Closed
-