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

ASF GitHub Bot commented on KAFKA-2484:
---------------------------------------

GitHub user Ishiihara opened a pull request:

    https://github.com/apache/kafka/pull/307

    KAFKA-2484: Add schema projection utilities

    This PR adds schema projection utilities to copycat. 

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/Ishiihara/kafka schema-projection

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/307.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 #307
    
----
commit 9747208fead30dcaed5295f674650b61cce25977
Author: Liquan Pei <liquan...@gmail.com>
Date:   2015-10-14T01:16:32Z

    Add schema projection utilities

----


> Add schema projection utilities
> -------------------------------
>
>                 Key: KAFKA-2484
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2484
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: copycat
>            Reporter: Ewen Cheslack-Postava
>            Assignee: Liquan Pei
>            Priority: Minor
>             Fix For: 0.9.0.0
>
>
> Since Copycat has support for versioned schemas and connectors may encounter 
> different versions of the same schema, it will be useful for some connectors 
> to be able to project between different versions of a schema, or have an 
> automatic way to try to project to a target schema (e.g. an existing database 
> table the connector is trying to write data to).
> These utilities should be pretty small because the complex types we support 
> are fairly limited. The primary code required will be for Structs. However, 
> we should take care in designing these utilities since there may be 
> performance implications. For example, when projecting between two schemas, 
> it would be better to come up with a plan object that can efficiently perform 
> the project and be able to reuse that plan many times.



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

Reply via email to