egalpin commented on issue #10712: URL: https://github.com/apache/pinot/issues/10712#issuecomment-1633182873
My original motivation was to add the ability to replace a table in a way that was transparent to anything issuing queries. Ex. `myTable` is a realtime upsert table with 8 kafka partitions. Later, data volume has grown such that I really ought to be using 16 partitions to handle the volume. Using this feature, I could go about adding `myTable_v2` which is populated from a new kafka topic with 16 partitions this time. Then I could "flip the switch" so that queries would start using the new table instead of the original table. There are similar parallels for OFFLINE tables as well, where I might want to rebuild the table in some backward incompatible or potentially dangerous way, and maintain the ability to swap to the new table immediately, and also swap back immediately if things don't go according to plan. If this can be extended or re-used to be able to support what Jackie mentioned, i.e. "fanout" queries to all tables with the same alias, that would be great too. I can think of many use cases where it would be helpful to have multiple tables sharing an alias. If fanning out to multiple tables can be done via alias though, it feels like `UNION` might be even better to support? -- 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 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
