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.

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

[CAPI] Support setting priority for consumers #12526

Merged
merged 1 commit into from
Nov 2, 2021
Merged

[CAPI] Support setting priority for consumers #12526

merged 1 commit into from
Nov 2, 2021

Conversation

k2la
Copy link
Contributor

@k2la k2la commented Oct 29, 2021

Motivation

We would like to make it possible for C API based client library to set the priority level for consumers.

Modifications

Add methods to set/get priority level for consumers.

Verifying this change

  • Make sure that the change passes the CI checks.

Does this pull request potentially affect one of the following parts:

If yes was chosen, please highlight the changes

  • Dependencies (does it add or upgrade a dependency): (yes / no)
  • The public API: (yes / no)
  • The schema: (yes / no / don't know)
  • The default values of configurations: (yes / no)
  • The wire protocol: (yes / no)
  • The rest endpoints: (yes / no)
  • The admin cli options: (yes / no)
  • Anything that affects deployment: (yes / no / don't know)

Documentation

Check the box below and label this PR (if you have committer privilege).

Need to update docs?

  • doc-required

    (If you need help on updating docs, create a doc issue)

  • no-need-doc

    (Please explain why)

  • doc

    (If this PR contains doc changes)

@k2la k2la self-assigned this Oct 29, 2021
@github-actions
Copy link

@k2la:Thanks for your contribution. For this PR, do we need to update docs?
(The PR template contains info about doc, which helps others know more about the changes. Can you provide doc-related info in this and future PR descriptions? Thanks)

@github-actions
Copy link

@k2la:Thanks for your contribution. For this PR, do we need to update docs?
(The PR template contains info about doc, which helps others know more about the changes. Can you provide doc-related info in this and future PR descriptions? Thanks)

@Anonymitaet
Copy link
Member

Hi @k2la do we need to update docs for this PR?

@BewareMyPower BewareMyPower added doc-not-needed Your PR changes do not impact docs and removed doc-label-missing labels Nov 2, 2021
@BewareMyPower BewareMyPower added this to the 2.10.0 milestone Nov 2, 2021
@BewareMyPower BewareMyPower merged commit a75a974 into apache:master Nov 2, 2021
hangc0276 pushed a commit that referenced this pull request Nov 4, 2021
### Motivation

We would like to make it possible for C API based client library to set the priority level for consumers.

### Modifications

Add methods to set/get priority level for consumers.

Co-authored-by: k2la <yfuruta@yahoo-corp.jp>
(cherry picked from commit a75a974)
@hangc0276 hangc0276 added cherry-picked/branch-2.8 Archived: 2.8 is end of life and removed cherry-picked/branch-2.8 Archived: 2.8 is end of life release/2.8.2 labels Nov 4, 2021
@hangc0276
Copy link
Contributor

This PR need #12076 support, which is a new feature, and will be release in 2.9.0. So remove 2.8.2 tag.

@k2la k2la deleted the capi_priority_level branch November 5, 2021 01:59
eolivelli pushed a commit to eolivelli/pulsar that referenced this pull request Nov 29, 2021
### Motivation

We would like to make it possible for C API based client library to set the priority level for consumers.

### Modifications

Add methods to set/get priority level for consumers.

Co-authored-by: k2la <yfuruta@yahoo-corp.jp>
codelipenghui pushed a commit that referenced this pull request Dec 20, 2021
### Motivation

We would like to make it possible for C API based client library to set the priority level for consumers.

### Modifications

Add methods to set/get priority level for consumers.

Co-authored-by: k2la <yfuruta@yahoo-corp.jp>
(cherry picked from commit a75a974)
@codelipenghui codelipenghui added the cherry-picked/branch-2.9 Archived: 2.9 is end of life label Dec 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cherry-picked/branch-2.9 Archived: 2.9 is end of life doc-not-needed Your PR changes do not impact docs release/2.9.2
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants