-
Notifications
You must be signed in to change notification settings - Fork 27
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
Auto Install/Load extensions is causing schema inference discrepancies #124
Comments
Additionally, even if we use the SQL to disable the configuration options, This is after we start the DB:
then we set the configuration params and confirm:
then we read the parquet file:
and after that:
|
This is a problem in the DuckDB side, to be fixed there, where the autoloading in the parquet extensions do not properly checks configuration (and the API around that is not helping avoiding problems, to be improved). I am not aware of any proper workaround in the current version, barred something weird / heavy handed like placing a file that needs admin privileges to be read at |
The spatial extension will no longer be auto-loaded when reading parquet, additionally there is new option
you can set to disable geoparquet conversion even when spatial is loaded. |
We use Duckdb for inferring Parquet file schemas. The latest update (1.1.1) has changed the default behavior of parquet schema inference if
spatial
extension is installed. The problem is that the nodejs module automatically installs/loads the extensions. Is there a way to disable/override this behavior? We do not wantspatial
extension to be installed. I see that the DUCKDB_EXTENSION_AUTOINSTALL_DEFAULT flag is set by default. Is there a way to unset it (maybe using an environment variable) ?The text was updated successfully, but these errors were encountered: