Currently our sharding config file only contains "Partition Range End". This means we always partition BigQuery tables by using 0 for start point.
This is not an issue of our current default sharding config where variants of each chromosome is assigned to a separate table. However, if config file includes multiple shard per chromosome (such as this one) we can improved the performance of partitioning by including the start position.
Currently our sharding config file only contains "Partition Range End". This means we always partition BigQuery tables by using 0 for start point. This is not an issue of our current default sharding config where variants of each chromosome is assigned to a separate table. However, if config file includes multiple shard per chromosome (such as this one) we can improved the performance of partitioning by including the start position.