[jira] [Comment Edited] (KAFKA-7315) Streams serialization docs contain a broken link for Avro
[ https://issues.apache.org/jira/browse/KAFKA-7315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587602#comment-16587602 ] Jordan Moore edited comment on KAFKA-7315 at 8/21/18 3:38 PM: -- I understand the "Serde" class itself is a Streams class. I use the SerDe term loosely to mean serializer/deserializer. I wasn't trying to imply that there needed to be "how to (de)serialize to datatype X,Y,Z", maybe just mention some popular options, and say something along the lines of "as long one can translate a datatype into bytes, it can be transferred with Kafka." My main point was that the while the Serde class itself is specific to Streams API, the mention of custom Serializers (and the SerDe classes that are already implemented, which wrap their respective serializer&deserializers) seems "hidden" under the Streams docs page; on the "front page", I'm only able to find the term "serializer" in the config sections, and it's not really clear what needs to be done to implement a custom one. E.g. saying "a class that implements the org.apache.kafka.common.serialization.Serializer interface", 1) really only applies to JVM-based clients, 2) doesn't specifically mention that the Serializer needs to return byte[] and Deserializer converts from byte[] Like I said, though, maybe that is implicitly said/known already in some other section of the docs? was (Author: cricket007): I understand the "Serde" class itself is a Streams class. I use the SerDe term loosely to mean serializer/deserializer. I wasn't trying to imply that there needed to be "how to (de)serialize to datatype X,Y,Z", maybe just mention some popular options. My main point was that the while the Serde class itself is specific to Streams API, the mention of custom Serializers (and the SerDe classes that are already implemented, which wrap their respective serializer&deserializers) seems "hidden" under the Streams docs page; on the "front page", I'm only able to find the term "serializer" in the config sections, and it's not really clear what needs to be done to implement a custom one. E.g. saying "a class that implements the org.apache.kafka.common.serialization.Serializer interface", 1) really only applies to JVM-based clients, 2) doesn't specifically mention that the Serializer needs to return byte[] and Deserializer converts from byte[] Like I said, though, maybe that is implicitly said/known already in some other section of the docs? > Streams serialization docs contain a broken link for Avro > - > > Key: KAFKA-7315 > URL: https://issues.apache.org/jira/browse/KAFKA-7315 > Project: Kafka > Issue Type: Improvement > Components: streams >Reporter: John Roesler >Priority: Major > Labels: docuentation, newbie > > https://kafka.apache.org/documentation/streams/developer-guide/datatypes.html#avro -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (KAFKA-7315) Streams serialization docs contain a broken link for Avro
[ https://issues.apache.org/jira/browse/KAFKA-7315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16586650#comment-16586650 ] Jordan Moore edited comment on KAFKA-7315 at 8/20/18 11:12 PM: --- What about a separate section on SerDe's outside of the Streams docs? I've seen examples of people using MsgPack and ProtoBuf as well. Sure, it's documented implicitly (or briefly under "Message Format") that Kafka uses only byte[] for keys/values, but lots of "getting started guides" are sending strings and not really discussing the benefits of alternative, more compact "structured" formats. was (Author: cricket007): What about a separate section on SerDe's outside of the Streams docs? I've seen examples of people using MsgPack and ProtoBuf as well. Sure, it's documented implicitly (or briefly under "Message Format") that Kafka uses only byte[] for keys/values, but lots of "getting started guides" are sending strings and not really discussing the values of alternative, more compact "structured" formats. > Streams serialization docs contain a broken link for Avro > - > > Key: KAFKA-7315 > URL: https://issues.apache.org/jira/browse/KAFKA-7315 > Project: Kafka > Issue Type: Improvement > Components: streams >Reporter: John Roesler >Priority: Major > Labels: docuentation, newbie > > https://kafka.apache.org/documentation/streams/developer-guide/datatypes.html#avro -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (KAFKA-7315) Streams serialization docs contain a broken link for Avro
[ https://issues.apache.org/jira/browse/KAFKA-7315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16586629#comment-16586629 ] Jordan Moore edited comment on KAFKA-7315 at 8/20/18 10:56 PM: --- bq. should be vendor agnostic and not mention any of them Fair enough. Though, in its place I feel it would be fair to mention at least _somewhere_ the alternatives to primitive Java types, byte arrays and JSON. The only mentions of Avro elsewhere in the docs that I can easily find are in the Connect sections. was (Author: cricket007): bq. should be vendor agnostic and not mention any of them Fair enough. Though, in it's place I feel it would be fair to mention at least _somewhere_ the alternatives to primitive Java types, byte arrays and JSON. The only mentions of Avro elsewhere in the docs that I can easily find are in the Connect sections. > Streams serialization docs contain a broken link for Avro > - > > Key: KAFKA-7315 > URL: https://issues.apache.org/jira/browse/KAFKA-7315 > Project: Kafka > Issue Type: Improvement > Components: streams >Reporter: John Roesler >Priority: Major > Labels: docuentation, newbie > > https://kafka.apache.org/documentation/streams/developer-guide/datatypes.html#avro -- This message was sent by Atlassian JIRA (v7.6.3#76005)