The problem i am facing is we have joins and have multiple logical ways to product a tombstone for deleting a record in the KTable.
Is it possible to determine of if a tombstone was a result of ktable join and not not an explicit tombstone?
The problem i am facing is we have joins and have multiple logical ways to product a tombstone for deleting a record in the KTable.
Is it possible to determine of if a tombstone was a result of ktable join and not not an explicit tombstone?
Copyright © 2021 Jogjafile Inc.
One way I can think of differentiating the tombstones i.e. one occurring as part of the
ktable joinand another one sent as anexplicit tombstoneis to set an extra header attribute in theexplicit tombstonemessage and the consumer can then read those header to determine the source of tombstone.