Skip to content

🎉 New Destination: Exasol#21200

Merged
sunny (sh4sh) merged 70 commits intoairbytehq:masterfrom
kaklakariada:add-exasol-connector
Feb 21, 2023
Merged

🎉 New Destination: Exasol#21200
sunny (sh4sh) merged 70 commits intoairbytehq:masterfrom
kaklakariada:add-exasol-connector

Conversation

@kaklakariada
Copy link
Copy Markdown
Contributor

@kaklakariada Christoph Pirkl (kaklakariada) commented Jan 10, 2023

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

  1. ExasolDestination.java
  2. ExasolSqlOperations.java
  3. ExasolDestinationAcceptanceTest.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

  • Community member? Grant edit access to maintainers (instructions)
  • Secrets in the connector's spec are annotated with airbyte_secret
  • Unit & integration tests added and passing. Community members, please provide proof of success locally e.g: screenshot or copy-paste unit, integration, and acceptance test output. To run acceptance tests for a Python connector, follow instructions in the README. For the Exasol connector run ./gradlew :airbyte-integrations:connectors:destination-exasol:integrationTest.
  • Code reviews completed
  • Documentation updated
    • Connector's README.md
    • Connector's bootstrap.md. See description and examples
    • docs/integrations/destination/exasol.md including changelog. See changelog example
    • docs/integrations/README.md
    • airbyte-integrations/builds.md
  • PR name follows PR naming conventions

Airbyter

If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.

  • Create a non-forked branch based on this PR and test the below items on it
  • Build is successful
  • If new credentials are required for use in CI, add them to GSM. Instructions.
  • /test connector=connectors/<name> command is passing
  • New Connector version released on Dockerhub by running the /publish command described here
  • After the connector is published, connector added to connector index as described here
  • Seed specs have been re-generated by building the platform and committing the changes to the seed spec files, as described here

Tests

Unit tests and integration/acceptance tests run during CI. No special setup is required:

./gradlew :airbyte-integrations:connectors:destination-exasol:test :airbyte-integrations:connectors:destination-exasol:integrationTest

@kaklakariada Christoph Pirkl (kaklakariada) changed the title Add exasol connector New Destination: Exasol Jan 10, 2023
@kaklakariada
Copy link
Copy Markdown
Contributor Author

Ivica Taseski (@itaseskii) I implemented your comments, please check again.

@itaseskii
Copy link
Copy Markdown
Contributor

Ivica Taseski (itaseskii) commented Jan 25, 2023

/test connector=connectors/destination-exasol

🕑 connectors/destination-exasol https://github.com/airbytehq/airbyte/actions/runs/4004559668
✅ connectors/destination-exasol https://github.com/airbytehq/airbyte/actions/runs/4004559668
No Python unittests run

Build Passed

Test summary info:

All Passed

@itaseskii
Copy link
Copy Markdown
Contributor

Nice work Christoph Pirkl (@kaklakariada)! I have approved your changes and I will proceed with the release process.

@sh4sh
Copy link
Copy Markdown
Contributor

sunny (sh4sh) commented Feb 7, 2023

/publish connector=connectors/destination-exasol

🕑 Publishing the following connectors:
connectors/destination-exasol
https://github.com/airbytehq/airbyte/actions/runs/4117243984


Connector Did it publish? Were definitions generated?
connectors/destination-exasol

if you have connectors that successfully published but failed definition generation, follow step 4 here ▶️

@sh4sh sunny (sh4sh) temporarily deployed to more-secrets February 7, 2023 23:26 — with GitHub Actions Inactive
@sh4sh sunny (sh4sh) temporarily deployed to more-secrets February 7, 2023 23:26 — with GitHub Actions Inactive
@kaklakariada
Copy link
Copy Markdown
Contributor Author

Ivica Taseski (@itaseskii) sunny (@sh4sh) Greg Solovyev (@grishick) : When will this PR be merged? Can I do anything to help?

@sh4sh sunny (sh4sh) merged commit f9bc114 into airbytehq:master Feb 21, 2023
@sh4sh
Copy link
Copy Markdown
Contributor

Thanks for your contribution!

@evantahler
Copy link
Copy Markdown
Contributor

Evan Tahler (evantahler) commented Feb 22, 2023

sunny (@sh4sh) - this PR should not have been merged as it did not pass the branch requirements. Now the master branch is also failing too. The /publish command above also failed. I'm going to revert this PR.

Edit: I think I know what's wrong - trying to fix it. Check out #23321!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/connectors Connector related issues area/documentation Improvements or additions to documentation bounty community connectors/destination/exasol

Projects

No open projects

Development

Successfully merging this pull request may close these issues.

8 participants