lksvenoy-r7 opened a new issue, #8973: URL: https://github.com/apache/pinot/issues/8973
Currently nothing stops developers from defining segment relocation in their upsert tables using the instanceAssignmentConfigMap. From discussions in the Pinot slack group, it's become apparent that this breaks the upsert functionality for upsert tables (and apparently also the realtime to offline segments task). We should mark the table configuration as invalid if segment relocation is enabled for an upsert table, or if the realtime to offline task is enabled (cc. @Jackie-Jiang . Can you verify this issue applies to the realtime to offline segments task as well?) -- 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: commits-unsubscr...@pinot.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org For additional commands, e-mail: commits-h...@pinot.apache.org
