Github user roshannaik commented on a diff in the pull request:

    https://github.com/apache/storm/pull/1914#discussion_r99713201
  
    --- Diff: docs/Joins.md ---
    @@ -0,0 +1,102 @@
    +---
    +title: Joining Streams in Storm Core
    +layout: documentation
    +documentation: true
    +---
    +
    +Storm core supports joining multiple data streams into one with the help 
of `JoinBolt`.
    +`JoinBolt` is a Windowed bolt, i.e. it waits for the configured window 
duration to match up the
    +tuples among the streams being joined. This helps align the streams within 
the Window boundary.
    +
    +Each of `JoinBolt`'s incoming data streams must be Fields Grouped on a 
single field. A stream 
    +should only be joined with the other streams using the field on which it 
has been FieldsGrouped.  
    +Knowing this will help understand the join syntax described below.  
    +
    +## Performing Joins
    +Consider the following SQL join involving 4 tables called: stream1, 
stream2, stream3 & stream4:
    +
    +```sql
    +select  userId, key4, key2, key3
    +from    stream1 
    +join       stream2  on stream2.userId =  stream1.key1
    +join       stream3  on stream3.key3   =  stream2.userId
    +left join  stream4  on stream4.key4   =  stream3.key3
    +```
    +
    +This could be expressed using `JoinBolt` over 4 similarly named streams 
as: 
    +
    +```java
    +new JoinBolt(JoinBolt.Selector.STREAM, "stream1", "key1")               // 
from stream1  
    +                            .join     ("stream2", "userId",  "stream1") // 
join      stream2  on stream2.userId = stream1.key1
    +                            .join     ("stream3", "key3",    "stream2") // 
join      stream3  on stream3.key3   = stream2.userId   
    +                            .leftjoin ("stream4", "key4",    "stream3") // 
left join stream4  on stream4.key4   = stream3.key3
    +                            .select("userId, key4, key2, key3")         // 
chose output fields
    --- End diff --
    
    1. Conversion it to list is done internally.  Chose CSV string instead of 
list to make it easier for end users (less typing) ... without loss of 
functionality. 
    
    2. I think .. as of now its not supported.. let me take a look and add it 
if not there already.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to