-
Notifications
You must be signed in to change notification settings - Fork 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
Operator has been terminated issue with RowsFetchSpec and Spring DatabaseClient #133
Comments
Hm, it seems that the mapping function is not the problem. It's It boils down to |
Hi, @sephiroth-j. Thank you for reporting this. I think I've got a fix: #134 In a nutshell: Oracle R2DBC will handle resource clean up the way Project Reactor intends it to: Flux.usingWhen(...) |
Hey, thanks for the quick solution. Until the release with the fix is available, I can use |
Hi @Michael-A-McMahon, can you give an estimated date for the release of this fix? |
Hi @sephiroth-j, I'll check with my team about a new release. I think we are due for one. I can't estimate a date right now, but I'll update this thread once I know more. |
Going to get a few more changes in this week, and then get our release process started. Next release could happen by the end of next week, but there's no guarantee. |
When a mapping function via
map
is used on aGenericExecuteSpec
, theonErrorDropped
hook is triggered twice and the following error is logged. This does not happen whenfetch
is used with its default row mapper that maps the result to aMap<String,Object>
. The query is successfully executed in both cases.Error
Example
spring-oracle-r2dbc-issue.zip
The text was updated successfully, but these errors were encountered: