The execute phase is pipelined and only the commits are strictly ordered.
So a trident bolt could receive tuples from batch1, batch2 and again batch1 and
so on. The framework internally maintains separate context for each batch and
the execute is invoked with the respective batch’s context. The
Hi Daniela,
For storm core, windowed bolts would give you the tuples in the last minute but
you would have to do the grouping yourself. You could of-course use a fields
grouping to split the load across the windowed bolts. For trident you might
want to take a look at the windowing apis that wer
+1
Verified build from the source archive, deployed .tar.gz binary and ran a
sample topology.
- Arun
On 4/6/16, 2:40 AM, "P. Taylor Goetz" wrote:
>+1 (binding)
>
>- Verified build from source archive with `mvn clean install -P all-tests`
>- Checked LICENSE and NOTICE files
>- Deployed to a
Hi Matthias,
WindowedBolt does support event time. In trident its is not yet exposed.
Hi Daniela,
You could solve your use cases in different ways. One would be to have a
WindowedBolt with a 1 min tumbling window, do your custom aggregation (e.g.
sum) every time the window tumbles and emit th
+1 (binding)
- Extracted all binaries.
- Ran sample topologies.
- Verified Stateful bolt changes added in 1.0.1 works as expected.
Thanks,
Arun
On 5/3/16, 4:52 AM, "Harsha" wrote:
>+1 (binding)
> - Deployed 3-node cluster and example topologies
> - Verified the binaries signature.
>Thank
+1 (binding)
- Extracted binaries
- Ran sample topologies
- Browsed storm UI
Thanks,
Arun
On 4/28/16, 12:01 PM, "Jungtaek Lim" wrote:
>+1 (binding)
>
>- testing with source distribution : OK
> - unzip : OK
> - building from source dist : OK
>- how to build: running `mvn -P all-tests c
Hi Balázs,
The idea sounds good.
Only whitelisted configs can be overridden at component level. The java configs
are converted to clojure variables by replacing _ (underscore) with - (hyphen)
and you need to add and entry like [1] in executor.clj to get it working.
- Arun
[1]
https://github
Shade and relocate the external modules sounds ok as a short term solution.
For the long term we should consider something like the second option to add
external modules without shipping uber jars.
Thanks,
Arun
On 7/22/16, 6:07 AM, "Jungtaek Lim" wrote:
>Hi devs,
>
>AFAIK, we had been strugg
+1 (binding)
Deployed 1.0.2 and ran sample topologies.
Thanks,
Arun
On 8/3/16, 5:57 AM, "Jungtaek Lim" wrote:
>Reminder: vote was open for a week and has 1 binding and 2 non-binding.
>
>Please participate testing the 1.0.2 RC4 and vote to make releasing happen.
>
>Thanks,
>Jungtaek Lim (Heart
+1 (binding)
On 9/9/16, 7:20 AM, "Jungtaek Lim" wrote:
>+1 (binding)
>
>Thanks,
>Jungtaek Lim (HeartSaVioR)
>
>On Friday, September 9, 2016, S G wrote:
>
>> +1
>>
>> On Thu, Sep 8, 2016 at 1:50 PM, P. Taylor Goetz > > wrote:
>>
>> > Following an earlier discussion thread, I’d like to start of
+1
On 10/19/16, 8:58 PM, "P. Taylor Goetz" wrote:
>If there are no objections, I’d like to create the feature branch and push
>what I have so far. I’ve not had too much time lately to work on it, but
>other’s have expressed interest in contributing so I’d like to make it
>available.
>
>-Taylo
The streams API implementation has limited usage of 1.8 features and can be
easily ported to 1.7 if required. The examples are written in 1.8, the thought
being users would stick to the Java 8 style usage (lambdas) from the beginning.
If there is consensus we could also consider moving the 1.x b
>> 2017년 1월 3일 (화) 오후 12:26, S G 님이 작성:
>>
>> > I have found several bad usages of Java 8 lambdas and many developers are
>> > not comfortable using them.
>> >
>> > So we should use them only if it really makes the code beautiful and
>> easier
>&
Grouping makes sense only when you have more than one task for a bolt. If your
bolt has more than one task, then the grouping will decide how the tuples from
the spout are distributed to the individual tasks of the bolt. (shuffe =
random, fields = keyed on some field and so on).
See http
Can you please raise a pull request with your proposal? That way it will be
easier to review and comment.
Thanks,
Arun
On 2/15/17, 9:04 AM, "Sachin Pasalkar" wrote:
>Can any one take a look at this? I have attached my code in JIRA.
>
>On 14/02/17, 7:38 AM, "Sachin Pasalkar"
>wrote:
>
>>I hav
>If we really need long time to discuss above, I'm even OK to revert DRPC
>port and start 2.0.0 with webservices unported, (DRPC, UI, Logviewer) and
>address them at 2.1 or other minor versions.
>
>Any other opinions?
>
Yes, it may be better to move to 2.0 sooner and migrate the pending components
Verified the artifacts. Compiled examples and ran some sample topologies. Looks
good.
BTW, why are the external modules excluded from the binaries (the .zip and
.tar.gz). Isn’t it better if the binary distribution includes them? Maybe it
was already discussed but I am missing it. The sql direct
bute the same copy of them multiple
>> times.
>> > I agree with Alexandre. We should document this change better, because
>> it is confusing for people to get a release that used to have these in it,
>> but does not any more.
>> >
>> >
>> >
+1 to release with the porting completed. I think its mainly the UI server and
log viewer that’s pending.
We can start doing the regression and performance tests for whatever is already
ported.
If anyone is running the master branch in their pre-prod / prod environments,
it will be good to kn
Hi Kamal,
If you are interested to work on the streaming API, there are a few pending
tasks here (https://issues.apache.org/jira/browse/STORM-1843) that you could
pick up. CoGroupByKey and union might be simpler ones to start with. If you are
planning to add support for beam runner, you could a
+1 for Google Java Style Guide (with 4 spaces indentation instead of 2 and line
wrap set to 120 instead of 100)
Thanks,
Arun
On 5/2/17, 12:32 AM, "Bobby Evans" wrote:
>Just a reminder to everyone that voting ends on Wednesday.
>
>
>- Bobby
>
>On Friday, April 28, 2017, 1:33:37 PM CDT, Kishorku
+1 for addressing the pending reviews and getting 1.2.0 out soon.
On 10/10/17, 6:14 AM, "Jungtaek Lim" wrote:
>Stig,
>
>Let's just handle all the issues pending Storm 1.1.2. For pending issues on
>Storm 1.2.0, I already handled all the things.
>
>For STORM-2607, could you just take over and c
l the discussion go through either JIRA or dev
>email list.
>
>On Oct 10, 2017, at 12:48 PM, Stig Rohde Døssing
>mailto:stigdoess...@gmail.com>> wrote:
>
>Thanks Jungtaek, that sounds like a good plan. Here's the new PR for 2607
>https://github.com/apache/storm/pul
As you already noted, tick tuples provides only seconds granularity so that was
one of the reasons for having separate threads for triggering processing time
windows. Also the tick tuples are published to the receive queue of the
executor, so if there are messages in front of it, the delivery of
Hi,
Looks like we are only waiting on
https://issues.apache.org/jira/browse/STORM-2546 .
Are there any other issues which are blockers for Storm 1.2.0? Would be great
to see the 1.2.0 release out soon as it has a lot of critical fixes.
Thanks,
Arun
+1, I don’t see much use for standalone mode other than for testing.
Assume we can use the storm-sql in local mode to run topologies locally without
deploying to cluster ?
Thanks,
Arun
On 12/4/17, 10:53 PM, "Jungtaek Lim" wrote:
>Hi devs,
>
>We have been exposing "standalone mode" of St
Looks like now we are only waiting on below Kafka spout issues :
https://github.com/apache/storm/pull/2428
https://github.com/apache/storm/pull/2438
Maybe we should include the metrics changes as well?
https://github.com/apache/storm/pull/2203
Can we try to get the above merged ASAP and start
>STORM-2869: KafkaSpout discards all pending record when adjusting the
>consumer position after a commit [1]
Hope we could get it merged this week or early next week.
>>New Feature
>STORM-2153: New Metrics Reporting API [2]
I think this is waiting for a final +1 from revans2.
>STORM-2867: Add
860, and STORM-2860 doesn't seem
>to bring benefit on 1.x version line hence unless I'm missing here, we just
>need to make sure STORM-2153 is resolved so that we could start release
>phase for Storm 1.2.0.
>
>- Jungtaek Lim (HeartSaVioR)
>
>2017년 12월 29일 (금) 오전 4:51,
If possible, would like to include this minor patch to address storm-druid
issues when its used with storm-autocreds -
https://issues.apache.org/jira/browse/STORM-2907
Thanks,
Arun
On 1/23/18, 1:04 PM, "Alexandre Vermeerbergen" wrote:
>Hello,
>
>Just to let you know that I ran some basic
Looks weird, at-least the storm-starter exclamation and word count topologies
shows Assigned Mem: 2496 MB and capacity numbers in the range of “0.005 -
0.015” on a 16 GB macbook.
Thanks,
Arun
On 1/23/18, 3:09 PM, "Alexandre Vermeerbergen" wrote:
>Hello,
>
>I'm afraid I my vote in 1.2.0 RC1
to drag
>this more.
>There may be small time frame if RC1 is cancelled for some reason. Let's
>have short discussion to decide which things to include then. I also have
>some non-blocker issues to merge for 1.x-branch, but will hold merging
>while RC1 is open.
>
>-Jun
+1 (binding)
- Downloaded and deployed the tar.gz and .zip binary distribution.
- Verified MD5.
- Built the source with JDK 1.8
- Ran a few sample topologies and observed the output.
- Viewed the worker logs via log viewer and did some basic sanity on the
metrics.
Thanks,
Arun
On 1/23/18, 10
If the storm-kafka-client is fairly stable with the changes we made in the 1.2
release, then would we just want to continue the current process ?
If we want to decouple, I think option 2 may be better than option 1 to start
with.
When you say storm-kafka-client-vX.X.X, is it going to be comple
Are we waiting for https://github.com/apache/storm/pull/2538 to start the next
RC ?
This patch seem to contain more changes than just fixing a logging issue. Can
we only address the concern raised about logs filling with WARN messages and
address the rest in the next release or does the logs in
ehave differently for at-least-once and
>> at-most-once/no-guarantee.
>>
>> The patch makes changes to ensure that we store metadata in all cases.
>>
>> 2018-01-31 19:47 GMT+01:00 Arun Mahadevan :
>>
>> > Are we waiting for https://github.com/apache/
+1 to maintain 3 version lines.
I think the next focus should be 2.0.0 than 1.3.0.
On 2/12/18, 11:40 PM, "Jungtaek Lim" wrote:
>Hi devs,
>
>I've noticed that we are providing 4 different version lines (1.1.x, 1.0.x,
>0.10.x, 0.9.x) in download page, and I expect we will add one more for
>1.2
+1 (binding)
- Downloaded .zip/.tar.gz and verified md5.
- Verified the oncrpc jar is not included in the distribution
- Ran a few sample topologies, checked log viewer.
- Built the source code from .zip file
Thanks,
Arun
On 2/16/18, 3:27 PM, "Satish Duggana" wrote:
>+1 (binding)
>
>On S
Hi Jungtaek,
1. Right now users need to vary the database/table name in the state provider
config per topology. Agree, its better to include topology in the namespace.
2. IMO, users should have the flexibility to store multiple key-values in the
state in the core API. As of now storm only supp
hing we should support sooner than later, I'm not
>100% sure about which thing to do first. We're supporting at-least-once
>stateful processing in 1.x version line and haven't provided "state
>reshard" feature for a long time which makes actual users directly su
+1 to get it out soon.
On 7/10/18, 11:52 AM, "P. Taylor Goetz" wrote:
>+1 Sounds good to me.
>
>-Taylor
>
>> On Jul 10, 2018, at 2:18 AM, Jungtaek Lim wrote:
>>
>> Hi devs,
>>
>> I hopefully have a time to sort out issues regarding Storm 2.0.0 and link
>> to epic issue.
>>
>> https://issu
ig to take up remaining issues.
> > Thanks
> > > > to
> > > > >> his efforts, according to the epic, we have only one major issue
> > left:
> > > > >> porting UI to Java [1], and pull request [2] is available for
> that.
> > > &
+1
- Downloaded the binaries and validated signatures.
- Deployed the binaries, ran some sample topologies and checked the UI.
- Ran top level build using the source zip.
Thanks,
Arun
On Tue, 8 Jan 2019 at 11:03, P. Taylor Goetz wrote:
> This is a call to vote on releasing Apache Storm 2.0.0
Congratulations Govind, keep up the good work.
- Arun
On Wed, 9 Jan 2019 at 11:13, Kishorkumar Patil
wrote:
> Congratulations Govind!
>
> -Kishor
>
>
> On Wed, Jan 9, 2019 at 1:00 PM Stig Rohde Døssing
> wrote:
>
> > Congratulations.
> >
> > Den ons. 9. jan. 2019 kl. 19.55 skrev Roshan Naik
>
rote:
> > >
> > >> +1
> > >>
> > >> Built it and ran all of the tests. Everything passed.
> > >>
> > >> -Xin
> > >>
> > >> Kishorkumar Patil 于2019年1月9日周三 上午5:08写道：
> > >>
> > >>>
Nice suggestions Roshan and Taylor.
I think we can start with a release announcement (maybe with pointers to
the docs) and follow it up with blog posts that deep dives into the
different features and improvements.
A few from my side for the release announcement would be,
- Streams API - A typed
Agree with continuing with the RC if this is not a blocker.
On Tue, 29 Jan 2019 at 12:29, Roshan Naik
wrote:
> Correct me if I am wrong, this seems to be a bug with a workaround but
> not an exploitable security hole. ? if this is not a security hole, and the
> workaround is realistic then we s
+1
- Downloaded binaries
- Brought up a local cluster
- Ran a few topologies and checked the output and logs.
If I just click on the "Owner" link from the UI, it displays a red banner
with a warning.
"This user's topologies are in danger of being unscheduled due to the
owner's over-use of cluster
Arun Mahadevan created STORM-1207:
-
Summary: Add flux support for handling windowed bolts
Key: STORM-1207
URL: https://issues.apache.org/jira/browse/STORM-1207
Project: Apache Storm
Issue
[
https://issues.apache.org/jira/browse/STORM-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15010316#comment-15010316
]
Arun Mahadevan commented on STORM-1187:
---
Thanks for the inputs. Yes, the plan t
[
https://issues.apache.org/jira/browse/STORM-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15011489#comment-15011489
]
Arun Mahadevan commented on STORM-1187:
---
At a high level this is captured u
[
https://issues.apache.org/jira/browse/STORM-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15012801#comment-15012801
]
Arun Mahadevan commented on STORM-1187:
---
The plan is to add support to core f
Arun Mahadevan created STORM-1219:
-
Summary: Fix HDFS and Hive bolt flush/acking
Key: STORM-1219
URL: https://issues.apache.org/jira/browse/STORM-1219
Project: Apache Storm
Issue Type: Bug
[
https://issues.apache.org/jira/browse/STORM-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun Mahadevan resolved STORM-1389.
---
Resolution: Fixed
> unnecessary generatiion of projection tuples again
[
https://issues.apache.org/jira/browse/STORM-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun Mahadevan updated STORM-1389:
--
Fix Version/s: 0.11.0
> unnecessary generatiion of projection tuples again
[
https://issues.apache.org/jira/browse/STORM-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun Mahadevan updated STORM-1389:
--
Affects Version/s: 0.11.0
> unnecessary generatiion of projection tuples again
Arun Mahadevan created STORM-1416:
-
Summary: Add documentation for windowing state store functionality
Key: STORM-1416
URL: https://issues.apache.org/jira/browse/STORM-1416
Project: Apache Storm
[
https://issues.apache.org/jira/browse/STORM-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun Mahadevan resolved STORM-1411.
---
Resolution: Fixed
> some fixes for storm-window
[
https://issues.apache.org/jira/browse/STORM-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun Mahadevan updated STORM-1411:
--
Fix Version/s: 0.11.0
> some fixes for storm-window
[
https://issues.apache.org/jira/browse/STORM-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15092198#comment-15092198
]
Arun Mahadevan commented on STORM-676:
--
[~satish.duggana] do you have any res
[
https://issues.apache.org/jira/browse/STORM-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15106600#comment-15106600
]
Arun Mahadevan commented on STORM-1478:
---
Thanks [~vesense] merged to ma
[
https://issues.apache.org/jira/browse/STORM-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun Mahadevan resolved STORM-1478.
---
Resolution: Fixed
Fix Version/s: 2.0.0
> make bolt's getComponentConfiguratio
Arun Mahadevan created STORM-1486:
-
Summary: Fix Storm-kafka documentation to reflect changes from
STORM-1220
Key: STORM-1486
URL: https://issues.apache.org/jira/browse/STORM-1486
Project: Apache
Arun Mahadevan created STORM-1505:
-
Summary: Add map and flatMap operations in trident api
Key: STORM-1505
URL: https://issues.apache.org/jira/browse/STORM-1505
Project: Apache Storm
Issue
[
https://issues.apache.org/jira/browse/STORM-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun Mahadevan updated STORM-1505:
--
Summary: Add map, flatMap and filter operations in trident api (was: Add
map and flatMap
Arun Mahadevan created STORM-1513:
-
Summary: Update trident api docs
Key: STORM-1513
URL: https://issues.apache.org/jira/browse/STORM-1513
Project: Apache Storm
Issue Type: Sub-task
Arun Mahadevan created STORM-1517:
-
Summary: Add peek api in trident stream
Key: STORM-1517
URL: https://issues.apache.org/jira/browse/STORM-1517
Project: Apache Storm
Issue Type: Bug
Arun Mahadevan created STORM-1527:
-
Summary: Trident api doc for peek
Key: STORM-1527
URL: https://issues.apache.org/jira/browse/STORM-1527
Project: Apache Storm
Issue Type: Bug
Arun Mahadevan created STORM-1532:
-
Summary: Fix readCommandLineOpts to parse JSON correctly
Key: STORM-1532
URL: https://issues.apache.org/jira/browse/STORM-1532
Project: Apache Storm
Issue
[
https://issues.apache.org/jira/browse/STORM-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15138858#comment-15138858
]
Arun Mahadevan commented on STORM-1532:
---
-c drpc.servers=[\"host1\"
[
https://issues.apache.org/jira/browse/STORM-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15138898#comment-15138898
]
Arun Mahadevan commented on STORM-1532:
---
Actually this seems to be an issue
[
https://issues.apache.org/jira/browse/STORM-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15140427#comment-15140427
]
Arun Mahadevan commented on STORM-1476:
---
Thanks [~satish.duggana] merged to ma
[
https://issues.apache.org/jira/browse/STORM-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun Mahadevan resolved STORM-1476.
---
Resolution: Fixed
Fix Version/s: 2.0.0
> Filter -c options from args and add them
Arun Mahadevan created STORM-1550:
-
Summary: Fix storm.cmd to pass url-encoded options
Key: STORM-1550
URL: https://issues.apache.org/jira/browse/STORM-1550
Project: Apache Storm
Issue Type
Arun Mahadevan created STORM-1552:
-
Summary: Fix topology event sampling log directory
Key: STORM-1552
URL: https://issues.apache.org/jira/browse/STORM-1552
Project: Apache Storm
Issue Type
[
https://issues.apache.org/jira/browse/STORM-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148380#comment-15148380
]
Arun Mahadevan commented on STORM-1540:
---
Actually this issue happens only when
[
https://issues.apache.org/jira/browse/STORM-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun Mahadevan resolved STORM-1558.
---
Resolution: Fixed
Thanks [~Cody] merged to master.
> Utils in java breaks component page
[
https://issues.apache.org/jira/browse/STORM-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun Mahadevan resolved STORM-1566.
---
Resolution: Fixed
Fix Version/s: 2.0.0
Thanks [~satish.duggana] merged to master
Arun Mahadevan created STORM-1570:
-
Summary: Support nested field lookup and user defined functions in
Storm sql
Key: STORM-1570
URL: https://issues.apache.org/jira/browse/STORM-1570
Project: Apache
Arun Mahadevan created STORM-1576:
-
Summary: TopologyBuilder fails with ConcurrentModification in
addCheckPointInputs for stateful topologies
Key: STORM-1576
URL: https://issues.apache.org/jira/browse/STORM-1576
[
https://issues.apache.org/jira/browse/STORM-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun Mahadevan updated STORM-1576:
--
Affects Version/s: 2.0.0
1.0.0
> TopologyBuilder fails w
[
https://issues.apache.org/jira/browse/STORM-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun Mahadevan updated STORM-1570:
--
Summary: Support nested field lookup in Storm sql (was: Support nested
field lookup and user
Arun Mahadevan created STORM-1584:
-
Summary: Support UDF in storm-sql
Key: STORM-1584
URL: https://issues.apache.org/jira/browse/STORM-1584
Project: Apache Storm
Issue Type: Improvement
Arun Mahadevan created STORM-1585:
-
Summary: Add DDL support for UDFs in Storm-sql
Key: STORM-1585
URL: https://issues.apache.org/jira/browse/STORM-1585
Project: Apache Storm
Issue Type: Sub
[
https://issues.apache.org/jira/browse/STORM-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun Mahadevan reassigned STORM-1586:
-
Assignee: Arun Mahadevan
> ExprCompiler support for UDFs in Storm-
Arun Mahadevan created STORM-1586:
-
Summary: ExprCompiler support for UDFs in Storm-sql
Key: STORM-1586
URL: https://issues.apache.org/jira/browse/STORM-1586
Project: Apache Storm
Issue Type
Arun Mahadevan created STORM-1608:
-
Summary: Fix stateful bolt acking behavior
Key: STORM-1608
URL: https://issues.apache.org/jira/browse/STORM-1608
Project: Apache Storm
Issue Type: Bug
[
https://issues.apache.org/jira/browse/STORM-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun Mahadevan updated STORM-1608:
--
Summary: Fix stateful topology acking behavior (was: Fix stateful bolt
acking behavior)
>
Arun Mahadevan created STORM-1615:
-
Summary: Update state checkpointing doc with bolt's acking contract
Key: STORM-1615
URL: https://issues.apache.org/jira/browse/STORM-1615
Project: Apache
Arun Mahadevan created STORM-1662:
-
Summary: Reduce map lookups in send_to_eventlogger
Key: STORM-1662
URL: https://issues.apache.org/jira/browse/STORM-1662
Project: Apache Storm
Issue Type
[
https://issues.apache.org/jira/browse/STORM-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229845#comment-15229845
]
Arun Mahadevan commented on STORM-1692:
---
HBaseSecurityUtil
[
https://issues.apache.org/jira/browse/STORM-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun Mahadevan updated STORM-1692:
--
Summary: HBaseSecurityUtil#login modifies the current UGI causing issues if
two instances are
Arun Mahadevan created STORM-1709:
-
Summary: Add group by support in storm-sql standalone mode
Key: STORM-1709
URL: https://issues.apache.org/jira/browse/STORM-1709
Project: Apache Storm
Arun Mahadevan created STORM-1711:
-
Summary: Kerberos principals gets mixed up while using storm-hive
Key: STORM-1711
URL: https://issues.apache.org/jira/browse/STORM-1711
Project: Apache Storm
Arun Mahadevan created STORM-1714:
-
Summary: StatefulBolts ends up as normal bolts while using
TopologyBuilder.setBolt without parallelism
Key: STORM-1714
URL: https://issues.apache.org/jira/browse/STORM-1714
[
https://issues.apache.org/jira/browse/STORM-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15268155#comment-15268155
]
Arun Mahadevan commented on STORM-1757:
---
Would like to collaborate in this ef
[
https://issues.apache.org/jira/browse/STORM-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15282475#comment-15282475
]
Arun Mahadevan commented on STORM-1757:
---
Unified storm stream api is ideal
Arun Mahadevan created STORM-1833:
-
Summary: Add simple equi-join support in storm-sql standalone mode
Key: STORM-1833
URL: https://issues.apache.org/jira/browse/STORM-1833
Project: Apache Storm
[
https://issues.apache.org/jira/browse/STORM-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15284266#comment-15284266
]
Arun Mahadevan commented on STORM-1757:
---
Multiple active windows
[
https://issues.apache.org/jira/browse/STORM-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15284767#comment-15284767
]
Arun Mahadevan commented on STORM-1757:
---
[~revans2] distributed checkpoin
1 - 100 of 141 matches
Mail list logo
