sfc-gh-pfus commented on issue #3480:
URL: https://github.com/apache/arrow-adbc/issues/3480#issuecomment-3389216773
Hi @CurtHagenlocher , I'm a go driver dev (unsed under the hood by ADBC). I
took a look at our statistics for the two queries you mentioned and I can see
one difference between the queries - in case of .NET the query is:
```
COPY INTO IDENTIFIER('"<cut>"') FROM <cut>$BIND MATCH_BY_COLUMN_NAME =
CASE_INSENSITIVE
```
Whereas for ADBC it is:
```
COPY INTO IDENTIFIER('"<cut>"') FROM @<cut>/ MATCH_BY_COLUMN_NAME =
CASE_INSENSITIVE FILE_FORMAT = (TYPE = 'PARQUET')
```
Comparing times spent on the backend it seems there is a difference (first
query - 27s, second query - 56min!).
There are two significant differences - `$BIND` suffix and `FILE_FORMAT`
directive. I think the later may do the difference. Can you try ADBC using the
same `FILE_FORMAT` parameter?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
