Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configuration option autoload_known_extensions default not consistent with other client APIs #582

Open
pierre-lamarche opened this issue Nov 6, 2024 · 0 comments

Comments

@pierre-lamarche
Copy link

pierre-lamarche commented Nov 6, 2024

Trying to work with data stored on S3, I've come across the fact that when using the duckdb R package, I have to load the httpfs extension as a pre-requisite, which I don't have to do when using Python's duckdb module or the standalone CLI.

I am probably missing something, but it looks like this is linked with the fact that when I run FROM duckdb_settings() on the R package, I can see that the option autoload_known_extensions is set by default to false, while it is set to true in Python and on the CLI (which is actually consistent with the documentation).

As a consequence, I have to explicitly load the extension httpfs, should I want to query data stored on S3 for instance. It seems not completely consistent with the documentation. Do you agree with this, and if yes, would it be possible to consider turning the default of this option to true?

@pierre-lamarche pierre-lamarche changed the title Configuration option autoload_known_extensions default not consistent with client APIs Configuration option autoload_known_extensions default not consistent with other client APIs Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant