Skip to content

Comments

Resuming query from a continuation token after split#18698

Merged
mbhaskar merged 2 commits intoAzure:masterfrom
mbhaskar:split-continuationtoken
Jan 21, 2021
Merged

Resuming query from a continuation token after split#18698
mbhaskar merged 2 commits intoAzure:masterfrom
mbhaskar:split-continuationtoken

Conversation

@mbhaskar
Copy link
Member

@mbhaskar mbhaskar commented Jan 20, 2021 •
edited
Loading

@ghost ghost added the Cosmos label Jan 20, 2021
@check-enforcer
Copy link

check-enforcer bot commented Jan 20, 2021

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

@mbhaskar
Copy link
Member Author

mbhaskar commented Jan 20, 2021

/azp run java - cosmos - tests

@azure-pipelines
Copy link

azure-pipelines bot commented Jan 20, 2021

Azure Pipelines successfully started running 1 pipeline(s).

moderakh
moderakh approved these changes Jan 20, 2021
View reviewed changes
Copy link
Contributor

@moderakh moderakh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks.

bchong95
bchong95 approved these changes Jan 20, 2021
View reviewed changes
Copy link

@bchong95 bchong95 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@mbhaskar
Copy link
Member Author

mbhaskar commented Jan 20, 2021

/azp run java - cosmos - ci

@azure-pipelines
Copy link

azure-pipelines bot commented Jan 20, 2021

Azure Pipelines successfully started running 1 pipeline(s).

@mbhaskar
Copy link
Member Author

mbhaskar commented Jan 21, 2021

/azp run java - cosmos - ci

@azure-pipelines
Copy link

azure-pipelines bot commented Jan 21, 2021

Azure Pipelines successfully started running 1 pipeline(s).

@mbhaskar
Copy link
Member Author

mbhaskar commented Jan 21, 2021

/azp run java - cosmos - tests

@azure-pipelines
Copy link

azure-pipelines bot commented Jan 21, 2021

Azure Pipelines successfully started running 1 pipeline(s).

@mbhaskar
Copy link
Member Author

mbhaskar commented Jan 21, 2021

/azp run java - cosmos - ci

@azure-pipelines
Copy link

azure-pipelines bot commented Jan 21, 2021

Azure Pipelines successfully started running 1 pipeline(s).

@mbhaskar mbhaskar merged commit 0ab856a into Azure:master Jan 21, 2021
azure-sdk pushed a commit to azure-sdk/azure-sdk-for-java that referenced this pull request Apr 20, 2022
CodeGen from PR 18698 in Azure/azure-rest-api-specs
6183b15 
Kipartha/execution details action start end (Azure#18698)

* Add action start/end time.

* Update examples with action start/end times.

* fix typo in description.

Co-authored-by: kipartha <kipartha@microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@FabianMeiswinkel FabianMeiswinkel Awaiting requested review from FabianMeiswinkel

@kirankumarkolli kirankumarkolli Awaiting requested review from kirankumarkolli

@kushagraThapar kushagraThapar Awaiting requested review from kushagraThapar

@milismsft milismsft Awaiting requested review from milismsft

@simplynaveen20 simplynaveen20 Awaiting requested review from simplynaveen20

@xinlian12 xinlian12 Awaiting requested review from xinlian12

2 more reviewers

@moderakh moderakh moderakh approved these changes

@bchong95 bchong95 bchong95 approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

Cosmos

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Split Proof Continuation Token on Azure Cosmos Java V4 SDK

3 participants

@mbhaskar @bchong95 @moderakh