KAFKA-9011: Scala bindings for flatTransform and flatTransformValues in KStream - #7520
Conversation
c5b3cb5 to
e133fa8
Compare
|
Hey @kokachev , Thanks for the contribution! This looks good to me, but can you add some tests exercising the new methods? We have had quite a few issues in the past with Scala implicits behaving unintuitively, so now it's hard to trust even code that looks "obviously correct". Thanks, |
…mValues in KStream
…eam#flatTransformValues in Scala API.
9f2c6b0 to
89af113
Compare
|
retest this please |
|
retest this please |
|
(doing it again so we can capture the test results) Retest this, please. |
|
Note that it's too late for the 2.4.0 release, as of the beginning of October, so I think we need to wait for the 2.4.0 release to actually happen before cherry-picking to the 2.4 branch. We could cherry-pick it to the 2.3 branch, but it might be safer to do the 2.4 and 2.3 cherry-picks at the same time (so we don't drop 2.4 on the floor). |
|
@vvcephei , |
|
Merged #7520 into trunk. |
|
Thanks for the contribution @kokachev! |
|
FWIW I agree with @vvcephei with the cherry-picking, IMHO it's better to wait and do them at one time. |
| override def transform(key: K, value: V): JIterable[VO] = supplier.get().transform(key, value).asJava | ||
| override def init(context: ProcessorContext): Unit = supplier.get().init(context) | ||
| override def close(): Unit = supplier.get().close() |
There was a problem hiding this comment.
@kokachev I just realized that we have multiple calls to supplier.get() here. Calling supplier.get() will return a new instance each time correct? This needs to get changed here and below, as well. We can do this in a follow-up PR using KAFKA-9011.
…in KStream (#7520) Reviewers: John Roesler <john@confluent.io>, Bill Bejeck <bbejeck@gmail.com>
…in KStream (apache#7520) Reviewers: John Roesler <john@confluent.io>, Bill Bejeck <bbejeck@gmail.com>
…d multiple transformer instances being created. (apache#7685) This is a followup PR for apache#7520 to address issue of multiple calls to get() as it was pointed out by @bbejeck in apache#7520 (comment) Reviewers: Bill Bejeck <bbejeck@gmail.com>
@cadonna
More detailed description of your change,
if necessary. The PR title and PR message become
the squashed commit message, so use a separate
comment to ping reviewers.
Summary of testing strategy (including rationale)
for the feature or bug fix. Unit and/or integration
tests are expected for any behaviour change and
system tests should be considered for larger changes.
Committer Checklist (excluded from commit message)