Skip to content
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

Milvus, Chroma, Qdrant, Pinecone: Update CDK #30820

Merged
merged 4 commits into from Oct 1, 2023

Conversation

flash1293
Copy link
Contributor

What

Updates CDK for Milvus, Chroma, Qdrant and Pinecone connectors to get fix in for Azure embedders.

@vercel
Copy link

vercel bot commented Sep 28, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
airbyte-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 1, 2023 2:12pm

@github-actions
Copy link
Contributor

github-actions bot commented Sep 28, 2023

Before Merging a Connector Pull Request

Wow! What a great pull request you have here! 🎉

To merge this PR, ensure the following has been done/considered for each connector added or updated:

  • PR name follows PR naming conventions
  • Breaking changes are considered. If a Breaking Change is being introduced, ensure an Airbyte engineer has created a Breaking Change Plan.
  • Connector version has been incremented in the Dockerfile and metadata.yaml according to our Semantic Versioning for Connectors guidelines
  • You've updated the connector's metadata.yaml file any other relevant changes, including a breakingChanges entry for major version bumps. See metadata.yaml docs
  • Secrets in the connector's spec are annotated with airbyte_secret
  • All documentation files are up to date. (README.md, bootstrap.md, docs.md, etc...)
  • Changelog updated in docs/integrations/<source or destination>/<name>.md with an entry for the new version. See changelog example
  • Migration guide updated in docs/integrations/<source or destination>/<name>-migrations.md with an entry for the new version, if the version is a breaking change. See migration guide example
  • If set, you've ensured the icon is present in the platform-internal repo. (Docs)

If the checklist is complete, but the CI check is failing,

  1. Check for hidden checklists in your PR description

  2. Toggle the github label checklist-action-run on/off to re-run the checklist CI.

@airbyte-oss-build-runner
Copy link
Collaborator

destination-qdrant test report (commit 118dfae4e2) - ✅

⏲️ Total pipeline duration: 03mn46s

Step Result
Connector package install
Build destination-qdrant docker image for platform linux/x86_64
Unit tests
Code format checks
Validate metadata for destination-qdrant
Connector version semver check
Connector version increment check
QA checks

🔗 View the logs here

☁️ View runs for commit in Dagger Cloud

Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command

airbyte-ci connectors --name=destination-qdrant test

@airbyte-oss-build-runner
Copy link
Collaborator

destination-chroma test report (commit 118dfae4e2) - ❌

⏲️ Total pipeline duration: 04mn04s

Step Result
Connector package install
Build destination-chroma docker image for platform linux/x86_64
Unit tests
Code format checks
Validate metadata for destination-chroma
Connector version semver check
Connector version increment check
QA checks

🔗 View the logs here

☁️ View runs for commit in Dagger Cloud

Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command

airbyte-ci connectors --name=destination-chroma test

@airbyte-oss-build-runner
Copy link
Collaborator

destination-pinecone test report (commit 118dfae4e2) - ✅

⏲️ Total pipeline duration: 04mn06s

Step Result
Connector package install
Build destination-pinecone docker image for platform linux/x86_64
Unit tests
Integration tests
Acceptance tests
Code format checks
Validate metadata for destination-pinecone
Connector version semver check
Connector version increment check
QA checks

🔗 View the logs here

☁️ View runs for commit in Dagger Cloud

Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command

airbyte-ci connectors --name=destination-pinecone test

@airbyte-oss-build-runner
Copy link
Collaborator

destination-milvus test report (commit 118dfae4e2) - ✅

⏲️ Total pipeline duration: 04mn08s

Step Result
Connector package install
Build destination-milvus docker image for platform linux/x86_64
Unit tests
Integration tests
Acceptance tests
Code format checks
Validate metadata for destination-milvus
Connector version semver check
Connector version increment check
QA checks

🔗 View the logs here

☁️ View runs for commit in Dagger Cloud

Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command

airbyte-ci connectors --name=destination-milvus test

@airbyte-oss-build-runner
Copy link
Collaborator

destination-qdrant test report (commit 40af6af121) - ✅

⏲️ Total pipeline duration: 01mn45s

Step Result
Connector package install
Build destination-qdrant docker image for platform linux/x86_64
Unit tests
Code format checks
Validate metadata for destination-qdrant
Connector version semver check
Connector version increment check
QA checks

🔗 View the logs here

☁️ View runs for commit in Dagger Cloud

Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command

airbyte-ci connectors --name=destination-qdrant test

@airbyte-oss-build-runner
Copy link
Collaborator

destination-milvus test report (commit 40af6af121) - ✅

⏲️ Total pipeline duration: 02mn54s

Step Result
Connector package install
Build destination-milvus docker image for platform linux/x86_64
Unit tests
Integration tests
Acceptance tests
Code format checks
Validate metadata for destination-milvus
Connector version semver check
Connector version increment check
QA checks

🔗 View the logs here

