You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2018/04/17 01:32:00 UTC

[jira] [Resolved] (HIVE-19139) Hive.getValidPartitionsInPath() issue

     [ https://issues.apache.org/jira/browse/HIVE-19139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergey Shelukhin resolved HIVE-19139.
-------------------------------------
    Resolution: Not A Problem

This should be fixed as part of actually adding multi statement txns :)

> Hive.getValidPartitionsInPath() issue
> -------------------------------------
>
>                 Key: HIVE-19139
>                 URL: https://issues.apache.org/jira/browse/HIVE-19139
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Transactions
>            Reporter: Eugene Koifman
>            Priority: Major
>
> this method looks like this.  This will not work for multi-stmt txns since each statement uses the same writeId but different statementId.
> {noformat}
> // The non-MM path only finds new partitions, as it is looking at the temp path.
> // To produce the same effect, we will find all the partitions affected by this txn ID.
> // Note: we ignore the statement ID here, because it's currently irrelevant for MoveTask
> // where this is used; we always want to load everything; also the only case where
> // we have multiple statements anyway is union.
> Utilities.FILE_OP_LOGGER.trace(
>  "Looking for dynamic partitions in {} ({} levels)", loadPath, numDP);
> Path[] leafStatus = Utilities.getMmDirectoryCandidates(
>  fs, loadPath, numDP, numLB, null, writeId, -1, conf, isInsertOverwrite); 
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)