[
https://issues.apache.org/jira/browse/KAFKA-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712401#comment-14712401
]
Gwen Shapira commented on KAFKA-2367:
-------------------------------------
My opinions / comments on the above:
* Logical types are important (timestamp, decimals) - but can be done separately
* I don't see much value in non-ordered versions (it doesn't give you any
information you don't get from the schema itself), so an int makes more sense.
We also need to support lack of versions. While there, we should also support
lack of schema (since some connectors won't know the schema or won't care)
* If we recommend ByteBuffer, I don't know if we should offer byte[]. I don't
feel strongly either way though.
* I like the new explicit schemas! Much less error-prone.
* Follow up jira for caching, its important.
* Lack of unions is fine, IMO Avro unions are somewhat misused and we have
better support for nulls ;)
* Lack of IndexedRecord is fine given the current API.
* I agree with how you defined the default+nullable behavior and will watch out
during the review.
> Add Copycat runtime data API
> ----------------------------
>
> Key: KAFKA-2367
> URL: https://issues.apache.org/jira/browse/KAFKA-2367
> Project: Kafka
> Issue Type: Sub-task
> Components: copycat
> Reporter: Ewen Cheslack-Postava
> Assignee: Ewen Cheslack-Postava
> Fix For: 0.8.3
>
>
> Design the API used for runtime data in Copycat. This API is used to
> construct schemas and records that Copycat processes. This needs to be a
> fairly general data model (think Avro, JSON, Protobufs, Thrift) in order to
> support complex, varied data types that may be input from/output to many data
> systems.
> This should issue should also address the serialization interfaces used
> within Copycat, which translate the runtime data into serialized byte[] form.
> It is important that these be considered together because the data format can
> be used in multiple ways (records, partition IDs, partition offsets), so it
> and the corresponding serializers must be sufficient for all these use cases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
