HI All The JIRA I filed: https://issues.apache.org/jira/browse/ATLAS-4323
I want to add Keys to the Kafka notifications. My current plan is to use the GUID as the key for the kafka event. I noticed, however, that the V1 notifications appear to use LONG Ids. I am evaluating a few options here: 1) Make it so that all V2 notifications have keys by default. This won't affect any existing behaviour since null keys give no guarantees of partition data locality. The downside here is that there would be a minor increase in the amount of data sent over the wire (the GUID string). 2) Leave V1 notifications entirely alone, and only enable GUID String keys on V2 notifications. 3) Enable notifications with LONG key V1, String GUID key V2. The main issue is around serializing the arbitrary key type to Bytes. If we decide to only go with String GUIDs then this is much easier (just for V2), but I am curious as to if V1 users would also want this data locality? The most robust solution is to just support keys of arbitrary types. If this is the desired outcome I can do this as well, I just wanted to get a feeling for the limits of scope of responsibility for V1 and V2 notifications. Thanks Adam
