Skip to content

Follow Up for ConflictResolver improvements #1562

@cstamas

Description

@cstamas

Follow up to #1547

The PR has been merged, but:

  • introduces a change to ConflictResolver that was the only implementation and a final class, but now is abstract.
  • introduced two "coexisting" conflict resolver implementations ("classic" and "path")
  • the superior (faster) "path" needs to be checked against other version selection strategies than "nearest", if fails it may need more seems it works as expected IF old DF or new BF collector w/ skipper=false is used. If skipper is enabled, BF performs unwanted premature optimizations.
  • do we want to do something about this?

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions