Ewen Cheslack-Postava commented on KAFKA-5575:

[~rhauch] I think I didn't trigger a vote on the KIP yet though. Really I just 
grab public API changes that someone's hesitating on KIPs for and write the KIP 
because I think the 15min it takes for the simple ones isn't a big deal and 
gives the community, and especially frequent, direct contributors, a chance to 
catch issues like incompatibilities. I think a few minutes investment + a 
couple of days turn-around time for a public API change in an API that's used 
very broadly is actually quite a low cost. In this case, there's really nothing 
I can see that would be a problem beyond what's already mentioned in the KIP, 
so I think we should just move forward w/ voting and execution.

> SchemaBuilder should have a method to clone an existing Schema.
> ---------------------------------------------------------------
>                 Key: KAFKA-5575
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5575
>             Project: Kafka
>          Issue Type: Improvement
>          Components: KafkaConnect
>            Reporter: Jeremy Custenborder
>            Assignee: Jeremy Custenborder
>            Priority: Minor
>              Labels: needs-kip
> Now that Transformations have landed in Kafka Connect we should have an easy 
> way to do quick modifications to schemas. For example changing the name of a 
> schema shouldn't be much more than. I should be able to do more stuff like 
> this.
> {code:java}
> return SchemaBuilder.from(Schema.STRING_SCHEMA).name("MyNewName").build()
> {code}

This message was sent by Atlassian JIRA

Reply via email to