-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
🎉 New Destination: Weaviate #20094
🎉 New Destination: Weaviate #20094
Conversation
itaseski seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
/test connector=destination-weaviate |
1 similar comment
/test connector=destination-weaviate |
801b846
to
9e56857
Compare
/test connector=connectors/destination-weaviate
|
/test connector=connectors/destination-weaviate
|
@itaseskii not sure if the error is related to my PR? https://github.com/airbytehq/airbyte/actions/runs/3674928650/jobs/6213762344#step:13:22 |
/test connector=connectors/destination-weaviate
Build FailedTest summary info:
|
/test connector=connectors/destination-weaviate |
/test connector=connectors/destination-weaviate
Build PassedTest summary info:
|
d7989df
to
19541e9
Compare
/test connector=connectors/destination-weaviate |
/test connector=connectors/destination-weaviate
Build PassedTest summary info:
|
/publish connector=connectors/destination-weaviate
if you have connectors that successfully published but failed definition generation, follow step 4 here |
/publish connector=connectors/destination-weaviate
if you have connectors that successfully published but failed definition generation, follow step 4 here |
@samos123 please make sure you follow step no.4 of this document to fix the definition generation failure: Then when the publish command is successful and all CI/CD checks have passed, we can merge this PR. Thanks for your contribution! |
The definitions have already been generated in a subsequent commit after the publish failure. Going through the points sequentially the connector should first be published and then definitions should be generated guarantying that definition generation will fail on publish for PR's for new connectors. |
Thanks for the PR @samos123 and thanks for the review @itaseskii |
* Add Weaviate Destination #20012 * Fix formatting and standards * Fix flake issue * Fix unused client variable * Add support for int based ID fields * Ensure stream name meets Weaviate class reqs * add integration test for using pokemon as source * handle nested objects by converting to json string * create schema for transforming data to weaviate * Add docs for weaviate destination * Remove pokemon-schema external dependency * Remove pikachu integration test external dep * Add large batch test case * add test for second sync * Fix issue with fields starting with uppercase * add more checks to line_break test * Update README for Weaviate * Make batch_size configurable with 100 as default * Add support for providing vectors * Update docs * Add test for existing Weaviate class * Add trying to create schema in check connection * Add support for mongodb _id fields * Add support for providing custom ID * remove unused file * fix flow of is_ready() check * Move standalone functions to utils.py * Support overwrite mode * Add regex based stream_name_class_name conversion * remove unneeded print statement * Add "airbyte_secret" : true to password config * add support for array of arrays * remove unneeded variable declaration * change to MutableMapping since we use del * change name from queued_write to buffered_write * add retry on partial batch error * Fix partial batch retry and add tests * fix ID generation * Clean up recursive retry logic * fix flake tests * ran flake reformat * add definitions Co-authored-by: Ivica Taseski <ivica.taseski94@gmail.com> Co-authored-by: itaseski <itaseski@debian-BULLSEYE-live-builder-AMD64>
What
Add a connector for Weaviate to be able to write data to Weaviate. Source Connector will be done in separate PR
How
Use the Weaviate Python client to batch AirbyteRecords and flush them on state or when batch size is reached.
🚨 User Impact 🚨
Yes 🚨, end-users will be able to utilize this new connector after this gets merged. So this should probably be highlighted in change notes somewhere.
Pre-merge Checklist
Expand the relevant checklist and delete the others.
New Connector
Community member or Airbyter
airbyte_secret
./gradlew :airbyte-integrations:connectors:<name>:integrationTest
.README.md
bootstrap.md
. See description and examplesdocs/integrations/<source or destination>/<name>.md
including changelog. See changelog exampledocs/integrations/README.md
airbyte-integrations/builds.md
Airbyter
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/publish
command described hereUpdating a connector
Community member or Airbyter
airbyte_secret
./gradlew :airbyte-integrations:connectors:<name>:integrationTest
.README.md
bootstrap.md
. See description and examplesdocs/integrations/<source or destination>/<name>.md
including changelog. See changelog exampleAirbyter
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/publish
command described hereConnector Generator
-scaffold
in their name) have been updated with the latest scaffold by running./gradlew :airbyte-integrations:connector-templates:generator:testScaffoldTemplates
then checking in your changesTests
Unit
Put your unit tests output here.
Integration
Acceptance
Put your acceptance tests output here.