chore: downgrade vector destinations from certified to community support - #75299
Conversation
…unity Downgrade destination-weaviate, destination-milvus, and destination-snowflake-cortex from certified to community support level based on low cloud connection counts: - Weaviate: 76 total connections, 0 active in last 30 days - Milvus: 42 total connections, 2 active - Snowflake Cortex: 28 total connections, 1 active Pinecone (621 total) and PGVector (176 total) remain certified. Co-Authored-By: AJ Steers <aj@airbyte.io>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
👋 Greetings, Airbyte Team Member!Here are some helpful tips and reminders for your convenience. 💡 Show Tips and TricksPR Slash CommandsAirbyte Maintainers (that's you!) can execute the following slash commands on your PR:
📚 Show Repo GuidanceHelpful Resources
|
|
|
|
Downgrade destination-pgvector from certified to community support level. PGVector had 176 total connections (18 enabled) - low usage relative to the remaining certified destinations.
|
8f85385
into
master
certified to community support
…support (airbytehq#75299) Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
What
Downgrades four low-usage vector store destination connectors from
certifiedtocommunitysupport level:destination-weaviatedestination-milvusdestination-snowflake-cortexdestination-pgvectorThis is based on Airbyte Cloud production connection data showing relatively low adoption:
After this change, Pinecone (621 total, 102 enabled) remains the only certified Python vector destination.
How
Changed
supportLevel: certified→supportLevel: communityin each connector'smetadata.yaml. No other fields modified.Review guide
airbyte-integrations/connectors/destination-milvus/metadata.yamlairbyte-integrations/connectors/destination-snowflake-cortex/metadata.yamlairbyte-integrations/connectors/destination-weaviate/metadata.yamlairbyte-integrations/connectors/destination-pgvector/metadata.yamlReviewer check: Confirm whether the
ab_internal.slandab_internal.qlfields should also be updated to reflect the new community support level, or if those are independent. Current values: Weaviate/Milvus/Snowflake Cortex havesl: 300, ql: 300; PGVector hassl: 200, ql: 300.User Impact
These four connectors will appear as "community" instead of "certified" in the Airbyte UI and connector registry. No functional changes to the connectors themselves.
Can this PR be safely reverted and rolled back?
Link to Devin session: https://app.devin.ai/sessions/0d4c25fa273147bba0ed9ed9d4f76a0b
Requested by: Aaron ("AJ") Steers (@aaronsteers)