kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Randall Hauch (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-2600) Make KStream interfaces compatible with Java 8 java.util.function
Date Fri, 02 Oct 2015 14:52:28 GMT

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

Randall Hauch commented on KAFKA-2600:
--------------------------------------

My original suggestion was to make these changes so we can eventually _evolve_ from KStream's
custom functional interfaces to Java8 standard functional interfaces. These changes would
make it possible for our functional interfaces to extend Java 8's and remain binary compatible,
but changing `KStream` methods to *use* the Java 8 functional interfaces is not binary compatible.
Overloading is also not an option, since that wreaks havoc with lambdas and makes it ambiguous
as to which method is being used. Thus, the goal of these changes is to simply align names
and concepts with those in the Java 8 API for ease of learning and use. The attached PR still
does this.

> Make KStream interfaces compatible with Java 8 java.util.function
> -----------------------------------------------------------------
>
>                 Key: KAFKA-2600
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2600
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Guozhang Wang
>            Assignee: Randall Hauch
>             Fix For: 0.9.0.0
>
>
> As suggested by [~rhauch], if we make the interface method names as the same to java.util.function.[Functions]:
> https://docs.oracle.com/javase/8/docs/api/java/util/function/package-summary.html
> Our goal is to simply align names and concepts with those in the Java 8 API for ease
of learning and use.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message