[
https://issues.apache.org/jira/browse/KAFKA-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072727#comment-15072727
]
ASF GitHub Bot commented on KAFKA-2929:
---------------------------------------
GitHub user granthenke reopened a pull request:
https://github.com/apache/kafka/pull/616
KAFKA-2929: Migrate duplicate error mapping functionality
Deprecates ErrorMapping.scala in core in favor or Errors.java in common.
Duplicated exceptions in core are deprecated as well, to ensure the mapping
is correct.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/granthenke/kafka error-mapping
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/616.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #616
----
commit eba3b41309cf9f0436a0159dffa63fa51d89beb7
Author: Grant Henke <granthe...@gmail.com>
Date: 2015-12-16T17:55:33Z
KAFKA-2929: Migrate duplicate error mapping functionality
----
> Migrate server side error mapping functionality
> -----------------------------------------------
>
> Key: KAFKA-2929
> URL: https://issues.apache.org/jira/browse/KAFKA-2929
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.9.0.0
> Reporter: Grant Henke
> Assignee: Grant Henke
>
> Kafka common and core both have a class that maps error codes and exceptions.
> To prevent errors and issues with consistency we should migrate from
> ErrorMapping.scala in core in favor or Errors.java in common.
> When the old clients are removed ErrorMapping.scala and the old exceptions
> should be removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
