egalpin commented on issue #10712:
URL: https://github.com/apache/pinot/issues/10712#issuecomment-1703058994
Friendly ping 😊 Any thoughts on how these use cases would impact
recommendations for what the mapping should look like or where it should live?
In case it's helpful as a starting point, I had thought the aliases could be
stored as a single json-serialized string of key-value pairs where the keys are
the alias name and the values are arrays of physical table names associated
with the alias, like so:
```json
{
"myAlias": ["physicalTable1", "physicalTable2"],
"myOtherAlias":
["otherPhysicalTable1","otherPhysicalTable2","otherPhysicalTable3"]
}
```
This would allow for easily modifying associations of many aliases
atomically, as well as easy translation to java Map with constant time lookup
of physical tables that should be targeted for a query. Thoughts?
--
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
