Moritz Eyssen

Not urgent, but there is some special handling in #1489 because of this which could be removed if RangeFilter were available for all types.

In the non-equi case it just... partitions (is that the same as "clusters"?), right iirc? So I wouldn't think that a name that contains "Sort" is fitting. "ClusterOrSortMaterializer"? I mean,...

seems acceptable then

> expect this to only be significant if we call a virtual method on a class where we already knew the type precisely > Also, is marking the class final...

I'm using this, seems to work ```c++ // Pin to the current node { const auto cpu = sched_getcpu(); Assert(cpu >= 0, "Couldn't determine CPU"); const auto node = numa_node_of_cpu(cpu);...

Nice, no, doesn't look familiar. Happy drilling ;) You could checkout the JoinTestRunner branch and make the query plans use the JoinVerificationOperator (by altering the LQPTranslator) instead of JoinHash, JSM,...

any idea why this would only fail if the query is run in isolation, but never if the entire testsuite is run?

Setting and especially forwarding flags on Tables/Chunks/Segments is not something we should do in Hyrise. It requires Operators, which *should* be single-concern algorithms, to think about what everybody else might...

Admittedly, with Proxy Operators the Optimizer-sets-properties approach falls apart.

Okay, if forwarding Chunk properties in operators is unavoidable we have to *force* the operators to think about them. It should be impossible to construct a Chunk without specifying its...