Interface MergeKeyBehavior


  • @Immutable
    public interface MergeKeyBehavior
    • Method Detail

      • getExpectedTargetContent

        @Nullable
        @Nullable
        Content getExpectedTargetContent()
        If present, the current content on the target branch will be compared against this value.

        This parameter is not supported when multiple commits will be generated, which means only merge operations.

        Supplying a resolved content requires setting this attribute. The merge operation will result in a "conflict", if current value on the target branch is different from this value.

      • getResolvedContent

        @Nullable
        @Nullable
        Content getResolvedContent()
        Clients can provide a "resolved" content object, which will then automatically be persisted via the merge operation instead of detecting and potentially raising a merge-conflict, assuming the content-type is the same.

        This functionality is not implemented for the "legacy" storage model, using this option with the "legacy" storage model will result in an error.

        This parameter is not supported when multiple commits will be generated, which means only merge operations.

        It is mandatory to supply the expected content value,

      • getExpectedTargetDocumentation

        @Nullable
        @Nullable
        Documentation getExpectedTargetDocumentation()
        If present, the current documentation on the target branch will be compared against this value.

        This parameter is not supported when multiple commits will be generated, which means only merge operations.

        Supplying a resolved documentation requires setting this attribute. The merge operation will result in a "conflict", if current value on the target branch is different from this value.

      • getResolvedDocumentation

        @Nullable
        @Nullable
        Documentation getResolvedDocumentation()
        Clients can provide a "resolved" documentation object, which will then automatically be persisted via the merge operation instead of detecting and potentially raising a merge-conflict, assuming the content-type is the same.

        This functionality is not implemented for the "legacy" storage model, using this option with the "legacy" storage model will result in an error.

        This parameter is not supported when multiple commits will be generated, which means only merge operations.

        It is mandatory to supply the expected documentation value,

      • getMetadata

        java.util.List<ContentMetadata> getMetadata()
        Additional information about the operation and/or content object. If and how a Nessie server uses and handles the information depends on the server version and type of metadata (called variant).
      • builder

        static org.projectnessie.model.ImmutableMergeKeyBehavior.Builder builder()