Add query to extended clickbench suite for "complex filter"

[acking-you]

Which issue does this PR close?

• Parts of BinaryExpr evaluate lacks optimization for Or and And scenarios #11212.
• Detail see: Add short circuit evaluation for AND and OR #15462 (review)

Rationale for this change

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

[alamb]

Thank you @acking-you

[Omega359]

I am seeing the sql_planner benchmark now failing after this was merged.

Benchmarking physical_plan_clickbench_q50
Benchmarking physical_plan_clickbench_q50: Warming up for 3.0000 s

thread 'main' panicked at datafusion/core/benches/sql_planner.rs:60:14:
called `Result::unwrap()` on an `Err` value: Context("type_coercion", Plan("Internal error: Expect TypeSignatureClass::Native(LogicalType(Native(String), String)) but received NativeType::Binary, DataType: BinaryView.\nThis was likely caused by a bug in DataFusion's code and we would welcome that you file an bug report in our issue tracker No function matches the given name and argument types 'levenshtein(BinaryView, BinaryView)'. You might need to add explicit type casts.\n\tCandidate functions:\n\tlevenshtein(Coercion(TypeSignatureClass::Native(LogicalType(Native(String), String))), Coercion(TypeSignatureClass::Native(LogicalType(Native(String), String))))"))

[Omega359]

I think we may need to augment the github extended tests to run all the benchmarks, not to validate the results (though we can do that later) but to just make sure the benchmarks still run after a commit. Too many failures without the automated testing.

Edit: filed as #15511

[alamb]

I think we may need to augment the github extended tests to run all the benchmarks, not to validate the results (though we can do that later) but to just make sure the benchmarks still run after a commit. Too many failures without the automated testing.

Yeah -- thanks

I'll file a ticket for the actual error tomorrow.

We should also add real tests for those clickbench queries too 🤔