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

ASF GitHub Bot commented on HIVE-17410:
---------------------------------------

GitHub user anishek opened a pull request:

    https://github.com/apache/hive/pull/240

    HIVE-17410 : repl load task during subsequent DAG generation does notstart 
from the last partition processed

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/anishek/hive HIVE-17410

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/hive/pull/240.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #240
    
----
commit f9072a7f76484222f0f78398fec6138d0d0847a3
Author: Anishek Agarwal <anis...@gmail.com>
Date:   2017-08-30T00:03:39Z

    HIVE-17410 : repl load task during subsequent DAG generation does not start 
from the last partition processed

----


> 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)

Reply via email to