[jira] [Resolved] (STORM-3005) [DRPC] LinearDRPCTopologyBuilder shouldn't be deprecated
[ https://issues.apache.org/jira/browse/STORM-3005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans resolved STORM-3005. Resolution: Fixed Fix Version/s: 1.2.2 1.0.7 1.1.3 2.0.0 Thanks [~rauluka], I merged this into all of the release lines since 1.0.x > [DRPC] LinearDRPCTopologyBuilder shouldn't be deprecated > - > > Key: STORM-3005 > URL: https://issues.apache.org/jira/browse/STORM-3005 > Project: Apache Storm > Issue Type: Task >Affects Versions: 1.1.1, 1.2.1 >Reporter: Lukasz Gebel >Assignee: Lukasz Gebel >Priority: Major > Labels: pull-request-available > Fix For: 2.0.0, 1.1.3, 1.0.7, 1.2.2 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Apache Storm provides DRPC functionality. However LinearDRPCTopologyBuilder > is deprecated due to: "Trident subsumes the functionality provided by this > class, so it's deprecated". I think it shouldn't be so, because you may still > want to use DRPC without Trident. > LinearDRPCTopologyBuilder is also mentioned as a part of example in current > documentation: [http://storm.apache.org/releases/1.2.1/Distributed-RPC.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (STORM-3022) Decouple storm-hive UTs with Hive
[ https://issues.apache.org/jira/browse/STORM-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated STORM-3022: -- Labels: pull-request-available (was: ) > Decouple storm-hive UTs with Hive > - > > Key: STORM-3022 > URL: https://issues.apache.org/jira/browse/STORM-3022 > Project: Apache Storm > Issue Type: Improvement > Components: storm-hive >Reporter: Jungtaek Lim >Assignee: Jungtaek Lim >Priority: Major > Labels: pull-request-available > > The unit tests in storm-hive are running Hive instance and interact with > Hive. This creates unnecessary directories and more likely easier to be > broken. Given that they're UTs, it would be better to decouple Hive from > storm-hive tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (STORM-3021) RAS doesn't horror topology.worker
Ethan Li created STORM-3021: --- Summary: RAS doesn't horror topology.worker Key: STORM-3021 URL: https://issues.apache.org/jira/browse/STORM-3021 Project: Apache Storm Issue Type: Bug Reporter: Ethan Li Continue the discussion from STORM-2983. ResourceAware schedule dynamically calculated the number of workers and doesn't horror topology.worker. So we need to 1) update docs to avoid confusion; 2) check what RAS breaks and fix them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (STORM-917) Ability to emit messages from a kafka spout to a specific stream
[ https://issues.apache.org/jira/browse/STORM-917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated STORM-917: - Labels: pull-request-available (was: ) > Ability to emit messages from a kafka spout to a specific stream > - > > Key: STORM-917 > URL: https://issues.apache.org/jira/browse/STORM-917 > Project: Apache Storm > Issue Type: Improvement > Components: storm-kafka >Reporter: anishek >Priority: Major > Labels: pull-request-available > > Today even if we have multiple spouts in storm they will all emit on the same > "default" stream. Having an ability to configure the stream that a kafka > spout emits to would be great. By default should emit to the "default" stream -- This message was sent by Atlassian JIRA (v7.6.3#76005)
