Escaping =
when querying files on s3 storage
#237
saptarshiguha
started this conversation in
General
Replies: 1 comment
-
Looks like I need to do
Why do I need this for duck lake but when querying a parquet file it's not required? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
Firstly, thanks! And also firstly, thanks for making the developer ux(documentation, api) so seamless. I onboarded in one sleepy hour. As for my question
I attached to the DB
And I successfully wrote data using create table and insert into. Seamless. I also have partitions e.g.
ALTER TABLE my_harvest.poem_projects SET PARTITIONED BY (project_type,grading_context_id);
Now I tried one query
and error was
But when I browse the s3 location I do see the file
And when I run the following query in duckdb it works
Is duck lake replacing
=
with the escaped versions? (or is the error happening elsewhere)thanks again
(some errors in copy/paste/and other information removal, but the observations made are correct)
Beta Was this translation helpful? Give feedback.
All reactions