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

Posted to issues@carbondata.apache.org by "Kunal Kapoor (JIRA)" <ji...@apache.org> on 2017/12/22 05:31:00 UTC

[jira] [Updated] (CARBONDATA-1928) Separate the lock property for concurrent load and others

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

Kunal Kapoor updated CARBONDATA-1928:
-------------------------------------
    Description: 
Currently the property that is used to configure the lock retry count and the interval between retries is common for all the locks.
This will be problematic when the user has configured the retries to 10/20 for concurrent loading. This property will be affecting other lock behaviours also, all other locks would have to retry for 10 times too.

  was:Currently the property that is used to configure the lock retry count and the interval between retries is common for all the locks.


> Separate the lock property for concurrent load and others
> ---------------------------------------------------------
>
>                 Key: CARBONDATA-1928
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-1928
>             Project: CarbonData
>          Issue Type: Improvement
>            Reporter: Kunal Kapoor
>            Assignee: Kunal Kapoor
>            Priority: Minor
>
> Currently the property that is used to configure the lock retry count and the interval between retries is common for all the locks.
> This will be problematic when the user has configured the retries to 10/20 for concurrent loading. This property will be affecting other lock behaviours also, all other locks would have to retry for 10 times too.



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