[
https://issues.apache.org/jira/browse/CALCITE-2557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Sereda updated CALCITE-2557:
-----------------------------------
Description:
Elastic doesn't normally support pagination with aggregates (see
[4915|https://github.com/elastic/elasticsearch/issues/4915]).
Starting with v6.1 there is [bucket aggregation sorting
|https://www.elastic.co/guide/en/elasticsearch/reference/6.1/search-aggregations-pipeline-bucket-sort-aggregation.html]
which can possibly be leveraged. However we have to support older versions of
elastic like 2,5 and 6. Christian suggested to fetch larger dataset {{offset +
limit}} and manually trim the result set on application side.
was:
Elastic doesn't normally support pagination with aggregates (see
[4915|https://github.com/elastic/elasticsearch/issues/4915]).
Starting with v6.1 there is [bucket aggregation sorting
|https://www.elastic.co/guide/en/elasticsearch/reference/6.1/search-aggregations-pipeline-bucket-sort-aggregation.html]
which can possibly be leveraged. However we have to support older versions of
elastic like 2,5 and 6. Christian suggested to fetch larger dataset {{offset +
limit}} and manually trim the result set on application side.
> Support pagination for buckets aggregations in ElasticSearch adapter
> --------------------------------------------------------------------
>
> Key: CALCITE-2557
> URL: https://issues.apache.org/jira/browse/CALCITE-2557
> Project: Calcite
> Issue Type: Bug
> Components: elasticsearch-adapter
> Reporter: Andrei Sereda
> Assignee: Julian Hyde
> Priority: Major
>
> Elastic doesn't normally support pagination with aggregates (see
> [4915|https://github.com/elastic/elasticsearch/issues/4915]).
> Starting with v6.1 there is [bucket aggregation sorting
> |https://www.elastic.co/guide/en/elasticsearch/reference/6.1/search-aggregations-pipeline-bucket-sort-aggregation.html]
> which can possibly be leveraged. However we have to support older versions
> of elastic like 2,5 and 6. Christian suggested to fetch larger dataset
> {{offset + limit}} and manually trim the result set on application side.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
