-
Notifications
You must be signed in to change notification settings - Fork 230
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
[Bug]: Native parquet source does not work #2975
Comments
are you able to supply or point to your economies.parquet file? |
doesn't seem to matter which parquet file i try: here's another simple file that i tried: https://huggingface.co/datasets/substrate-labs/owid/blob/main/data/owid_co2_data.parquet |
Did you install the parquet connector and add it to your evidence.config.yaml?
We will be moving this to a first party connector very soon |
Still not working. I started a fresh project using
then then add a dir with a
npm run sources
> [email protected] sources
> evidence sources
✔ Loading plugins & sources
-----
[Processing] mypar
[ ! ] Error connecting to datasource mypar: Invalid Input Error: Values were not provided for the following prepared statement parameters: |
Can you add the parquet source via the UI in localhost:3000/settings - it looks like you are missing config |
Tried that as well by adding a new parquet source
|
What's interesting is that the first time i try to add a new parquet source from |
that i think is a bug, but not the issue here
|
Are you able to repro? I've tried fresh a few times now, with the latest version. Looking at the code it seems identical to the csv plugin, which works fine for me |
Describe the bug
I'm trying to use the native parquet/csv source as described in the docs. My source dir looks like:
connection.yaml
looks like:and trying a very minimal
index.md
:ends up in an error:
My
npm run sources
output:Steps to Reproduce
Try a very simple project with a single source, having a single
.parquet
file in it and try to make a query that uses it.Logs
System Info
Severity
blocking all usage of Evidence
Additional Information, or Workarounds
No response
The text was updated successfully, but these errors were encountered: