feat: add support for multiquery in ts with limit

[nityanandagohain]

Fixes #2845

• two queries are created pre and main
• during execution if main is found then pre is executed and the result is added to main query and then main query is executed.

test curl

curl --location 'localhost:8080/api/v3/query_range' \
--header 'Content-Type: application/json' \
--data '{
    "start": 1680712088000000000,
    "end": 1690771611000000000,
    "step": 60,
    "dataSource": "logs",
    "compositeQuery": {
        "queryType": "builder",
        "panelType": "graph",
        "limit": 1,
        "builderQueries": {
            "A": {
                "stepInterval": 60,
                "queryName": "A",
                "dataSource": "logs",
                "aggregateOperator": "count",
                "filters": {},
                "limit": 3,
                "groupBy": [
                    {
                        "key": "method",
                        "isColumn": true
                    }
                ],
                "expression": "A",
                "disabled": false
            }
        }
    }
}'

[nityanandagohain]

Have added support for multiple group by

[srikanthccv]

https://clickhouse.com/docs/en/sql-reference/operators/in

The left side of the operator is either a single column or a tuple.

My suggestion for the growing complexity of this is to use a subquery to get the tuple of columns you want to filter on and then use that in the outer query. You will get the same benefit as the two-query approach but without the complexity. You don't have to worry about the subquery affecting performance because it will only be executed once. And don't need to worry about the distributed setup (GLOBAL IN) either because IN doesn't involve a separate table; instead, it is a tuple of columns. If anything, it should be better than the two-query because we eliminate the query-service from the equation.

The one query equivalent of the two-query approach is:

SELECT
    toStartOfInterval(fromUnixTimestamp64Nano(timestamp), toIntervalSecond(60)) AS ts,
    method AS method,
    severity_number AS severity_number,
    toFloat64(count(*)) AS value
FROM signoz_logs.distributed_logs
WHERE timestamp >= 1680712088000000000 AND timestamp <= 1690771611000000000 AND (method, severity_number) IN (
    SELECT
        method,
        severity_number
    FROM
    (
        SELECT
            method AS method,
            severity_number AS severity_number,
            toFloat64(count(*)) AS value
        FROM signoz_logs.distributed_logs
        WHERE (timestamp >= 1680712088000000000) AND (timestamp <= 1690771611000000000)
        GROUP BY
            method,
            severity_number
        ORDER BY value ASC
    )
    LIMIT 1
)
GROUP BY
    method,
    severity_number,
    ts
ORDER BY
    method ASC,
    severity_number ASC,
    ts ASC

[srikanthccv]

You will still use the part of work you worked on already; instead of running queries and the preparing addition part of where you can replace it with a subquery.

[nityanandagohain]

Have added new changes where if there is no orderBy provided

• For table and TS -> add value DESC as orderBy
• For listview -> add timestamp DESC as orderBy

If an order by key is provided.

• For table, ts and listview -> use key provided for ordering.