jamesyfshao commented on a change in pull request #5175: add pinot upsert features to pinot common URL: https://github.com/apache/incubator-pinot/pull/5175#discussion_r397563786
########## File path: pinot-common/src/main/java/org/apache/pinot/common/config/TableConfig.java ########## @@ -75,6 +79,9 @@ private Map<InstancePartitionsType, InstanceAssignmentConfig> _instanceAssignmentConfigMap; private List<FieldConfig> _fieldConfigList; + @JsonPropertyDescription(value = "The update semantic of the table, either append or upsert, default as append") + private UpdateSemantic _updateSemantic; Review comment: @kishoreg I am thinking if using enum here will be more flexible in the case of future features changes or whatnot. Boolean seems to be only limiting two options and it might limit what other changes we might want to do with pinot. Please let me what you think. ingestionMode definitely sounds more explicit than what I am using here and I will definite consider about this. @Jackie-Jiang yes. So basically it is previous old design about we want to support update in pinot realtime ingestion by adding override by primary key (eg, a second message in Kafka with the same primary key represents the update of existing key instead of two records with the same primary key). Upsert stands for this new ingestion semantic (insert if no duplicated primary key, update if duplicate primary key). This feature will be applying to realtime table only ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
