Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Feature/servicebus newapi crosstxn datatype from june master branch #22426

Merged
merged 26 commits into from
Jun 23, 2021
Merged

Feature/servicebus newapi crosstxn datatype from june master branch #22426

merged 26 commits into from
Jun 23, 2021

Conversation

hemanttanwar
Copy link
Contributor

@hemanttanwar hemanttanwar commented Jun 21, 2021 •
edited
Loading

This PR is for merging following features into main branch for service bus

  1. Supporting AMQP Data Types
  2. Support cross entity transactions
  3. Added support receiving dead-letter queue (DLQ) for 'ServiceBusProcessorClient' and session receiver using 'subQueue'

API View :
core-amqp API View: https://apiview.dev/Assemblies/Review/06064a28f01e460ab065443b6f6e78e7?diffRevisionId=d4e3f00a3e0a4473836a3c27e039c3e1&doc=False&diffOnly=False

Service Bus: https://apiview.dev/Assemblies/Review/6af850ed7eb04843a6897afbe13cdd28?diffRevisionId=7d50e170bcc342778fd235fee3867293&doc=False&diffOnly=False

1, 2 : These API were reviewed by Srikanta and Jonathan.

Planned GA Release Week of 6/22/21

hemanttanwar and others added 19 commits April 5, 2021 10:59
@hemanttanwar
Service bus adding max auto lock renew duration in processor client (#…
754aa91 
…20317)

* Added API in builder  for "adding max auto lock renew duration in processor client"
Merge branch 'feature/servicebus-support-amqp-data-types-17614' of ht…
44ed5a3 
…tps://github.com/Azure/azure-sdk-for-java into feature/servicebus-support-amqp-data-types-17614
@hemanttanwar
Service Bus - Merging previously approved -cross transaction feature …
eb2fe35 
…- into feature branch - preparation for April release. (#20356)

* ServiceBus - cross entity transaction  feature  (#19863)

New Feature: Cross entity transaction API
Merge branch 'master' into feature/servicebus-support-amqp-data-types…
edd2253 
…-17614
Marge master
40db68b
@hemanttanwar
Service bus : Amqp Types SEQUENCE and VALUE (#20285)
a3ec7ae 
* Adding feature AMQP SEQUENCE/VALUE data type implementation
Merge master into branch
28d97dc
Merge master into branch
48264cb
beta version change
09e3715
getting ready to release beta
9bd0245
Updating beta version for event hubs
dd39f58
Fixing unit test case
0b8acfd
Removing unwanted import
ff627eb
@hemanttanwar
Fixing test subscriber name (#20666)
1cc58cc 
Co-authored-by: hemanttanwar <[email protected]>
@hemanttanwar
SB april beta release updates (#20672)
5883ccb 
* SB april beta release updates
@azure-sdk
Increment package version after release of com.azure azure-messaging-…
060fe17 
…servicebus (#20690)
@YijunXieMS
Use multiple subscribers for maxConcurrentCalls in ServiceBusProces…
a59869b 
…sorClient (#21085)
REsolved conflicts
94f076b
Merge main into the branch
90d4849
@ghost ghost added Azure.Core azure-core Service Bus azure-spring All azure-spring related issues labels Jun 21, 2021
@check-enforcer
Copy link

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

YijunXieMS
YijunXieMS approved these changes Jun 22, 2021
View reviewed changes
Copy link
Contributor

@YijunXieMS YijunXieMS left a comment

Choose a reason for hiding this comment

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

Approved to merge to master since this has been reviewed and previewed for a while.

@hemanttanwar
Copy link
Contributor Author

/azp run java - servicebus - ci

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@hemanttanwar
Copy link
Contributor Author

/azp run java - servicebus - ci

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@hemanttanwar
Copy link
Contributor Author

/azp run java - servicebus - ci

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@hemanttanwar
Copy link
Contributor Author

/azp run java - servicebus - ci

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@hemanttanwar hemanttanwar merged commit 064db64 into main Jun 23, 2021
@hemanttanwar hemanttanwar deleted the feature/servicebus-newapi-crosstxn-datatype-from-june-master-branch branch June 23, 2021 00:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@srnagar srnagar srnagar approved these changes

@YijunXieMS YijunXieMS YijunXieMS approved these changes

@alzimmermsft alzimmermsft Awaiting requested review from alzimmermsft

@anuchandy anuchandy Awaiting requested review from anuchandy anuchandy is a code owner

@backwind1233 backwind1233 Awaiting requested review from backwind1233

@chenrujun chenrujun Awaiting requested review from chenrujun

@conniey conniey Awaiting requested review from conniey conniey is a code owner

@danieljurek danieljurek Awaiting requested review from danieljurek

@g2vinay g2vinay Awaiting requested review from g2vinay

@jianghaolu jianghaolu Awaiting requested review from jianghaolu

@JimSuplizio JimSuplizio Awaiting requested review from JimSuplizio

@lmolkova lmolkova Awaiting requested review from lmolkova lmolkova is a code owner

@mitchdenny mitchdenny Awaiting requested review from mitchdenny

@samvaity samvaity Awaiting requested review from samvaity

@saragluna saragluna Awaiting requested review from saragluna

@stliu stliu Awaiting requested review from stliu

@yiliuTo yiliuTo Awaiting requested review from yiliuTo

@yvgopal yvgopal Awaiting requested review from yvgopal

Assignees
No one assigned
Labels
Azure.Core azure-core azure-spring All azure-spring related issues Service Bus
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@hemanttanwar @YijunXieMS @srnagar @azure-sdk