FasterFilesystemForeignSourceRepository is not working as expected

Description

The optional ForeignSourceRepository implementation called FasterFilesystemForeignSourceRepository, designed to keep all the requisitions on a cache and update the cache when the imports or foreign-source directories are changed, is not working as expected.

The JUnit tests designed for FasterFilesystemForeignSourceRepository and DirectoryWatcher are not covering all the use cases, which is why the problem was not caught before.

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Alejandro Galue April 2, 2016 at 9:03 AM

Yes

Ronny Trommer April 1, 2016 at 8:16 PM

Seems to be fixed, can we delete this branch: https://github.com/OpenNMS/opennms/tree/jira/NMS-7926

Alejandro Galue November 2, 2015 at 10:48 AM

The custom branch created for this issue has been merged into release-17.0.0 on revision 3b69532b64be5a43c290532decbe7d3837dcd79e.

The default strategy is still file. The fastFile implementation must be manually enable in opennms.properties.

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

PagerDuty

Created October 15, 2015 at 9:30 AM
Updated April 2, 2016 at 9:03 AM
Resolved November 2, 2015 at 10:48 AM