You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Ewen Cheslack-Postava (JIRA)" <ji...@apache.org> on 2016/11/29 23:32:58 UTC

[jira] [Resolved] (KAFKA-4397) Refactor Connect backing stores for thread-safety

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

Ewen Cheslack-Postava resolved KAFKA-4397.
------------------------------------------
    Resolution: Fixed

Issue resolved by pull request 2123
[https://github.com/apache/kafka/pull/2123]

> Refactor Connect backing stores for thread-safety
> -------------------------------------------------
>
>                 Key: KAFKA-4397
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4397
>             Project: Kafka
>          Issue Type: Improvement
>          Components: KafkaConnect
>    Affects Versions: 0.10.1.0
>            Reporter: Konstantine Karantasis
>            Assignee: Konstantine Karantasis
>            Priority: Minor
>             Fix For: 0.10.2.0
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> In Kafka Connect there has been already significant provisioning for multi-threaded execution with respect to classes implementing backing store interfaces. 
> A requirement for 
> [KAFKA-3008|https://issues.apache.org/jira/browse/KAFKA-3008] is to tighten thread-safety guarantees in these implementations, especially for ConfigBackingStore and StatusBackingStore, and this will be the focus of the current ticket. 
>  



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