[jira] [Commented] (CARBONDATA-244) Load and delete segment by id queries giving inconsistent results when we execute parallely

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (CARBONDATA-244) Load and delete segment by id queries giving inconsistent results when we execute parallely

Akash R Nilugal (Jira)

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

ASF GitHub Bot commented on CARBONDATA-244:
-------------------------------------------

Github user sujith71955 commented on a diff in the pull request:

    https://github.com/apache/incubator-carbondata/pull/156#discussion_r79291381
 
    --- Diff: processing/src/main/java/org/apache/carbondata/lcm/status/SegmentStatusManager.java ---
    @@ -287,12 +307,18 @@ private Integer compareDateValues(Long loadValue, Long userValue) {
             }
     
           } else {
    -        LOG.error("Unable to acquire the metadata lock");
    +        String errorMsg = "Delete segment by id is failed for " + tableDetails
    +            + ". Not able to acquire the delete segment lock due to other operation running "
    --- End diff --
   
    update message, provide operation name


> Load and delete segment by id queries giving inconsistent results when we execute parallely
> -------------------------------------------------------------------------------------------
>
>                 Key: CARBONDATA-244
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-244
>             Project: CarbonData
>          Issue Type: Bug
>            Reporter: Manohar Vanam
>            Assignee: Manohar Vanam
>
> Delete segment by id behavior is inconsistent when  we Execute load and delete segment by id queries parallely,  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)