☁️ View runs for commit in Dagger Cloud

Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command

airbyte-ci connectors --name=destination-milvus test

@airbyte-oss-build-runner
Copy link
Collaborator

destination-pinecone test report (commit 40af6af121) - ✅

⏲️ Total pipeline duration: 02mn54s

Step Result
Connector package install
Build destination-pinecone docker image for platform linux/x86_64
Unit tests
Integration tests
Acceptance tests
Code format checks
Validate metadata for destination-pinecone
Connector version semver check
Connector version increment check
QA checks

🔗 View the logs here

☁️ View runs for commit in Dagger Cloud

Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command

airbyte-ci connectors --name=destination-pinecone test

@airbyte-oss-build-runner
Copy link
Collaborator

destination-chroma test report (commit 40af6af121) - ✅

⏲️ Total pipeline duration: 03mn09s

Step Result
Connector package install
Build destination-chroma docker image for platform linux/x86_64
Unit tests
Code format checks
Validate metadata for destination-chroma
Connector version semver check
Connector version increment check
QA checks

🔗 View the logs here

☁️ View runs for commit in Dagger Cloud

Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command

airbyte-ci connectors --name=destination-chroma test

Copy link
Contributor

@pedroslopez pedroslopez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nits/Qs, but LGTM!

Comment on lines +50 to +53
if config.embedding.mode == "azure_openai" or config.embedding.mode == "openai":
self.embedder = embedder_map[config.embedding.mode](config.embedding, config.processing.chunk_size)
else:
self.embedder = embedder_map[config.embedding.mode](config.embedding)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could you share more about what's going on here and why only chroma needs this?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh - are we just now adding the embedder for chroma but others have it already?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, exactly, this is aligning with the others.

@@ -6,7 +6,7 @@
from setuptools import find_packages, setup

MAIN_REQUIREMENTS = [
"airbyte-cdk[vector-db-based]",
"airbyte-cdk[vector-db-based]==0.51.22",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need to pin exact? If we want to at least include this version but go up to 0.51.x we could use ~=

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As the vector db CDK currently changes dramatically even in patch versions, I would like to keep it like this for now until things are more stable-

@flash1293 flash1293 enabled auto-merge (squash) October 1, 2023 14:02
@airbyte-oss-build-runner
Copy link
Collaborator

destination-pinecone test report (commit 1c2c5848b6) - ✅

⏲️ Total pipeline duration: 03mn46s

Step Result
Connector package install
Build destination-pinecone docker image for platform linux/x86_64
Unit tests
Integration tests
Acceptance tests
Code format checks
Validate metadata for destination-pinecone
Connector version semver check
Connector version increment check
QA checks

🔗 View the logs here

☁️ View runs for commit in Dagger Cloud

Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command

airbyte-ci connectors --name=destination-pinecone test

@airbyte-oss-build-runner
Copy link
Collaborator

destination-qdrant test report (commit 1c2c5848b6) - ✅

⏲️ Total pipeline duration: 04mn43s

Step Result
Connector package install
Build destination-qdrant docker image for platform linux/x86_64
Unit tests
Code format checks
Validate metadata for destination-qdrant
Connector version semver check
Connector version increment check
QA checks

🔗 View the logs here

☁️ View runs for commit in Dagger Cloud

Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command

airbyte-ci connectors --name=destination-qdrant test

@airbyte-oss-build-runner
Copy link
Collaborator

destination-chroma test report (commit 1c2c5848b6) - ✅

⏲️ Total pipeline duration: 04mn44s

Step Result
Connector package install
Build destination-chroma docker image for platform linux/x86_64
Unit tests
Code format checks
Validate metadata for destination-chroma
Connector version semver check
Connector version increment check
QA checks

🔗 View the logs here

☁️ View runs for commit in Dagger Cloud

Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command

airbyte-ci connectors --name=destination-chroma test

@airbyte-oss-build-runner
Copy link
Collaborator

destination-milvus test report (commit 1c2c5848b6) - ✅

⏲️ Total pipeline duration: 05mn06s

Step Result
Connector package install
Build destination-milvus docker image for platform linux/x86_64
Unit tests
Integration tests
Acceptance tests
Code format checks
Validate metadata for destination-milvus
Connector version semver check
Connector version increment check
QA checks

🔗 View the logs here

☁️ View runs for commit in Dagger Cloud

Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command

airbyte-ci connectors --name=destination-milvus test

@flash1293 flash1293 merged commit 14bfc11 into master Oct 1, 2023
23 checks passed
@flash1293 flash1293 deleted the flash1293/update-connectors branch October 1, 2023 14:28
girarda pushed a commit that referenced this pull request Oct 10, 2023
Co-authored-by: flash1293 <flash1293@users.noreply.github.com>
girarda pushed a commit that referenced this pull request Oct 10, 2023
Co-authored-by: flash1293 <flash1293@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants