Tigon SQL

[edug...@gmail.com]

Hello everyone,

I wanted to know if it was possible to modify the SQLJoinFlow example, so instead of receiving the input from the http port receive the input from another flowlet and then do the SQL query. In other words merge the TwitterAnalytics app with the SQLJoinFlow, so TweetCollector class will collect the tweets from Twitter and transfer the data between the TweetCollector and the Analytics flowlet and then the Analytics flowlet will do the SQL join on the data received from the TweetCollector?

Thanks.

[Gokul Gunasekaran]

Hi,

Currently it is not possible to do that. I have created a JIRA (https://issues.cask.co/browse/TIGON-154) to track this feature. I have added the reasoning behind using InputFlowlet as the first Flowlet of a Tigon Flow in the JIRA. I am copy/pasting it here for reference.

InputFlowlet (Tigon SQL flowlet) currently uses in-memory queue and doesn't provide persistence and so in case of failure of the flowlet container, data held in-memory will be lost. This is one of the reasons why InputFlowlet is used as (optionally) first flowlet of a Tigon Flow so that it can improve the throughput of input events ingested by trading off persistence (so that uninteresting events can be dropped right away) and subsequent Flowlets can process events that are of interest and there Tigon provides full persistence (and of course, exactly-once processing guarantees) using Queues implemented in HBase.

Thanks,

Gokul

--
You received this message because you are subscribed to the Google Groups "Tigon User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tigon-user+...@googlegroups.com.
To post to this group, send email to tigon...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tigon-user/0468cc33-ca41-4f39-b3fa-caa9016e4c3d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.