[
https://issues.apache.org/jira/browse/STORM-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15108779#comment-15108779
]
ASF GitHub Bot commented on STORM-1214:
---------------------------------------
Github user revans2 commented on a diff in the pull request:
https://github.com/apache/storm/pull/1029#discussion_r50272891
--- Diff: storm-core/src/jvm/org/apache/storm/trident/Stream.java ---
@@ -57,6 +57,23 @@
import org.apache.storm.trident.state.StateUpdater;
import org.apache.storm.trident.util.TridentUtils;
+/**
+ * A Stream represents the core data model in Trident, and can be thought
of as a "stream" of tuples that are processed
+ * as a series of small batches. A stream is partitioned accross the nodes
in the in the cluster, and operations are
--- End diff --
`the nodes in the *in the* cluster` the second `in the` should probably go
away.
> Trident API Improvements
> ------------------------
>
> Key: STORM-1214
> URL: https://issues.apache.org/jira/browse/STORM-1214
> Project: Apache Storm
> Issue Type: Bug
> Reporter: P. Taylor Goetz
> Assignee: P. Taylor Goetz
>
> There are a few idiosyncrasies in the Trident API that can sometimes trip
> developers up (e.g. when and how to set the parallelism of components). There
> are also a few areas where the API could be made slightly more intuitive
> (e.g. add Java 8 streams-like methods like {{filter()}}, {{map()}},
> {{flatMap()}}, etc.).
> Some of these concerns can be addressed through documentation, and some by
> altering the API. Since we are approaching a 1.0 release, it would be good to
> address any API changes before a major release.
> The goal of this JIRA is to identify specific areas of improvement and
> formulate an implementation that addresses them.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
