Open kysshsy opened 3 months ago
The issue occurs in both the FDW and executor hook. I suspect there's an issue with connection::create_arrow. It can query correctly with E''
but fails with non-zero-length bytes.
Hi @philippemnoel I would like to look into this
Hi @philippemnoel I would like to look into this
All yours :) Thank you for looking into it!
Hi, I think it's about the difference of duckdb and postgres hex representation. https://www.postgresql.org/docs/current/datatype-binary.html https://duckdb.org/docs/sql/data_types/blob
Hi, I think it's about the difference of duckdb and postgres hex representation. https://www.postgresql.org/docs/current/datatype-binary.html https://duckdb.org/docs/sql/data_types/blob
That is a possibility, pg might be using the escape format which is causing all the problem. We might need to decode the string and then encode it into a format that goes well with Duckdb.
But before that I'd like to finish investigating from my side too
Hi @kysshsy can you please attach the paraquet file here, if possible?
test_arrow_types.parquet.zip @destrex271 Yes, github not support parquet files. I forget to zip it.
Hi, I think it's about the difference of duckdb and postgres hex representation. https://www.postgresql.org/docs/current/datatype-binary.html https://duckdb.org/docs/sql/data_types/blob
Yep seems like this is the actual problem. I checked the query execution but its working fine.
Will raise a PR as soon as I come up with a possible fix.
Hi, I think it's about the difference of duckdb and postgres hex representation. https://www.postgresql.org/docs/current/datatype-binary.html https://duckdb.org/docs/sql/data_types/blob
Yep seems like this is the actual problem. I checked the query execution but its working fine.
Will raise a PR as soon as I come up with a possible fix.
Thank you :)
Hi, I think it's about the difference of duckdb and postgres hex representation. https://www.postgresql.org/docs/current/datatype-binary.html https://duckdb.org/docs/sql/data_types/blob
Yep seems like this is the actual problem. I checked the query execution but its working fine.
Will raise a PR as soon as I come up with a possible fix.
Hi @destrex271. Any update on this?
Nope not any as of now, I think it's better if someone else picks it up for now
Nope not any as of now, I think it's better if someone else picks it up for now
Thank you!
What happens?
I am developing quals push-down feature and have found that the query result is abnormal
To Reproduce
CREATE SERVER parquet_server FOREIGN DATA WRAPPER parquet_wrapper;
CREATE FOREIGN TABLE t1 ( boolean_col boolean, int8_col smallint, int16_col smallint, int32_col integer, int64_col bigint, uint8_col smallint, uint16_col integer, uint32_col bigint, uint64_col numeric(20), float32_col real, float64_col double precision, date32_col date, date64_col date, binary_col bytea, large_binary_col bytea, utf8_col text, large_utf8_col text ) SERVER parquet_server OPTIONS (files '/home/kyss/labs/paradedb/test_arrow_types.parquet');
OS:
x86
ParadeDB Version:
0.8.6.
Are you using ParadeDB Docker, Helm, or the extension(s) standalone?
ParadeDB pg_lakehouse Extension
Full Name:
kyss
Affiliation:
NA
Did you include all relevant data sets for reproducing the issue?
Yes
Did you include the code required to reproduce the issue?
Did you include all relevant configurations (e.g., CPU architecture, PostgreSQL version, Linux distribution) to reproduce the issue?