[
https://issues.apache.org/jira/browse/STORM-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15323099#comment-15323099
]
Narendra Bidari commented on STORM-1898:
----------------------------------------
[[email protected]][~priyank780] : any thoughts?
> MAX_BATCH_SIZE_CONF not working in Trident storm Spout
> -------------------------------------------------------
>
> Key: STORM-1898
> URL: https://issues.apache.org/jira/browse/STORM-1898
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-kafka
> Affects Versions: 1.0.0
> Reporter: Narendra Bidari
> Priority: Blocker
>
> Ideally Trident process should process tuples in Batch.
> ex >
> https://github.com/apache/storm/blob/ab66003c18fe4f8c0926b3219408b735b2ce2adf/storm-core/src/jvm/org/apache/storm/trident/spout/RichSpoutBatchExecutor.java
> there is a parameter called MAX_BATCH_SIZE_CONF which limits the size of the
> batch.
> This parameter is not present in TridentKafkaEmitter.
> https://github.com/apache/storm/blob/1.x-branch/external/storm-kafka/src/jvm/org/apache/storm/kafka/trident/TridentKafkaEmitter.java
> ---------------
> Problem is that now everytime the topology restarts it just fetches all
> messages from Kafka.
> Could any one throw some idea on it, I certainly feel its a bug.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
