kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ewen Cheslack-Postava (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (KAFKA-4579) Schema Registry client should have a proper caching mechanism for schema IDs
Date Tue, 03 Jan 2017 23:59:58 GMT

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

Ewen Cheslack-Postava resolved KAFKA-4579.
------------------------------------------
    Resolution: Invalid
      Assignee: Ewen Cheslack-Postava

Closing as this should be filed against the schema-registry project.

> Schema Registry client should have a proper caching mechanism for schema IDs
> ----------------------------------------------------------------------------
>
>                 Key: KAFKA-4579
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4579
>             Project: Kafka
>          Issue Type: Bug
>          Components: clients
>    Affects Versions: 0.10.1.1
>         Environment: Kafka version: 10.0.1
> JVM: 1.8
> OS: Ubuntu 14.01 LTS
>            Reporter: Justin Manchester
>            Assignee: Ewen Cheslack-Postava
>
> Problem:
> Currently the Schema Registry client does not have a proper caching mechanism for Schema
IDs.  This regularly leads to users writing producers which do not reuses schema ID's and
which then crash with the following:
> Caused by: java.lang.IllegalStateException: Too many schema objects created 
> Suggested solution:  It would better if we had a proper caching mechanism in place to
prevent hard crashes.  This often leads to data loss, and the concept of reusing schema ID's
is not always intuitive to users.



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

Mime
View raw message