Skip to content

improve MongoStatement#executeUpdate #40

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

NathanQingyangXu
Copy link
Contributor

https://jira.mongodb.org/browse/HIBERNATE-40

The implementation is based on bulk write API, paving the way for future batch processing code refactoring.

@NathanQingyangXu NathanQingyangXu marked this pull request as draft February 12, 2025 16:29
| MongoSocketWriteTimeoutException
| MongoTimeoutException
| MongoExecutionTimeoutException e) {
throw new SQLTimeoutException(e.getMessage(), e);
Copy link
Contributor Author

Choose a reason for hiding this comment

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

MongoOperationTimeoutException is the only child class of MongoTimeoutException which has been listed here.

@NathanQingyangXu NathanQingyangXu marked this pull request as ready for review February 12, 2025 20:44
@NathanQingyangXu NathanQingyangXu force-pushed the HIBERNATE-40-improve-executeUpdate branch from b6197d7 to 65a017b Compare February 13, 2025 18:00
# Conflicts:
#	src/test/java/com/mongodb/hibernate/jdbc/MongoPreparedStatementTests.java
# Conflicts:
#	src/main/java/com/mongodb/hibernate/jdbc/MongoStatement.java
Copy link
Collaborator

@jyemin jyemin left a comment

Choose a reason for hiding this comment

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

@NathanQingyangXu I'm confused by this PR. Shouldn't it be stacked on top of #35? Otherwise there will be a lot of duplicated bulkWrite-related code I think.

@NathanQingyangXu
Copy link
Contributor Author

@NathanQingyangXu I'm confused by this PR. Shouldn't it be stacked on top of #35? Otherwise there will be a lot of duplicated bulkWrite-related code I think.

If #35 is merged first, yeah. If this PR is merged first, #35 would be refactored. The gist is to centralize the bulk write in one single location. To avoid confusion, let me close this PR and re-open it after #35 is merged.

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