This concerns the behavior when cross_shard_disabled = true.
If an unknown sharding key is used (with SET for example), the parser will throw the same error as if no sharding key was entered at all. It's not critical, but it would be nice if the error message thrown would indicate that the sharding key does not exist, to differentiate the two scenarios.
This concerns the behavior when
cross_shard_disabled = true.If an unknown sharding key is used (with SET for example), the parser will throw the same error as if no sharding key was entered at all. It's not critical, but it would be nice if the error message thrown would indicate that the sharding key does not exist, to differentiate the two scenarios.