You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Xavier Léauté (Jira)" <ji...@apache.org> on 2021/06/03 02:47:00 UTC

[jira] [Created] (KAFKA-12883) Adress KIP-100 type constraints now that Java 7 support is dropped

Xavier Léauté created KAFKA-12883:
-------------------------------------

             Summary: Adress KIP-100 type constraints now that Java 7 support is dropped
                 Key: KAFKA-12883
                 URL: https://issues.apache.org/jira/browse/KAFKA-12883
             Project: Kafka
          Issue Type: Improvement
            Reporter: Xavier Léauté


As part of [KIP-100 rejected alternatives|https://cwiki.apache.org/confluence/display/KAFKA/KIP-100+-+Relax+Type+constraints+in+Kafka+Streams+API#KIP100RelaxTypeconstraintsinKafkaStreamsAPI-RejectedAlternatives], we suggested a more correct alternative to the type constraints for some of the {{KStream}} methods.

Unfortunately at the time, there was a Java 7 compiler behavior that prevented us from using those type constraints, so we had to relax them in order to preserve backwards compatibility.

As part of the KIP it was mentioned that:

??Once we drop support for 1.7 we can always decide to switch to approach 2. without breaking source compatibility, by making a proposal similar to this KIP.??

Since Java 7 support has been dropped a while ago, it would be a good time to revisit this and possibly switch to the alternative type constraints. The change should be source compatible, although the streams APIs have significantly evolved since, so there might be some additional investigation required to ensure that is still the case and also covers the Scala Streams APIs.
 



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