Operational Defect Database
BugZero found this defect 38 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
MongoDB | 2638883
Translate UnknownError raised by checkShardingIndex to InvalidOptions error
Last update date:
4/12/2024
Affected products:
MongoDB Server
Affected releases:
8.0.0-rc1
Fixed releases:
No fixed releases provided.
Description:
Info
On SERVER-88548, we changed the behavior of checkShardingIndex command to throw an InvalidOptions error instead of returning an UnknownError, so that there was no need to translate it at the shardCollection operation level. However, in a multiversion scenario, we may still receive an UnknownError from a checkShardingIndex command running on an old binary node that has to be translated to an InvalidOptions error. So, we still need to translate an UnknownError to a InvalidOptions error until v8.0 becomes the last LTS (note that we will backport SERVER-88548 to v8.0 before it gets released).
Top User Comments
JIRAUSER1268536 commented on Fri, 12 Apr 2024 07:00:21 +0000: This ticket will be fixed by backporting SERVER-88548 to v8.0 (BACKPORT-19709). Then there won't be nodes with the old behavior on multiversion suites in v8.1. However, all the backports of SERVER-88548 are not going to be a trivial cherry-pick: they should take into account that there could be nodes with the old behavior.
Steps to Reproduce
