Tom Ebergen
Tom Ebergen
Hi, This should be fixed with https://github.com/duckdb/duckdb/pull/14969 Just tested lastest dev version with the example [here](https://github.com/duckdb/duckdb/issues/10988#issuecomment-2563689699) as well
Keep in mind that `USING SAMPLE` is only supported by DuckDB, so when it comes to precedence as to where the sampling operator should be placed, there's not really anywhere...
0. Yes given the diff you provided of course this will return the same result, but the result is not always created in the same way. Without optimization, a cross...
Oops, sorry about that. I will test it again
Latest results will use v2.1.2 You can see here. https://github.com/duckdblabs/db-benchmark/pull/126/files Also running the large join on collapse, hopefully can have the results up later today
Hi @SebKrantz, So I've run the benchmark for collapse a couple of times on the large machine large dataset. Collapse @v2.1.2 seems to fail each time during ingestion. I know...
Seems like https://github.com/duckdb/duckdb-aws/issues/62#issuecomment-2839235394 is a workaround/fix? @nicornk Happy to keep your PR open so we can include it in the v1.5 release. Is anyone else still experiencing issues? Or can...
Please reopen if the provided workaround does not work for people
I'll take a look 👍
Closing since fix has been merged