### Description

Only "search hits" based queries (no aggregations) provide a consistent view on the data when paginating through the result set. With point-in-time, it is possible to support transactional semantics for aggregation queries as well.

This issue is somewhat blocked by https://github.com/elastic/elasticsearch/issues/75528 because a PIT can not immediately be closed if the aggregation result set contains less than `fetch_size` records. This could cause some increased resource utilization due to open PITs. Especially if the client does not close the SQL cursor.
x-pack/plugin/sql/qa/server/src/main/java/org/elasticsearch/xpack/sql/qa/rest/BaseRestSqlTestCase.java
return this;
        }
        public RequestObjectBuilder params(String params) {
            request.append(field(PARAMS_NAME, params));
            return this;
        }
        public RequestObjectBuilder columnar(Boolean columnar) {
            request.append(field(COLUMNAR_NAME, columnar));
            return this;
        }
        public RequestObjectBuilder binaryFormat(Boolean binaryFormat) {
            request.append(field(BINARY_FORMAT_NAME, binaryFormat));
            return this;
        }
        public RequestObjectBuilder waitForCompletionTimeout(String timeout) {
            request.append(field(WAIT_FOR_COMPLETION_TIMEOUT_NAME, timeout));
            return this;
        }
        public RequestObjectBuilder keepOnCompletion(Boolean keepOnCompletion) {
            request.append(field(KEEP_ON_COMPLETION_NAME, keepOnCompletion));
            return this;
        }
        public RequestObjectBuilder keepAlive(String keepAlive) {
            request.append(field(KEEP_ALIVE_NAME, keepAlive));
            return this;
        }
        public RequestObjectBuilder fieldMultiValueLeniency(Boolean fieldMultiValueLeniency) {
            request.append(field(FIELD_MULTI_VALUE_LENIENCY_NAME, fieldMultiValueLeniency));
            return this;
        }