From dev-return-39771-apmail-kafka-dev-archive=kafka.apache.org@kafka.apache.org Thu Aug 27 17:58:47 2015 Return-Path: X-Original-To: apmail-kafka-dev-archive@www.apache.org Delivered-To: apmail-kafka-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7702F18851 for ; Thu, 27 Aug 2015 17:58:47 +0000 (UTC) Received: (qmail 60545 invoked by uid 500); 27 Aug 2015 17:58:46 -0000 Delivered-To: apmail-kafka-dev-archive@kafka.apache.org Received: (qmail 60450 invoked by uid 500); 27 Aug 2015 17:58:46 -0000 Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@kafka.apache.org Delivered-To: mailing list dev@kafka.apache.org Received: (qmail 60432 invoked by uid 99); 27 Aug 2015 17:58:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Aug 2015 17:58:46 +0000 Date: Thu, 27 Aug 2015 17:58:46 +0000 (UTC) From: "Ewen Cheslack-Postava (JIRA)" To: dev@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (KAFKA-2484) Add schema projection utilities MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Ewen Cheslack-Postava created KAFKA-2484: -------------------------------------------- Summary: 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: Ewen Cheslack-Postava Priority: Minor 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)