The data set created using Kafka with the source 'Type' as Kafka would not allow the Partition keys to be defined as Non-Scalar property.
The JSON object that we read from the Kafka has unique key that we want to define as Partition Key is inside a page property. E.g., Primay.Page1.Page2.Prop1.
Since we cannot define Primay.Page1.Page2.Prop1 as partition key in the data set how can we ensure that the updates related to same item are always published in the same partition?
What is the type of Prop1? Can you elaborate (with screenshots) what problems you are observing? By default, the available properties to be used as keys correspond to the properties of the Applies To class of the Kafka data set.
Posted: 1 year ago
Posted: 26 Oct 2020 15:02 EDT
Vinod kumar Giripogu (VinodkumarG5467)
Prop1 is Singe value text property, but it is with in the embedded page property of Primay page that is published in Kafka queue. The key I would like to define in the data set is .page1.page2.Prop1, however Pega is not allowing to use properties with in embedded page as keys. Attached screen shots of the error message when I use embedded page property