[jira] [Updated] (KAFKA-2484) Add schema projection utilities
[ https://issues.apache.org/jira/browse/KAFKA-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2484: Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 307 [https://github.com/apache/kafka/pull/307] > 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)
[jira] [Updated] (KAFKA-2484) Add schema projection utilities
[ https://issues.apache.org/jira/browse/KAFKA-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-2484: - Reviewer: Gwen Shapira > 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)
[jira] [Updated] (KAFKA-2484) Add schema projection utilities
[ https://issues.apache.org/jira/browse/KAFKA-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liquan Pei updated KAFKA-2484: -- Status: Patch Available (was: In Progress) > 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)
