Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Stream ids job, relation doesn't exist while using multi tenant

Description

Feature works with diku tenant. But fails while using multi tenant

Steps to reproduce:
1. Create new tenant and enable mod-search for created tenant OR run karate tests
2.  Run job for streaming ids

Expected result: Job status is COMPLETED/ERROR
Actual result: Job freeze in IN_PROGRESS status

Error from logs:

Note: It looks like repository can't specify the tenant module and to fix it we need to add
tenant with module name to select query:

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

2

Checklist

hide

TestRail: Results

Activity

Show:

Valery_Pilko August 1, 2022 at 2:33 PM

Verified at Snapshot env - works as expected.
In situation when we have 2 tenants with mod-search module enabled, the job doesn't freeze with “In progress” status.
See attached screencast:

Shans Kaluhin July 25, 2022 at 11:52 AM

It happens when you use @Transaction and @Async annotations together.
Solution is separate it to two methods. Then first with Async annotation will call method with Transaction

Done

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Spitfire

RCA Group

Implementation coding issue

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created July 10, 2022 at 11:10 PM
Updated October 17, 2022 at 8:03 AM
Resolved August 3, 2022 at 12:22 PM
TestRail: Cases
TestRail: Runs