Support for multiple DB shard sets with different shard strategies

[eeverman]

Does ShardingSphere have support for working multiple shared DBs, each with the same data, but optimized for different types of queries? The hope would be that ShardingSphere-JDBC would route a select query to the set of shards that was best optimized to respond to a select query.

For instance, we have a large, mostly read-only, data set which people search in different ways, for instance by State or by Date Range. We could create two sharded DBs, one based on state, another based on Date: Each set of shards would contain the full complete data, just broken up differently.

Where a select query like this is received:
Select * from X where state = 'MN' - it should be routed to the State based shard set.

Similarly this query:
Select * from X where start_date = '2022-10-01' - should be routed to the Date based shard set.

Is this possible or supported?

Thank you,

--Eric Everman