You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Steven Aerts (JIRA)" <ji...@apache.org> on 2017/10/06 09:49:00 UTC
[jira] [Created] (KAFKA-6018) Make from KafkaFuture.Function java 8
lambda compatible
Steven Aerts created KAFKA-6018:
-----------------------------------
Summary: Make from KafkaFuture.Function java 8 lambda compatible
Key: KAFKA-6018
URL: https://issues.apache.org/jira/browse/KAFKA-6018
Project: Kafka
Issue Type: Bug
Components: clients
Reporter: Steven Aerts
KafkaFuture.Function is currently an empty public abstract class.
This means you cannot implement them as a java lambda. And you end up with constructs as:
{code:java}
new KafkaFuture.Function<Set<String>, Object>() {
@Override
public Object apply(Set<String> strings) {
return foo;
}
}
{code}
I propose to define them as interfaces.
So this code can become in java 8:
{code:java}
strings -> foo
{code}
I know this change is backwards incompatible (extends becomes implements).
But as {{KafkaFuture}} is marked as {{@InterfaceStability.Evolving}}.
And KafkaFuture states in its javadoc:
{quote}This will eventually become a thin shim on top of Java 8's CompletableFuture.{quote}
I think this change might be worth considering.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)