Skip to content

unify KeyValueMapper and KeyValueFlatMap#16

Merged
ymatsuda merged 1 commit into
confluentinc:streamingfrom
ymatsuda:remove_KeyValueFlatMap
Aug 28, 2015
Merged

unify KeyValueMapper and KeyValueFlatMap#16
ymatsuda merged 1 commit into
confluentinc:streamingfrom
ymatsuda:remove_KeyValueFlatMap

Conversation

@ymatsuda

Copy link
Copy Markdown

Guozhang Wang (@guozhangwang)
This unifies KeyValueMapper and KeyValueFlatMap to reduce the number of functional interfaces. For Java7 users, their code will be a little bit more verbose. Java8 users using lambda expressions won't be affected.

@guozhangwang

Copy link
Copy Markdown

LGTM. One related thought is that the input and output formats are now a bit different: we have two inputs K key, V value, with one output (of course :P) KeyValue. Do we want to unify the input to be also KeyValue<K, V>?

Also in practice, type K would mostly be String, while type V maybe a Tuple that possibly wraps AvroGenericRecord, what do you think of optimizing ser-de overheads of intermediate results?

ymatsuda added a commit that referenced this pull request Aug 28, 2015
unify KeyValueMapper and KeyValueFlatMap
@ymatsuda ymatsuda merged commit 4effc53 into confluentinc:streaming Aug 28, 2015
@ymatsuda ymatsuda deleted the remove_KeyValueFlatMap branch September 2, 2015 16:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants