Hello,
My team is working on a feature to add a general “base table” for a collection of Calcite tables in our service. Something we’ve come across is that different tables will have different supported data retrieval patterns, which we’ve been referring to as “indices”. For example, assume we have a service with two APIs: - getByPrice(<inputs>) → <results> - getByPriceAndTime(<inputs>) → <results> In this case, the Calcite table which will expose this service has two possible ways to retrieve data (i.e. there are two “indices”). Since the table implementation is meant to be generic, we would like to devise a general solution for encoding these indices in Calcite (with relative priority in case one index is preferred over the other), and having Calcite choose the “best” one for a given query. Have you encountered this problem or something similar before? We have some ideas for how to solve it, but wanted to see if this is a common pattern. Thank you, Austin
