pulsar-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] srkukarni opened a new pull request #3608: Added ability to specify consumer queue size for function input topics
Date Fri, 15 Feb 2019 20:11:19 GMT
srkukarni opened a new pull request #3608: Added ability to specify consumer queue size for
function input topics
URL: https://github.com/apache/pulsar/pull/3608
   ### Motivation
   Currently the receiver queue size of the consumer of a function input is set to whatever
the default is. In cases where there are big messages, having an ability to control this size
is essential to maintain reduced memory profile for functions. This pr adds the ability for
functions to specify this queue size on a per input topic.
   ### Modifications
   *Describe the modifications you've done.*
   ### Verifying this change
   - [ ] Make sure that the change passes the CI checks.
   *(Please pick either of the following options)*
   This change is a trivial rework / code cleanup without any test coverage.
   This change is already covered by existing tests, such as *(please describe tests)*.
   This change added tests and can be verified as follows:
     - *Added integration tests for end-to-end deployment with large payloads (10MB)*
     - *Extended integration test for recovery after broker failure*
   ### 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
     - Does this pull request introduce a new feature? (yes / no)
     - If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
     - If a feature is not applicable for documentation, explain why?
     - If a feature is not documented yet in this PR, please create a followup issue for adding
the documentation

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

View raw message