I've went through several iterations of back-and-forth with @rhauch on the PR and on Confluent's Slack Community. The current thinking is that assuming an empty array is a String array is not necessarily the best option, nor is assuming that all null values in a JSON node is a String.
We might be able to account for these potentially false assumptions/inferences by introducing new task properties (with value.converter prefix) that explicitly define overrides for either specific json field keys, or give the option for Kafka Connect users to provide a full immutabl schema they know are true for the topics impacted by the Sink Connector. What do you think? - Allen On Mon, May 14, 2018 at 2:58 PM, Allen Tang <nateng...@gmail.com> wrote: > Hi, > > I just opened a KIP to add Schema Inferencing in JsonConverters for Kafka > Connect. > > The details of the proposal can be found here: > https://cwiki.apache.org/confluence/display/KAFKA/KIP-301%3A+Schema+Inferencing+for+JsonConverter > > Also, I have created a - > > 1.) JIRA ticket: https://issues.apache.org/jira/browse/KAFKA-6895 > > 2.) Provisional PR with initial discussion: > https://github.com/apache/kafka/pull/5001 > > Looking forward to the community's feedback! Cheers! > > -Allen > >
