Skip to content

Conversation

@vbabanin
Copy link
Member

@vbabanin vbabanin commented Nov 1, 2025

@vbabanin vbabanin self-assigned this Nov 1, 2025
@vbabanin vbabanin changed the title Remove assertion. Remove assertion for verbose result Nov 1, 2025
// Note: Previously, assertTrue(verboseResultsSetting) was used here because the server was not supposed
// to return successful operation results in the cursor when verboseResultsSetting is false.
// Due to server bug SERVER-113344, these unexpected results must be ignored until we stop supporting server
// versions with this bug. When that happens, restore assertTrue(verboseResultsSetting) here.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's leave a TODO-<JAVA ticket ID> tag here, and create a corresponding ticket, which is linked as "blocked by" / "depends on" (not sure what relations we have) to the aforementioned server ticket.

writeModelIndex,
new ConcreteClientUpdateResult(
individualOperationResponse.getInt32("n").getValue(),
individualOperationResponse.getInt32("nModified", new BsonInt32(0)).getValue(),
Copy link
Member

@stIncMale stIncMale Nov 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks to me that this change, coming from #1823, should have also had a corresponding JAVA ticket describing that it is to be rolled back once https://jira.mongodb.org/browse/SERVER-113026 (it is not the same as the aforementioned SERVER-113344) is fixed and no version where the bug is present is supported. The TODO-<Jira ticket ID> tag will be needed here as well, to point to the place that needs to be changed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants