Details
-
Bug
-
Resolution: Timed out
-
Low
-
None
-
6.1.3
-
6.01
-
Severity 3 - Minor
-
1
-
-
Description
In working out the cause of DESK-1692 on an internal JIRA instance, we discovered that the reason the background reindex did not have this problem was that its thread had the authentication context of the user that launched the background reindex.
This shouldn't matter, because nothing inside the indexing code should care who the current user is, but it is surprising and inconsistent with the foreground reindex. The background reindex should probably be done with and anonymous user context as well.
Attachments
Issue Links
- is related to
-
JRASERVER-35840 AccumulatingResultBuilder needs to provide a way to get full stack traces during reindex
- Closed
-
JRASERVER-35841 IssueDocument should be hardened against ill-behaved CF plugins
- Closed
-
JDEV-26173 Loading...