You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@carbondata.apache.org by "dhatchayani (JIRA)" <ji...@apache.org> on 2019/05/28 14:02:00 UTC

[jira] [Updated] (CARBONDATA-3393) Merge Index Job Failure should not trigger the merge index job again. Exception propagation should be decided by the User.

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

dhatchayani updated CARBONDATA-3393:
------------------------------------
    Summary: Merge Index Job Failure should not trigger the merge index job again. Exception propagation should be decided by the User.  (was: Merge Index Job Failure should not trigger the merge index job again. Exception should be propagated to the caller.)

> Merge Index Job Failure should not trigger the merge index job again. Exception propagation should be decided by the User.
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CARBONDATA-3393
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-3393
>             Project: CarbonData
>          Issue Type: Bug
>            Reporter: dhatchayani
>            Priority: Minor
>          Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> If the merge index job is failed, LOAD is also failing. Load should not consider the merge index job status to decide the LOAD status.



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