Mailing-List: contact issues-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Wed, 30 Aug 2017 18:19:00 +0000 (UTC)
From: "anishek (JIRA)" <jira@apache.org>
To: issues@hive.apache.org
Message-ID: <JIRA.13098392.1504041591000.162051.1504117140909@Atlassian.JIRA>
In-Reply-To: <JIRA.13098392.1504041591000@Atlassian.JIRA>
References: <JIRA.13098392.1504041591000@Atlassian.JIRA> <JIRA.13098392.1504041591553@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HIVE-17410) repl load task during subsequent
 DAG generation does not start from the last partition processed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 30 Aug 2017 18:19:08 -0000


    [ https://issues.apache.org/jira/browse/HIVE-17410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16147734#comment-16147734 ] 

anishek commented on HIVE-17410:
--------------------------------

* org.apache.hadoop.hive.cli.TestMiniTezCliDriver.testCliDriver[explainanalyze_2] : runs fine on local machine
* org.apache.hadoop.hive.cli.TestSparkCliDriver.org.apache.hadoop.hive.cli.TestSparkCliDriver  : seems to be a local environment problem, on local machine it takes for ever to run, running for about 20 mins now and no errors, stopped it since on the test environment it failed pretty fast.

Other tests are failures from older builds.

> repl load task during subsequent DAG generation does not start from the last partition processed
> ------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-17410
>                 URL: https://issues.apache.org/jira/browse/HIVE-17410
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2
>    Affects Versions: 3.0.0
>            Reporter: anishek
>            Assignee: anishek
>         Attachments: HIVE-17410.1.patch
>
>
> DAG generation for repl load task was to be generated dynamically such that if the load break happens at a partition load time then for subsequent runs we should start post the last partition processed.
> We currently identify the point from where we have to process the event but reinitialize the iterator to start from beginning of all partition's to process.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)