[GitHub] storm issue #1656: STORM-2057 Support JOIN statement in Storm SQL

Github user arunmahadevan commented on the issue: https://github.com/apache/storm/pull/1656 +1 --- 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

Re: How does Storm's OutputCollector work?

Hi T.I., Answered your question on StackOverflow. Hope that helps. Thanks, Manu On Mon, Sep 12, 2016 at 11:36 AM Tech Id wrote: > Hi, > > Can someone help provide a better understanding of Storm's OutputCollector? > A question for the same can be found at > >

[GitHub] storm issue #1661: [STORM-2071] Add in retry after rebalance in unit test

Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1661 @ppoulosk Do you have any update on this? --- 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

[jira] [Resolved] (STORM-1970) external project examples refator

[ https://issues.apache.org/jira/browse/STORM-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim resolved STORM-1970. - Resolution: Fixed Fix Version/s: 1.1.0 2.0.0 Thanks [~vesense], I

[GitHub] storm pull request #1565: STORM-1970: external project examples refator

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1565 --- 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

How does Storm's OutputCollector work?

Hi, Can someone help provide a better understanding of Storm's OutputCollector? A question for the same can be found at http://stackoverflow.com/questions/39439336/how-does-storms-outputcollector-work Thanks, T.I.

[jira] [Resolved] (STORM-2086) use DefaultTopicSelector instead of creating a new one

[ https://issues.apache.org/jira/browse/STORM-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim resolved STORM-2086. - Resolution: Fixed Fix Version/s: 1.0.3 1.1.0 2.0.0

[GitHub] storm pull request #1678: [STORM-2086][SQL] use DefaultTopicSelector instead...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1678 --- 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

[GitHub] storm issue #1656: STORM-2057 Support JOIN statement in Storm SQL

Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1656 @arunmahadevan @harshach I just addressed your review comments. Please take a look again. Adding Javadoc for Trident is not easy task since there's no method which has javadoc on

storm trident design doc

Hi, storm dev team: I'm interested in the internal design of storm trident, however I can not find any doc about it on the web. The design of trident seems complex and difficult to infer from source code, so I want to ask is there any design doc about it? -- Liu, Renjie Software Engineer, MVAD

[jira] [Commented] (STORM-1444) Support EXPLAIN statement in StormSQL

[ https://issues.apache.org/jira/browse/STORM-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15482854#comment-15482854 ] Jungtaek Lim commented on STORM-1444: - Yes I lost my draft comment which describes how Calcite

[jira] [Commented] (STORM-1444) Support EXPLAIN statement in StormSQL

[ https://issues.apache.org/jira/browse/STORM-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15482839#comment-15482839 ] Manu Zhang commented on STORM-1444: --- I wonder whether this has native support in Calcite. > Support

[jira] [Commented] (STORM-1444) Support EXPLAIN statement in StormSQL

[ https://issues.apache.org/jira/browse/STORM-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15482777#comment-15482777 ] Jungtaek Lim commented on STORM-1444: - No opinion received for this. I'll just add 'explain mode' and

[GitHub] storm issue #1676: STORM-2085: Remove guava from storm-core pom.

Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1676 We shaded Guava which downstream shouldn't rely on, so I think we can apply this to 1.x if applicable. (I'm not sure we also want to apply this to 1.0.x.) ps. Since external modules

[GitHub] storm issue #1678: [STORM-2086][SQL] use DefaultTopicSelector instead of cre...

Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1678 +1 Nice finding. --- 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,

[jira] [Commented] (STORM-2088) Typos in documentation "Guaranteeing Message Processing"

[ https://issues.apache.org/jira/browse/STORM-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15482765#comment-15482765 ] Bruno P. Kinoshita commented on STORM-2088: --- Thanks [~kabhwan], pull request submitted

[GitHub] storm pull request #1680: Minor typos in documentation

GitHub user kinow opened a pull request: https://github.com/apache/storm/pull/1680 Minor typos in documentation There's a placeholder ticket in JIRA https://issues.apache.org/jira/browse/STORM-2088 Two minor typos in the "Guaranteeing Message Processing" documentation.

[jira] [Commented] (STORM-2088) Typos in documentation "Guaranteeing Message Processing"

[ https://issues.apache.org/jira/browse/STORM-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15482719#comment-15482719 ] Jungtaek Lim commented on STORM-2088: - [~kinow] You can create pull request on Github mirror, and

[jira] [Updated] (STORM-2088) Typos in documentation "Guaranteeing Message Processing"

[ https://issues.apache.org/jira/browse/STORM-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno P. Kinoshita updated STORM-2088: -- Attachment: STORM-2088-1.patch Couldn't find a git repo, so I believe the repository

[jira] [Created] (STORM-2088) Typos in documentation "Guaranteeing Message Processing"

Bruno P. Kinoshita created STORM-2088: - Summary: Typos in documentation "Guaranteeing Message Processing" Key: STORM-2088 URL: https://issues.apache.org/jira/browse/STORM-2088 Project: Apache

Re: How to debug spout failures

Your tuple may be timing out, try increasing tuple timeout and also check ur setting of max pending tuple, you may not want unlimited tuple going through ur pipeline. Ravi. On 11 Sep 2016 7:09 p.m., "pradeep s" wrote: Hi, I have a storm topology running in storm

How to debug spout failures

Hi, I have a storm topology running in storm 1.0.0 in AWS with one spout which is reading messages from AWS SQS , then sends to a database insert bolt. The same tuple is emitted from database bolt to a S3 write bolt. Final bolt in the topo is a SQS message deletion action. All these are working

Re: [VOTE] Release Apache Storm 0.10.2 (rc2)

+1 Thanks for adding STORM-2042 in rc2. ~Satish. On 9/11/16, 5:46 PM, "Jungtaek Lim" wrote: +1 from me. I checked 0.10.2 RC1 so this is OK for me to not test again. Thanks, Jungtaek Lim (HeartSaVioR) 2016년 9월 10일 (토) 오전 3:55, Bobby Evans

Re: [VOTE] Release Apache Storm 0.10.2 (rc2)

+1 from me. I checked 0.10.2 RC1 so this is OK for me to not test again. Thanks, Jungtaek Lim (HeartSaVioR) 2016년 9월 10일 (토) 오전 3:55, Bobby Evans 님이 작성: > +1 - Bobby > > On Thursday, September 8, 2016 3:53 PM, P. Taylor Goetz < > ptgo...@gmail.com> wrote: > > >

[GitHub] storm issue #1359: STORM-1239: port backtype.storm.scheduler.IsolationSchedu...

Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1359 @vesense I guess you may need to fix this issue first, which is what you found: ``` classname: org.apache.storm.nimbus-test / testname: test-isolated-assignment expected: (= 1

[jira] [Commented] (STORM-2087) Storm-kafka-client: Failed tuples are not always replayed

[ https://issues.apache.org/jira/browse/STORM-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15481263#comment-15481263 ] Jeff Fenchel commented on STORM-2087: - The fix is now in that PR as well > Storm-kafka-client: Failed