Skip to content

Conversation

@JoshLove-msft
Copy link
Member

@JoshLove-msft JoshLove-msft commented Sep 8, 2020

Fixes #14765

Azure.Core.Experimental was already released so this will have to wait until next release for the Core changes, but they are an implementation detail that the SB library is not depending on so it should be fine to release SB this month.

@JoshLove-msft JoshLove-msft added Client This issue is related to a non-management package and removed Azure.Core labels Sep 8, 2020
@JoshLove-msft
Copy link
Member Author

/azp run net - servicebus - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Copy link
Contributor

@MiYanni MiYanni left a comment

Choose a reason for hiding this comment

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

Looks good. I like that the constants are all in the same place now.

@JoshLove-msft
Copy link
Member Author

/azp run net - servicebus - tests

@JoshLove-msft
Copy link
Member Author

/azp run net - servicebus - ci

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

1 similar comment
@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@JoshLove-msft
Copy link
Member Author

/azp run net - core - ci

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Copy link
Contributor

Choose a reason for hiding this comment

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

Is it a user property? This is a system property key, set by the broker.

Copy link
Member Author

Choose a reason for hiding this comment

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

It is in the user properties bag since the user can actually set the reason/error when deadlettering.

Copy link
Contributor

Choose a reason for hiding this comment

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

It's not set directly, unlike user set properties/headers. The value is passed into dead-letter method and set by the broker.

Also, it's a single usecase. Messages dead letter for other reasons and messages are neither controlled nor set by users but the broker.

Copy link
Member Author

Choose a reason for hiding this comment

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

Correct, but the doc comments were intended to indicate where the property key lives. It wasn't meant to imply that a user can just change it whenever. I can clarify.

Copy link
Contributor

Choose a reason for hiding this comment

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

Same as above

@JoshLove-msft
Copy link
Member Author

/azp run net - servicebus - ci

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@JoshLove-msft JoshLove-msft merged commit 1a2cfa3 into Azure:master Oct 2, 2020
annelo-msft pushed a commit to annelo-msft/azure-sdk-for-net that referenced this pull request Feb 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Client This issue is related to a non-management package Service Bus

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Clear out AmqpAnnotatedMessage properties for received message when copying

3 participants