-
Notifications
You must be signed in to change notification settings - Fork 57
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
Add Lots of Connector Unit Tests #957
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm. I gave up reading them thoroughly about halfway through but ya know, it's tests, as long as they're not testing that broken behavior stays broken they're good and I trust you not to have done that
text_representation="text", | ||
bbox=(0.0, 0.0, 1.0, 1.0), | ||
shingles=[1, 2, 3], | ||
embedding=[0.1, 0.2, 0.3, 0.4], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is a diff num dimensions than the target_params. Guess doesn't matter since mock but if we ever implement a runtime check won't this break stuff (prob good to have break anyway, so I'd leave it. just flagging)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right, think it might be best to leave it in, if we do implement a check we should change this test.
Adds unit tests for the Pinecone, Elasticsearch, and DuckDB readers and writers, fixes bugs, and refactors DuckDB to not hardcode the schema.