[
https://issues.apache.org/jira/browse/BEAM-3819?focusedWorklogId=80987&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-80987
]
ASF GitHub Bot logged work on BEAM-3819:
----------------------------------------
Author: ASF GitHub Bot
Created on: 15/Mar/18 21:37
Start Date: 15/Mar/18 21:37
Worklog Time Spent: 10m
Work Description: jbonofre commented on issue #4851: [BEAM-3819] Add
withLimit() option to KinesisIO
URL: https://github.com/apache/beam/pull/4851#issuecomment-373531082
Generally speaking, we try to avoid to expose user configuration in the IO
(see
https://beam.apache.org/contribute/ptransform-style-guide/#what-parameters-to-expose).
I wonder if it's worth to expose `limit` to the user as it's more an IO
constraint to me.
Thoughts ?
----------------------------------------------------------------
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:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 80987)
Time Spent: 50m (was: 40m)
> Add withLimit() option to KinesisIO
> -----------------------------------
>
> Key: BEAM-3819
> URL: https://issues.apache.org/jira/browse/BEAM-3819
> Project: Beam
> Issue Type: Improvement
> Components: io-java-kinesis
> Reporter: Jean-Baptiste Onofré
> Assignee: Alexey Romanenko
> Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> In some cases, the user might need to set the {{limit}} on the
> {{SimplifiedKinesisClient}}, especially for performance reason, depending of
> the number of records.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
