You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix duckdb/connector recipe: correct the startup log the reader is told to confirm
Step 4 tells the reader to confirm the dataset loaded by looking for
'INFO runtime: Loaded dataset: tpch_customer'. That log message no longer
exists anywhere in the runtime, so the check can never succeed. The runtime
now prints 'Dataset tpch_customer registered (duckdb:customer), results cache
enabled.' from runtime::init::dataset.
The same block also pasted two lines the runtime no longer emits: the
'spiced: Metrics listening' line (the metrics server is off by default on
v2) and 'runtime::opentelemetry: Spice Runtime OpenTelemetry listening on
127.0.0.1:50052' (that listener was removed).
Step 5's result table also predates the column type row the v2 SQL REPL
prints. The data itself is unchanged and still matches TPC-H sf=1.
0 commit comments