Using use_memory_table=false for a parquet backed dataset results in an error being generated when querying via postgres

[chrisfw]

Using roapi 0.12.4, when attempting to utilize the use_memory_table set to false for a parquet dataset, the error below occurs:

ERROR:  arrow to pg conversion not implemented for Utf8View

I tried this with two simple parquet files with the same error being generated as the outcome. Please let me known if you require any further information.

Thanks,
Chris

[chrisfw]

Note that I am also getting an error on a different parquet file dataset that in this case is being loaded into memory:

cwhelan=> select * from billingcons limit 10;
ERROR:  arrow to pg conversion not implemented for Decimal128(13, 2)

[houqp]

@chrisfw confirming this is only happening with the postgres wire protocol interface correct?

[chrisfw]

@houqp , I believe so, but I will test it and let you know for sure.

[chrisfw]

Hi @houqp ,

Yes, I confirmed that using the graphql with parquet output format works fine on the same file that the postgres error occurs on. Please let me know if you need any further information.

Thanks,
Chris

[chrisfw]

Hello @houqp , did you have any thoughts on this issue? Please note that I also reproduced the same issue on a different table with use_memory_table = true

[chrisfw]

Hi again @houqp , if you have a chance, could you let me know if this is something that should be reported as a bug?

Thank you,
Chris

[houqp]

Sorry for the delay, this is expected behavior because the postgres wire protocol doesn't have all the type support implemented yet. Please file a feature request for now.

What's your current use-case for the postgres wire protocol? Maybe we can come up with a quick workaround to unblock.

[chrisfw]

@houqp , no worries, apologies for my delay as well. I will file a feature request as you suggest.

I was looking potentially at hosting some parquet file based datasets and making them available to BI consumers using Postgres ODBC or JDBC drivers. I am certainly open to suggestions for a workaround.

Thanks,
Chris

[mshauneu]

depends on roapi/convergence#1