-
Notifications
You must be signed in to change notification settings - Fork 11
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
improve MongoStatement#executeUpdate #40
Conversation
| MongoSocketWriteTimeoutException | ||
| MongoTimeoutException | ||
| MongoExecutionTimeoutException e) { | ||
throw new SQLTimeoutException(e.getMessage(), e); |
There was a problem hiding this comment.
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.
b6197d7
to
65a017b
Compare
# Conflicts: # src/test/java/com/mongodb/hibernate/jdbc/MongoPreparedStatementTests.java
# Conflicts: # src/main/java/com/mongodb/hibernate/jdbc/MongoStatement.java
There was a problem hiding this 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.
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. |
https://jira.mongodb.org/browse/HIBERNATE-40
The implementation is based on bulk write API, paving the way for future batch processing code refactoring.