[ 
https://issues.apache.org/jira/browse/KAFKA-5146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17282162#comment-17282162
 ] 

A. Sophie Blee-Goldman commented on KAFKA-5146:
-----------------------------------------------

I agree, let's definitely not remove them entirely.

Personally I think it makes more sense to move them to their own module rather 
than re-use the streams-quickstart, since that modules serves its own purpose 
which is not the same as program examples. But I don't feel that strongly one 
way or another.

There may not be many examples at the moment, but maybe someone will want to 
contribute more. There are definitely plenty of examples that would be useful 
and are currently lacking, such as usage of a global store.

> Kafka Streams: remove compile dependency on connect-json
> --------------------------------------------------------
>
>                 Key: KAFKA-5146
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5146
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>    Affects Versions: 0.10.1.0, 0.10.2.0, 0.10.2.1
>            Reporter: Michael G. Noll
>            Priority: Minor
>
> We currently have a compile-dependency on `connect-json`:
> {code}
> <dependency>
>   <groupId>org.apache.kafka</groupId>
>   <artifactId>connect-json</artifactId>
>   <version>0.10.2.0</version>
>   <scope>compile</scope>
>   </dependency>
> {code}
> The snippet above is from the generated POM of Kafka Streams as of 0.10.2.0 
> release.
> AFAICT the only reason for that is because the Kafka Streams *examples* 
> showcase some JSON processing, but that’s it.
> First and foremost, we should remove the connect-json dependency, and also 
> figure out a way to set up / structure the examples so we that we can 
> continue showcasing JSON support.  Alternatively, we could consider removing 
> the JSON example (but I don't like that, personally).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to