Hi,
While working with Trino using this .NET client, I noticed a bug with the Hive connector (it could be true for other connectors too) when the request fails with more enriched response details.
How to reproduce:
- use a Hive metastore connector with some inaccessible instance (example: instance1.company.root.site:1234)
- using this .net client, try to run any Trino query that interacts with this hive catalog, example:
SELECT * FROM SYSTEM.METADATA.TABLE_COMMENTS
- Result from this .Net Client:
(Unexpected character encountered while parsing value: {. Path 'error.failureInfo.suppressed', line 1, position 8674.)>. Actual:<One or more errors occurred. (line 1:12: Cannot apply operator: varchar(1) = integer)>.
Expected:
The client should be able to parse the actual error ("Failed connecting to Hive metastore: [instance1.company.root.site:1234]") returned within the the REST API json response.
The Fix
I am submitting a PR shortly.
Regards,
Rachid
Hi,
While working with Trino using this .NET client, I noticed a bug with the Hive connector (it could be true for other connectors too) when the request fails with more enriched response details.
How to reproduce:
SELECT * FROM SYSTEM.METADATA.TABLE_COMMENTS(Unexpected character encountered while parsing value: {. Path 'error.failureInfo.suppressed', line 1, position 8674.)>. Actual:<One or more errors occurred. (line 1:12: Cannot apply operator: varchar(1) = integer)>.Expected:
The client should be able to parse the actual error ("Failed connecting to Hive metastore: [instance1.company.root.site:1234]") returned within the the REST API json response.
The Fix
I am submitting a PR shortly.
Regards,
Rachid