This PR fixes an internal error that occurs when a user runs a SELECT query with:

• A descending ORDER BY on the timestamp column
• A negative LIMIT
• Jit filtering enabled
• And a timestamp interval filter

Here's an example of such a query:

CREATE TABLE x AS (
  SELECT
    rnd_double() price,
    timestamp_sequence('2024', 24*60*60*1000*1000) ts
  FROM
    long_sequence(2)
) timestamp(ts) PARTITION BY day;

SELECT price, ts
FROM x
WHERE price > 0 AND ts >= '2024-01-01' AND ts <= '2024-12-31'
ORDER BY ts DESC
LIMIT -1

Root cause

The issue arises under several specific conditions:

• Jit is enabled, and the filter (price > 0) is compatible with it, so AsyncJitFilteredRecordCursorFactory is used.
• The ORDER BY ts DESC causes the optimiser to set forceBackwardScan to true.
• The timestamp filter (ts >= ... AND ts <= ...) leads SqlCodeGenerator to use IntervalBwdPartitionFrameCursorFactory.
• A negative LIMIT causes the AsyncJitFilteredRecordCursorFactory to reverse the order from ORDER_DESC to ORDER_ASC.

However, unlike FullBwdPartitionFrameCursorFactory, the IntervalBwdPartitionFrameCursorFactory did not support ORDER_ASC and threw an UnsupportedOperationException.

Fix

This PR resolves the issue by applying the same strategy used in FullBwdPartitionFrameCursorFactory:
If ORDER_ASC is requested, the factory now creates an IntervalFwdPartitionFrameCursor on the fly.

Work In Progress

I'm keeping the PR as work in progress as I'd like to add fuzzy testing to this use case.