[OAK-4924] avoid CommitInfo==null in contentChanged call in SegmentNodeStore.refresh

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Invalid
• Affects Version/s: 1.5.12
• Component/s: segmentmk
• Assignee: Stefan Egli
• Reporter: Stefan Egli
• Created: 11/Oct/16 14:12
• Updated: 26/Sep/19 11:42
• Resolved: 12/Oct/16 10:16

Description

Currently SegmentNodeStore.refreshHead calls contentChanged with null as the CommitInfo. This is problematic for prefiltering (OAK-4796, OAK-4907 et al) as for that a ChangeSet of changed items in a commit is stored in the CommitContext in the CommitInfo.

Thus it would be useful to not send null but a CommitInfo that has the equivalent meaning of null but is a new object for each call (so that the ChangeSet can be set).

Michael Dürig, Francesco Mari, [~alex.parvulescu] wdyt?

Issue Links

• is superceded by: OAK-4935 support prefiltering of async index updates
• relates to: OAK-4907 Collect changes (paths, nts, props..) of a commit in a validator
• relates to: OAK-5113 Avoid dispatching changes for checkpoint related changes