npawar commented on pull request #7733: URL: https://github.com/apache/pinot/pull/7733#issuecomment-966713310
Motivation from Vibhor Jain on slack ```Thanks for looking into this. Ours is a hybrid table where realtime is holding data for say 7 days and minion is moving it to offline (to support backfill for future needs). Now, duplicates occur in small batches for us since our Flink flows are at least once. There is no scenario where a duplicate is coming after say 4 days. So we only need UPSERT for realtime. Blocking this for hybrid table is not working out for us. Till now, we were handling deduplication flow for our hybrid table in 2 steps: realtime handles it via UPSERT. offline handles it via mergeType: "dedup" in "RealtimeToOfflineSegmentsTask" configs. This was working perfectly fine and no duplicates were seen. Pls note, we understand UPSERT cannot work across realtime and offline tables together. We were leveraging this functionality only for REALTIME. UPSERT documentation clearly states it's for REALTIME. So if I'm using it for the hybrid table, it should be allowed (given the limitation to real time only that's already documented). Let me know if you need further info on this one. ``` -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
