The default addition of "aggs": {} causes scroll pagination invalid
@Nick-S-2018 is already working on this.
Since Aug 25, 2025.
Assessment
This issue has not been assessed yet.
Description
sdk version: 8.1.0
/**
* search
*/
public SearchResponse search(String tableName, String queryString, List<Object> sort, String scrollToken,
Integer size) {
ApiClient client = this.newClient();
SearchQuery searchQuery = new SearchQuery();
searchQuery.setQueryString(queryString);
SearchRequest searchRequest = new SearchRequest();
searchRequest.table(tableName).query(searchQuery);
searchRequest.sort(sort);
searchRequest.limit(size);
// scroll pagination
Map<String, Object> options = new HashMap<>();
if (StrUtil.isNotBlank(scrollToken)) {
options.put("scroll", scrollToken);
} else {
options.put("scroll", true);
}
searchRequest.options(options);
SearchApi searchApi = new SearchApi(client);
try {
SearchResponse response = searchApi.search(searchRequest);
log.debug("Search response: {}", response);
return response;
} catch (ApiException e) {
this.printError(e);
throw new RuntimeException(e);
}
}
final json body:
{
"table": "products",
"query": {
"query_string": "黑色"
},
"join": [],
"limit": 10,
"aggs": {},
"expressions": {},
"options": {
"scroll": "eyJvcmRlcl9ieV9zdHIiOiJzYWxlcyBhc2MsIGlkIGFzYyIsIm9yZGVyX2J5IjpbeyJhdHRyIjoic2FsZXMiLCJkZXNjIjpmYWxzZSwidmFsdWUiOjAsInR5cGUiOiJpbnQifSx7ImF0dHIiOiJpZCIsImRlc2MiOmZhbHNlLCJ2YWx1ZSI6MjMwOTE4NDQwMzM3NDM0MjE1MywidHlwZSI6ImludCJ9XX0="
},
"sort": [
{
"sales": {
"order": "asc"
}
},
{
"id": {
"order": "asc"
}
}
]
}
There is an "aggs": {}, is auto-generated, it will cause scroll pagination invalid.
Did I use it incorrectly, or is this a feature or a bug ?
- Dominant language
- Java
- Stars
- 65
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from manticoresoftware/manticoresearch-java
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
manticoresoftware/manticoresearch-java#19 · 4 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
manticoresoftware/manticoresearch-java#14 · 2 comments ·
All issues in manticoresoftware/manticoresearch-java
Similar issues
-
`GET /v1/event/token/{uuid}` can report a BOM upload as done before policy evaluation and metrics have finishedPossibly taken @Zargath claimed this today. Opendefect in triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
DependencyTrack/dependency-track#7646 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
floci-io/floci#5425 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
objectionary/eo-graphs#80 ·
-
WebMvcStreamableServerTransportProvider: idle-session eviction stops permanently after a NullPointerException when a session is deleted mid-sweepPossibly taken @lejuho claimed this today. Openstatus: waiting-for-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
spring-projects/spring-ai#7133 ·
Maintainers usually reply within 6 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
objectionary/jucs#141 ·
Maintainers usually reply within 1 day