Hi Sameer, Dmitry:
Just a side note that for KStream.merge(), we do not guarantee timestamp
ordering, so the resulted KStream may likely have out-of-ordering regarding
the timestamps. If you do want to have some merging operations that
respects the timestamps of the input streams because you
Well. That is one possibility I guess. But some other way might be to
"merge both values" into a single one... There is no "straight forward"
best semantics IMHO.
If you really need this, you can build it via Processor API.
-Matthias
On 1/23/18 7:46 AM, Dmitry Minkovsky wrote:
>> Merging two
> Merging two tables does not make too much sense because each table might
contain an entry for the same key. So it's unclear, which of both values
the merged table should contain.
Which of both values should the table contain? Seems straightforward: it
should contain the value with the highest
Merging two tables does not make too much sense because each table might
contain an entry for the same key. So it's unclear, which of both values
the merged table should contain.
KTable.toStream() is just a semantic change and has no runtime overhead.
-Matthias
On 7/26/17 1:34 PM, Sameer Kumar
Hi,
Is there a way I can merge two KTables just like I have in KStreams api.
KBuilder.merge().
I understand I can use KTable.toStream(), if I choose to use it, is there
any performance cost associated with this conversion or is it just a API
conversion.
-Sameer.
