The integrity checker is loading the entire JIRA issue table

Description

During the integrity checking procedure, JIRA fired the following query to the database:

SELECT ID, pkey, issuenum, PROJECT, REPORTER, ASSIGNEE, CREATOR, issuetype, SUMMARY, DESCRIPTION, ENVIRONMENT, PRIORITY, RESOLUTION, issuestatus, CREATED, UPDATED, DUEDATE, RESOLUTIONDATE, VOTES, WATCHES, TIMEORIGINALESTIMATE, TIMEESTIMATE, TIMESPENT, WORKFLOW_ID, SECURITY, FIXFOR, COMPONENT FROM jiraissue

and load the data in the memory. For a large JIRA instance (more than 50 000 issues), loading such amount of data required a big chunk of heap that might cause the memory congestion or garbage collection performance issue.

Suggestion

The result set should paged to limit the size of data to be loaded in the memory to avoid the any memory pressure.