[
https://issues.apache.org/jira/browse/STORM-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15108836#comment-15108836
]
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_r50277718
--- Diff:
storm-core/src/jvm/org/apache/storm/trident/operation/TridentCollector.java ---
@@ -20,7 +20,33 @@
import java.util.List;
+/**
+ * Interface for publishing tuples to a stream and reporting exceptions
(to be displayed in Storm UI).
+ *
+ * Trident components that have the ability to emit tuples to a stream are
passed an instance of this
+ * interface.
+ *
+ * For example, to emit a new tuple to a stream, you would do something
like the following:
+ *
+ * ```java
+ * collector.emit(new Values("a", "b", "c"));
+ * ```
+ * @see storm.trident.Stream
+ * @see backtype.storm.tuple.Values
--- End diff --
Links need org.apache here too.
> 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)
