8000 DuckDB crashes when opening DuckLake - Data loaded via DBT · Issue #104 · duckdb/ducklake · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

DuckDB crashes when opening DuckLake - Data loaded via DBT #104

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.

Sign up for GitHub

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

Jump to bottom
Open
IS-Josh opened this issue May 31, 2025 · 0 comments
Open

DuckDB crashes when opening DuckLake - Data loaded via DBT #104

IS-Josh opened this issue May 31, 2025 · 0 comments

Comments

@IS-Josh
Copy link
IS-Josh commented May 31, 2025 •
edited
Loading

Data was loaded via DBT-DuckDB, with some tables having 2 level partitions.

I have tried loading data via DBT to both cloudflare R2 and GCP Cloud Storage. I've tried deleting the catalog and cloud storage field and starting again. Same issue occurs. When I try to load the ducklake, DuckDB crashes. I have no issues with another ducklake on r2 which I have only interacted with vi DuckDB UI

Catalog is hosted on postres (neon)
Running on OSX 15.3.1 - M1 Mac

Running latest versions of duckb and nightly of ducklake

libc++abi: terminating due to uncaught exception of type duckdb::Exception: {"exception_type":"FATAL","exception_message":"Failed: database has been invalidated because of a previous fatal error. The database must be restarted prior to being used again.\nOriginal error: "Attempted to dereference shared_ptr that is NULL!"\n\nStack Trace:\n\n0 _ZN6duckdb9ExceptionC2ENS_13ExceptionTypeERKNSt3__112basic_stringIcNS2_11char_traitsIcEENS2_9allocatorIcEEEE + 64\n1 _ZN6duckdb14FatalExceptionC1ENS_13ExceptionTypeERKNSt3__112basic_stringIcNS2_11char_traitsIcEENS2_9allocatorIcEEEE + 12\n2 _ZN6duckdb12ErrorManager19InvalidatedDatabaseERNS_13ClientContextERKNSt3__112basic_stringIcNS3_11char_traitsIcEENS3_9allocatorIcEEEE + 172\n3 _ZN6duckdb13ClientContext18BeginQueryInternalERNS_17ClientContextLockERKNSt3__112basic_stringIcNS3_11char_traitsIcEENS3_9allocatorIcEEEE + 980\n4 _ZN6duckdb13ClientContext35PendingStatementOrPreparedStatementERNS_17ClientContextLockERKNSt3__112basic_stringIcNS3_11char_traitsIcEENS3_9allocatorIcEEEENS_10unique_ptrINS_12SQLStatementENS3_14default_deleteISD_EELb1EEERNS_10shared_ptrINS_21PreparedStatementDataELb1EEERKNS_22PendingQueryParametersE + 60\n5 _ZN6duckdb13ClientContext43PendingStatementOrPreparedStatementInternalERNS_17ClientContextLockERKNSt3__112basic_stringIcNS3_11char_traitsIcEENS3_9allocatorIcEEEENS_10unique_ptrINS_12SQLStatementENS3_14default_deleteISD_EELb1EEERNS_10shared_ptrINS_21PreparedStatementDataELb1EEERKNS_22PendingQueryParametersE + 1556\n6 _ZN6duckdb13ClientContext20PendingQueryInternalERNS_17ClientContextLockENS_10unique_ptrINS_12SQLStatementENSt3__114default_deleteIS4_EELb1EEERKNS_22PendingQueryParametersEb + 144\n7 _ZN6duckdb13ClientContext5QueryERKNSt3__112basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEEb + 268\n8 _ZN6duckdb10Connection8RollbackEv + 68\n9 _ZN6duckdb19DuckLakeTransaction8RollbackEv + 40\n10 _ZN6duckdb26DuckLakeTransactionManager19RollbackTransactionERNS_11TransactionE + 36\n11 duckdb::TransactionContext::Rollback(duckdb::optional_ptr<duckdb::ErrorData, true>) + 168\n12 duckdb::ClientContext::Destroy() + 96\n13 duckdb::ClientContext::~ClientContext() + 32\n14 duckdb::Connection::~Connection() + 128\n15 duckdb::DuckDBPyConnection::Close() + 80\n16 void pybind11::cpp_function::initialize<pybind11::cpp_function::cpp_function<void, duckdb::DuckDBPyConnection, pybind11::name, pybind11::is_method, pybind11::sibling, char [21]>(void (duckdb::DuckDBPyConnection::)(), pybind11::name const&, pybind11::is_method const&, pybind11::sibling const&, char const (&) [21])::'lambda'(duckdb::DuckDBPyConnection), void, duckdb::DuckDBPyConnection*, pybind11::name, pybind11::is_method, pybind11::sibling, char [21]>(void&&, duckdb::DuckDBPyConnection ()(), pybind11::name const&, pybind11::is_method const&, pybind11::sibling const&, char const (&) [21])::'lambda'(pybind11::detail::function_call&)::__invoke(pybind11::detail::function_call&) + 112\n17 pybind11::cpp_function::dispatcher(_object, _object*, _object*) + 3664\n18 cfunction_call + 60\n19 _PyObject_MakeTpCall + 128\n20 _PyEval_EvalFrameDefault + 53588\n21 gen_send_ex2 + 204\n22 _gen_throw + 336\n23 _PyEval_EvalFrameDefault + 63392\n24 _PyEval_Vector + 156\n25 method_vectorcall + 296\n26 _PyEval_EvalFrameDefault + 48944\n27 gen_send_ex2 + 204\n28 _gen_throw + 336\n29 _PyEval_EvalFrameDefault + 63392\n30 _PyEval_Vector + 156\n31 method_vectorcall + 296\n32 _PyEval_EvalFrameDefault + 48944\n33 _PyEval_Vector + 156\n34 _PyEval_EvalFrameDefault + 63912\n35 _PyEval_Vector + 156\n36 _PyEval_EvalFrameDefault + 63912\n37 _PyEval_Vector + 156\n38 method_vectorcall + 364\n39 thread_run + 220\n40 pythread_wrapper + 48\n41 _pthread_start + 136\n42 thread_start + 8\n","stack_trace":""}
@IS-Josh IS-Josh changed the title DuckDB crashes when opening DuckLake (Backed by Postgrea and R2 ) DuckDB crashes when opening DuckLake - Data loaded via DBT May 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@IS-Josh
0