You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are scenarios where is convenient to run Kafka Configurator as an external library from Java code. But there are some obstacles in that:
Due to Scala/Java paradigm mismatch, there is no pretty way to process case classes in Java, the result of Kafka Configurator work is exactly that class.
Calling of run(...).get() yields in Tuple2<List,List> result type which cannot be processed from the outer code due to package restriction of ConfiguratorFailure class.
It would be nice to have:
A dedicated function which result can be elegantly processed in Java code
Positive results can be exposed as a List as it returned in Tuple2 result of Scala code
Negative results could be propagated as Exception class descendants (either Runtime one, or not)
Scala provides a list of ConfiguratorFailure but it's enough to return to Java a Throwable instance got from the head of this list (if we have got sufficient logging on Scala side)
The text was updated successfully, but these errors were encountered:
aaaleshaaa
changed the title
Support ru Kafka Configurator as an external library from Java code
Support Kafka Configurator as an external library which can be called from Java code
Jul 27, 2018
aaaleshaaa
changed the title
Support Kafka Configurator as an external library which can be called from Java code
Kafka Configurator as an external library which can be called from Java code
Jul 27, 2018
There are scenarios where is convenient to run Kafka Configurator as an external library from Java code. But there are some obstacles in that:
run(...).get()
yields in Tuple2<List,List> result type which cannot be processed from the outer code due to package restriction of ConfiguratorFailure class.It would be nice to have:
The text was updated successfully, but these errors were encountered: