Hi, I have two questions regarding the Phoenix + Calcite integration:
1) Phoenix has salted tables which add a hashed value "header" to the beginning of the rowkey. Thus salted tables are hash partitioned but maintains primary key order within each partition. So question is how should we describe the collation and distribution trait of salted tables? I assume distribution is just HASH_DISTRIBUTED, but is the collation of sorted on PK (just the same as regular tables) enough here? 2) Phoenix has a implementation of secondary index called local index, which means each partition (region) of index table is always co-located with the corresponding partition (region) of its parent table. Is there a way that we could describe this co-location relationship? I think it might be useful if we should have a "local join" operator in future. Thanks, Maryann
