Loading...

XML

Word

Printable

Blocked:
False
Ready:
False
Affects:

Documentation (Ref Guide, User Guide, etc.), Release Notes
Release Note Text:
Undefined
Steps to Reproduce:
Hide

1) Consider a data index installation with more than 100 user task instances created.

2) Execute the following query:

{ UserTaskInstances (where: {state: {in: ["Ready", "Completed"]}}, orderBy : {started: ASC}, pagination: {offset: 0, limit: 100}) { id, started } }

100 Tasks are returned.

3) Now change the limit to a value higher than 100, e.g.

{ UserTaskInstances (where: {state: {in: ["Ready", "Completed"]}}, orderBy : {started: ASC}, pagination: {offset: 0, limit: 200}) { id, started } }

4) The same set of 100 tasks are returned, however we know that the DB has more than 100 tasks.

This worked well before.
Show
1) Consider a data index installation with more than 100 user task instances created. 2) Execute the following query: { UserTaskInstances (where: {state: {in: [ "Ready" , "Completed" ]}}, orderBy : {started: ASC}, pagination: {offset: 0, limit: 100}) { id, started } } 100 Tasks are returned. 3) Now change the limit to a value higher than 100, e.g. { UserTaskInstances (where: {state: {in: [ "Ready" , "Completed" ]}}, orderBy : {started: ASC}, pagination: {offset: 0, limit: 200}) { id, started } } 4) The same set of 100 tasks are returned, however we know that the DB has more than 100 tasks. This worked well before.
Market:

It looks like the data index query limit is fixed in 100, it worked well some weeks ago, so maybe there was a change on that regard.

The issue is produced at least in Infinispan, in other repositories I don't know.

is related to

PLANNER-2183 Kogito Continuous Task Assignment in jBPM using OptaPlanner