-
Notifications
You must be signed in to change notification settings - Fork 151
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
SNOW-1374015: 🐛 Snowflake SQLAlchemy Driver fails when reflecting new VECTOR
data type
#499
Comments
VECTOR
data typeVECTOR
data type
hello and thank you for the interest of the public preview feature of
We'll work on adding support in other Snowflake drivers and connectors and thank you for bearing with us while this happens. |
@sfc-gh-dszmolka - Yes, that makes sense. Our workaround for now is to pass certain commands through the Snowflake Python client - but it would be beneficial long-term to switch back to the native SQLAlchemy integrations - and also to at least make sure SQLAlchemy does not break when attempting to scan or read from those tables. Happy to use this issue as a tracking item for that future work. Thanks for your support. |
Hey @sfc-gh-dszmolka. As this feature is now out of public preview, do you know the status of this issue? Thanks! |
hi @japborst unfortunately at this moment, I don't have any additional info on the timeline for the implementation, but trying to get it from the team and will update this issue when/if I have any news. Thank you all for bearing with us ! |
Hey @sfc-gh-dszmolka! On the website I read
Do I read correctly that whilst there is Python support (the Python snowflake connector), it's primarily SQLAlchemy support that is missing? |
for those who need vector dt in sqlalchemy, this temp workaround (there's nothing more permanent than temporary) might help:
embedding = Column(SFVector('FLOAT', 1536), nullable=True) |
Is there any ETA on this? It makes this quite hard to connect to sqlalchemy based solutions such as SuperSet. |
FWIW: I've used a similar workaround, although it won't help when SQLAlchemy is wrapped by another tool (like Superset in the comment above). Would be great to see native support added. |
Symptom trying to fix?
When reflecting a SQL table, failures will raise if using the (very new!)
VECTOR
data type.What did you expect to see?
I think this driver needs to be updated to handle
VECTOR
type. Internally, this is basically an array of floats, except that the number of items in the array is fixed at creation time.The text was updated successfully, but these errors were encountered: