Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | MODDICONV-293 |
---|
|
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | MODDICONV-251 |
---|
|
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | MODSOURMAN-943 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | UIDATIMP-1369 |
---|
|
Some profiles contain filled parentProfiles and childProfiles, which should be empty. These fields are filled only when constructing a response for the UI. In case profile json stores these values, they are not only redundant, but cause profile to be too heavy during processing. It may lead to slow performance of mod-data-import-converter-storage (mod-di-converter-storage since Orchid), OOM errors in mod-source-record-manager, and errors from Kafka. Such profiles need to be corrected and profile snapshots should be deleted from job executions that are completed. Run the following queries:
...