You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Implement External Table Transport for WolverineFx.Oracle #4482
Is your feature request related to a problem? Please describe.
My organisation is transitioning away from a legacy codebase using Oracle and wants to use the external table transport option. However this is currently not implemented
@Trasvi Careful, you're close to volunteering to be the Oracle guy for Wolverine! Nobody has wanted it until now. Relatively easy feature to add.
I don't mind doing this one at all, will put up a PR soon. Being "the Oracle guy" might be a bit much, i'm doing this so we can get away from it!!
Would it be a good opportunity to create a set of ExternalTableTransportCompliance tests for other providers as well, or should i keep it narrowly focussed on Oracle?
Done, and thank you @Trasvi — the external table transport is implemented for Oracle and shipped in #4558, with follow-up hardening in #4574, #4577, and #4578.
OracleMessageStore.ExternalDbTransportStore.cs replaces the NotImplementedException this issue linked to.
OracleTests/Transport/external_message_tables.cs and external_table_poll_failures_are_logged.cs cover it.
And to answer your question about widening the scope: yes, it was worth it. Wolverine.ComplianceTests/ExternalTableTransportCompliance.cs is now a shared suite run by Oracle, PostgreSQL, SQL Server, MySQL, and Sqlite, so every provider's external table transport is held to the same bar.
Activity
jeremydmiller commentedon Sep 18, 2026
@Trasvi Careful, you're close to volunteering to be the Oracle guy for Wolverine! Nobody has wanted it until now. Relatively easy feature to add.
Trasvi commentedon Sep 18, 2026
I don't mind doing this one at all, will put up a PR soon. Being "the Oracle guy" might be a bit much, i'm doing this so we can get away from it!!
Would it be a good opportunity to create a set of ExternalTableTransportCompliance tests for other providers as well, or should i keep it narrowly focussed on Oracle?
JasperFxGH-4482: Create Compliance Tests for ExternalTableTransport
JasperFxGH-4482: Implement External Table Transport for Oracle
JasperFxGH-4482: Update external-tables documentation.
Gh 4482 implement external table transport for oracle (#4558)
GH-4482 follow-up: small cleanups from the #4558 review (#4574)
GH-4482 follow-up: stop the Oracle poller swallowing failures, restor…
GH-4482 follow-up: assert the external table drains, make the store g…
jeremydmiller commentedon Sep 24, 2026
Done, and thank you @Trasvi — the external table transport is implemented for Oracle and shipped in #4558, with follow-up hardening in #4574, #4577, and #4578.
OracleMessageStore.ExternalDbTransportStore.csreplaces theNotImplementedExceptionthis issue linked to.OracleTests/Transport/external_message_tables.csandexternal_table_poll_failures_are_logged.cscover it.And to answer your question about widening the scope: yes, it was worth it.
Wolverine.ComplianceTests/ExternalTableTransportCompliance.csis now a shared suite run by Oracle, PostgreSQL, SQL Server, MySQL, and Sqlite, so every provider's external table transport is held to the same bar.Bump to 6.40.0 (#4608)