Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
sql: remove no longer needed tricky login in physical planning
TODO: need to make sure that the same NodeID is resolved to the same SQL instance in the instance resolver. This commit removes logic that was introduced in 9e4364a for physical planning in multi-tenant environment that made it so that whenever two consecutive spans to be partitioned happened to have the same "safe split key", they would end up on the same pod. This was needed in order to make sure that spans corresponding to different column families within a single SQL row would end up on the same SQL pod (otherwise, we'd get errors or incorrect results due to partial SQL rows processed by different pods). I believe this logic was needed only initially because we were using round-robin strategy for assigning pods to spans. That logic, however, was removed in bdda6a0, so I believe it can be safely removed. This removal makes sense conceptually too. Release note: None
- Loading branch information