🎉 New Destination: Exasol#21200
Conversation
Replace Exasol specific code with default method
|
Ivica Taseski (@itaseskii) I implemented your comments, please check again. |
|
/test connector=connectors/destination-exasol
Build PassedTest summary info: |
|
Nice work Christoph Pirkl (@kaklakariada)! I have approved your changes and I will proceed with the release process. |
|
/publish connector=connectors/destination-exasol
if you have connectors that successfully published but failed definition generation, follow step 4 here |
|
Ivica Taseski (@itaseskii) sunny (@sh4sh) Greg Solovyev (@grishick) : When will this PR be merged? Can I do anything to help? |
|
Thanks for your contribution! |
|
Edit: I think I know what's wrong - trying to fix it. Check out #23321! |
This reverts commit f9bc114.
What
This adds a connector for the Exasol database as destination. This PR replaces #20368 which did not allow edits and access to secrets by maintainers.
How
Created connector based on template.
Recommended reading order
ExasolDestination.javaExasolSqlOperations.javaExasolDestinationAcceptanceTest.java🚨 User Impact 🚨
New Exasol destination in Airbyte.
Pre-merge Checklist
Expand the relevant checklist and delete the others.
New Connector
Community member or Airbyter
airbyte_secret./gradlew :airbyte-integrations:connectors:destination-exasol:integrationTest.README.mdbootstrap.md. See description and examplesdocs/integrations/destination/exasol.mdincluding changelog. See changelog exampledocs/integrations/README.mdairbyte-integrations/builds.mdAirbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.
/test connector=connectors/<name>command is passing/publishcommand described hereTests
Unit tests and integration/acceptance tests run during CI. No special setup is required: