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

source-snowflake: discover vector columns #2157

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

williamhbaker
Copy link
Member

@williamhbaker williamhbaker commented Nov 20, 2024

Description:

Snowflake has a special type of column for storing vector embeddings. These columns contain either integer or float values in a fixed-length array.

We can discover schemas for these fields accordingly, giving their discovered arrays annotations for the type of items and min/max length of the array, which will always be the size of the vector.

These types of schematized fields may eventually be used by materializations for materializing into corresponding vector columns or indexes.

Workflow steps:

(How does one use this feature, and how has it changed)

Documentation links affected:

(list any documentation links that you created, or existing ones that you've identified as needing updates, along with a brief description)

Notes for reviewers:

(anything that might help someone review this PR)


This change is Reviewable

Snowflake has a special type of column for storing vector embeddings. These
columns contain either integer or float values in a fixed-length array.

We can discover schemas for these fields accordingly, giving their discovered
arrays annotations for the type of items and min/max length of the array, which
will always be the size of the vector.

These types of schematized fields may eventually be used by materializations for
materializing into corresponding vector columns or indexes.
@williamhbaker williamhbaker removed the request for review from willdonnelly January 14, 2025 16:13
@williamhbaker williamhbaker marked this pull request as draft January 14, 2025 16:14
@williamhbaker
Copy link
Member Author

Setting this back to draft status since there is some uncertainty around how captures should be adding information like this to schemas, and there's not an immediate need for it. I'll keep the branch around just in case somebody shows up and wants to use it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant