Details
-
Bug
-
Resolution: Fixed
-
Medium
-
6.1.3
-
None
-
6.01
-
Description
As discovered while troubleshooting reindex problems on an internal JIRA instance, a runtime exception raised by an issue's custom field prevents that issue from being indexed at all. IssueDocument.getDocument(Issue) should be hardened such that only the problem custom field is dropped from the indexing, not the entire issue. The data will still be wrong, but partial data is better than no data.
Ideally, the exception should be remembered and re-thrown after the issue has been indexed so that we can still report the problem.
Attachments
Issue Links
- is related to
-
JRASERVER-35840 AccumulatingResultBuilder needs to provide a way to get full stack traces during reindex
- Closed
- relates to
-
JRASERVER-35839 Foreground and Background reindex have different authentication context states
- Closed
-
ADM-45798 Loading...
-
FLASH-1148 Loading...
-
DESK-1692 Loading...
- Is related to
-
HOT-707 Loading...
- was cloned as
-
JDEV-26173 Loading...