[OAK-5164] ChangeSet's maxPathDepth must be taken into account by ChangeSetFilterImpl

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.5.14
• Fix Version/s: 1.5.15, 1.6.0
• Component/s: core
• Assignee: Stefan Egli
• Reporter: Stefan Egli
• Created: 25/Nov/16 09:31
• Updated: 12/Dec/16 14:36
• Resolved: 28/Nov/16 13:13

Description

The ChangeSet stops collecting paths that are deeper than maxPathDepth. This is to avoid collecting too much detail (and overflow the ChangeSet) given normally filters' includePaths are only a few levels deep.

This information is currently however not yet used by the ChangeSetFilterImpl. This is wrong and must be fixed. At the moment it's not a realistic problem though as the maxPathDepth is 9 and typically filters have include paths of perhaps 2-4. But with ChangeSet merging (OAK-5126) that figure of 9 might come down, so accounting for maxPathDepth in the filter must be done at some point.

Issue Links

• is related to: OAK-5126 Support ChangeSet merging and serialization