Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Won't Fix
-
None
-
None
-
None
Description
Right now, for multi-table insertion, we will start from multiple FileSinkOperators, and break from their lowest common ancestor, adding temporary FileSinkOperator and TableScanOperators. A special case is when the LCA is a ForwardOperator, in which case we don't break it, since it's already been optimized.
However, there's a issue, considering the following plan:
... RS_0 | FOR | / \ GBY_1 GBY_2 | | ... ... | | RS_1 RS_2 | | ... ... | | FS_1 FS_2
which may result to:
RW / \ RW RW
Hence, because of the issue in HIVE-7731 and HIVE-8118, both downstream branches will get duplicated (and same) input.
Attachments
Attachments
Issue Links
- depends upon
-
HIVE-7503 Support Hive's multi-table insert query with Spark [Spark Branch]
- Resolved
- Is contained by
-
HIVE-7292 Hive on Spark
- Resolved
- is related to
-
HIVE-8207 Add .q tests for multi-table insertion [Spark Branch]
- Resolved
- relates to
-
HIVE-8242 Investigate test failures when hive.multigroupby.singlereducer and hive.optimize.multigroupby.common.distincts are set to false [Spark Branch]
- Open
- links to