Full Fidelity Change Feed Processor with public surface changes

Open kushagraThapar opened this issue 1 year ago • 6 comments

This PR introduces public surface changes for full fidelity Change Feed Processor.

Same ChangeFeedProcessorBuilder which is already GA for incremental mode ->

public ChangeFeedProcessorBuilder handleAllVersionsAndDeletesChanges(Consumer<List<ChangeFeedProcessorItem>> consumer)

ChangeFeedProcessorItem -> contains JsonNode current, JsonNode previous and ChangeFeedMetaData metadata
ChangeFeedMetaData -> contains long crts, long lsn, ChangeFeedOperationType operationType, long previouslsn, boolean timeToLiveExpired
ChangeFeedOperationType -> CREATE, REPLACE and DELETE
Deprecated old APIs in ChangeFeedPolicy

    @Beta(value = Beta.SinceVersion.V4_12_0,
        warningText = Beta.PREVIEW_SUBJECT_TO_CHANGE_WARNING)
    @Deprecated(since = "V4_37_0", forRemoval = true)
    public static ChangeFeedPolicy createIncrementalPolicy();


   @Beta(value = Beta.SinceVersion.V4_12_0,
        warningText = Beta.PREVIEW_SUBJECT_TO_CHANGE_WARNING)
    @Deprecated(since = "V4_37_0", forRemoval = true)
    public static ChangeFeedPolicy createFullFidelityPolicy(Duration retentionDuration);


   @Beta(value = Beta.SinceVersion.V4_12_0,
        warningText = Beta.PREVIEW_SUBJECT_TO_CHANGE_WARNING)
    @Deprecated(since = "V4_37_0", forRemoval = true)
    public Duration getFullFidelityRetentionDuration();

New APIs added in ChangeFeedPolicy

    @Beta(value = Beta.SinceVersion.V4_37_0,
        warningText = Beta.PREVIEW_SUBJECT_TO_CHANGE_WARNING)
    public static ChangeFeedPolicy createAllVersionsAndDeletesPolicy(Duration retentionDuration)

    
    @Beta(value = Beta.SinceVersion.V4_12_0,
        warningText = Beta.PREVIEW_SUBJECT_TO_CHANGE_WARNING)
    public static ChangeFeedPolicy createLatestVersionPolicy()


    @Beta(value = Beta.SinceVersion.V4_37_0,
        warningText = Beta.PREVIEW_SUBJECT_TO_CHANGE_WARNING)
    public Duration getAllVersionsAndDeletesRetentionDuration()

Deprecated APIs in CosmosChangeFeedRequestOptions

    @Beta(value = Beta.SinceVersion.V4_12_0, warningText =
        Beta.PREVIEW_SUBJECT_TO_CHANGE_WARNING)
    @Deprecated(since = "V4_37_0", forRemoval = true)
    public CosmosChangeFeedRequestOptions fullFidelity()

New APIs added in CosmosChangeFeedRequestOptions

    @Beta(value = Beta.SinceVersion.V4_37_0, warningText =
        Beta.PREVIEW_SUBJECT_TO_CHANGE_WARNING)
    public CosmosChangeFeedRequestOptions allVersionsAndDeletes()

Aug 11 '22 01:08 kushagraThapar

API change check

APIView has identified API level changes in this PR and created following API reviews.

azure-cosmos

Aug 11 '22 01:08 azure-sdk

/azp run java - cosmos - tests

Aug 11 '22 23:08 kushagraThapar

Azure Pipelines successfully started running 1 pipeline(s).

Aug 11 '22 23:08 azure-pipelines[bot]

This pull request is protected by Check Enforcer.

What is Check Enforcer?

Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass.

Why am I getting this message?

You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged.

What should I do now?

If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows: /check-enforcer evaluate Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command: /check-enforcer override Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

What if I am onboarding a new service?

Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment: /azp run prepare-pipelines This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment: /azp run java - [service] - ci