[
https://issues.apache.org/jira/browse/STORM-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15269303#comment-15269303
]
Robert Hastings commented on STORM-1674:
Sure, in progress.
> Idle KafkaSpout consumes more
+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
Github user hustfxj commented on the pull request:
https://github.com/apache/storm/pull/1370#issuecomment-216446889
LGTM
---
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
[
https://issues.apache.org/jira/browse/STORM-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268169#comment-15268169
]
ASF GitHub Bot commented on STORM-1707:
---
Github user hustfxj commented on the pull request:
[
https://issues.apache.org/jira/browse/STORM-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268166#comment-15268166
]
Jungtaek Lim commented on STORM-1757:
-
I also would like to participate in.
Before that, how about
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1324#issuecomment-216452966
@unsleepy22 Addressed "dropping older metrics points when consumer can't
catch up" to STORM-1698, and rebase this pull request.
---
If your project is set up for
[
https://issues.apache.org/jira/browse/STORM-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268226#comment-15268226
]
ASF GitHub Bot commented on STORM-1700:
---
Github user HeartSaVioR commented on the pull request:
+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
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1387#issuecomment-216460320
Hi, @srdo
Since I didn't see any OOMEs, I'm curious that it is based on assumption or
you could provide scenario to reproduce.
---
If your project is set up
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1384#issuecomment-216463598
+1
@srdo Nice finding. Could you address this to 1.x-branch and 0.10.x-branch,
too? Thanks in advance!
---
If your project is set up for it, you can reply to
[
https://issues.apache.org/jira/browse/STORM-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268344#comment-15268344
]
ASF GitHub Bot commented on STORM-1745:
---
Github user HeartSaVioR commented on the pull request:
[
https://issues.apache.org/jira/browse/STORM-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268392#comment-15268392
]
ASF GitHub Bot commented on STORM-1735:
---
Github user HeartSaVioR commented on the pull request:
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1369#issuecomment-216472728
+1 Nice finding.
@srdo I could cherry-pick into 1.x-branch since changeset is really small
but then merging should wait to release 1.0.1. Could you craft pull
[
https://issues.apache.org/jira/browse/STORM-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268434#comment-15268434
]
ASF GitHub Bot commented on STORM-1661:
---
Github user HeartSaVioR commented on the pull request:
[
https://issues.apache.org/jira/browse/STORM-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268437#comment-15268437
]
Jungtaek Lim commented on STORM-1661:
-
FYI : PR for 1.x-branch is
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1388#issuecomment-216483766
@lujinhong No you need to create your branch based on 1.x-branch in order
to craft pull request against 1.x-branch.
---
If your project is set up for it, you can
Github user srdo commented on the pull request:
https://github.com/apache/storm/pull/1387#issuecomment-216488648
@HeartSaVioR I saw OOME on one of my branches, because each
KafkaServerStartable allocates a 130MB byte array for the log cleaner thread. A
heap dump showed that there
[
https://issues.apache.org/jira/browse/STORM-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268475#comment-15268475
]
ASF GitHub Bot commented on STORM-1756:
---
Github user srdo closed the pull request at:
Github user srdo closed the pull request at:
https://github.com/apache/storm/pull/1387
---
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
[
https://issues.apache.org/jira/browse/STORM-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268330#comment-15268330
]
ASF GitHub Bot commented on STORM-1750:
---
Github user HeartSaVioR commented on the pull request:
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1353#issuecomment-216473523
+1
@Parth-Brahmbhatt Would you have a plan to submit your patch for the
improvement?
---
If your project is set up for it, you can reply to this email and have
[
https://issues.apache.org/jira/browse/STORM-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268307#comment-15268307
]
ASF GitHub Bot commented on STORM-1756:
---
Github user HeartSaVioR commented on the pull request:
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1376#issuecomment-216467060
I also don't encounter this through 1.0.1 RC1 to 1.0.1 RC3. Did you set the
custom Kafka version while building?
---
If your project is set up for it, you can
[
https://issues.apache.org/jira/browse/STORM-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268402#comment-15268402
]
ASF GitHub Bot commented on STORM-1715:
---
Github user HeartSaVioR commented on the pull request:
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1350#issuecomment-216474165
@darionyaphet Sorry it takes long to review.
+1
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
GitHub user lujinhong opened a pull request:
https://github.com/apache/storm/pull/1388
storm-1726: use Put#addColumn to replace the deprecated Put#add
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/lujinhong/storm storm-hbase
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1298#issuecomment-216480852
+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
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1349#issuecomment-216474859
+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
[
https://issues.apache.org/jira/browse/STORM-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268420#comment-15268420
]
ASF GitHub Bot commented on STORM-1646:
---
Github user HeartSaVioR commented on the pull request:
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1271#issuecomment-216481444
+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
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1290#issuecomment-216481526
+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
[
https://issues.apache.org/jira/browse/STORM-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268441#comment-15268441
]
ASF GitHub Bot commented on STORM-1672:
---
Github user HeartSaVioR commented on the pull request:
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1286#issuecomment-216482595
+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
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1386#issuecomment-216460875
+1
This and ES case indicate that we would be better to have some strategies
or policies to be compatible with non-compatible versions range of external
[
https://issues.apache.org/jira/browse/STORM-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268314#comment-15268314
]
ASF GitHub Bot commented on STORM-1755:
---
Github user HeartSaVioR commented on the pull request:
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1375#issuecomment-216467436
+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
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1353#issuecomment-216474300
@lujinhong Never mind. It would be better to cherry-pick since patch is
really tiny.
---
If your project is set up for it, you can reply to this email and have
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1335#issuecomment-216477509
`max.block.ms` is not available for 0.8.x so IMO it would be not good to
change storm-kafka module to strictly support 0.9 or higher. Users who use
Kafka 0.9 or
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1290#issuecomment-216482021
Sorry I didn't indicate the compile error from the CI. Revoking +1.
@redsanket Could you check the compile issue? doAclValidation should be
initialized when it's
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1271#issuecomment-216482139
Sorry I didn't indicate the compile error from the CI. Revoking +1.
@redsanket Could you check the compile issue? doAclValidation should be
initialized when it's
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1287#issuecomment-216483408
@moesol Sorry to participate too lately.
Could you craft the pull request based on master, 1.x-branch, and
0.10.x-branch? If you mind to craft several pull
[
https://issues.apache.org/jira/browse/STORM-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268443#comment-15268443
]
ASF GitHub Bot commented on STORM-1674:
---
Github user HeartSaVioR commented on the pull request:
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1382#issuecomment-216463802
+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
[
https://issues.apache.org/jira/browse/STORM-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268333#comment-15268333
]
ASF GitHub Bot commented on STORM-1725:
---
Github user HeartSaVioR commented on the pull request:
[
https://issues.apache.org/jira/browse/STORM-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268361#comment-15268361
]
ASF GitHub Bot commented on STORM-1736:
---
Github user HeartSaVioR commented on the pull request:
[
https://issues.apache.org/jira/browse/STORM-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268428#comment-15268428
]
ASF GitHub Bot commented on STORM-1676:
---
Github user HeartSaVioR commented on the pull request:
[
https://issues.apache.org/jira/browse/STORM-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268480#comment-15268480
]
ASF GitHub Bot commented on STORM-1745:
---
GitHub user srdo reopened a pull request:
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1385#issuecomment-216461066
+1 Thanks for addressing.
---
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
[
https://issues.apache.org/jira/browse/STORM-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268316#comment-15268316
]
ASF GitHub Bot commented on STORM-1754:
---
Github user HeartSaVioR commented on the pull request:
[
https://issues.apache.org/jira/browse/STORM-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268334#comment-15268334
]
ASF GitHub Bot commented on STORM-1750:
---
Github user srdo commented on the pull request:
Github user srdo commented on the pull request:
https://github.com/apache/storm/pull/1384#issuecomment-216464027
Hi @HeartSaVioR,
Sure, I'll make another pair of PRs soon.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1378#issuecomment-216465801
+1
Could you craft pull requests for 1.x-branch and 0.10.x-branch, too?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1370#issuecomment-216472136
+1 Nice.
@ppoulosk Could you craft pull requests against 1.x-branch, too?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1353#issuecomment-216473947
@lujinhong Would you also craft pull request for 1.x-branch? I can also
cherry-pick so please submit if you really don't mind.
---
If your project is set up for
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1327#issuecomment-216479478
@kristopherkane Yes, squash and push with `force` option.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
[
https://issues.apache.org/jira/browse/STORM-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268422#comment-15268422
]
ASF GitHub Bot commented on STORM-1701:
---
Github user HeartSaVioR commented on the pull request:
[
https://issues.apache.org/jira/browse/STORM-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268439#comment-15268439
]
ASF GitHub Bot commented on STORM-1661:
---
Github user HeartSaVioR commented on the pull request:
Github user srdo closed the pull request at:
https://github.com/apache/storm/pull/1380
---
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 user srdo reopened a pull request:
https://github.com/apache/storm/pull/1380
STORM-1745: Add partition to log output in PartitionManager
Adding topic name and partition id to the log output makes it easier to
debug when an issue arises.
You can merge this pull request into
[
https://issues.apache.org/jira/browse/STORM-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268479#comment-15268479
]
ASF GitHub Bot commented on STORM-1745:
---
Github user srdo closed the pull request at:
[
https://issues.apache.org/jira/browse/STORM-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15269614#comment-15269614
]
ASF GitHub Bot commented on STORM-1674:
---
GitHub user moesol opened a pull request:
[
https://issues.apache.org/jira/browse/STORM-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15269498#comment-15269498
]
Hugo Louro commented on STORM-1757:
---
I also would like to work on this project.
> Apache Beam Runner
Github user moesol commented on the pull request:
https://github.com/apache/storm/pull/1391#issuecomment-21896
Without the MaxWait being set to 100, it is set to 1, which means that
the bolt will waiting for 10 seconds when no messages are available. On the 1.x
branch, I was
[
https://issues.apache.org/jira/browse/STORM-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15269608#comment-15269608
]
ASF GitHub Bot commented on STORM-1674:
---
Github user moesol commented on the pull request:
GitHub user harshach opened a pull request:
https://github.com/apache/storm/pull/1392
STORM-1760. HiveState should retire idle or old writes with flushAndClose
You can merge this pull request into a Git repository by running:
$ git pull
GitHub user moesol opened a pull request:
https://github.com/apache/storm/pull/1391
(STORM-1674) Idle KafkaSpout consumes more bandwidth than needed
* Allows minBytes in fetch request to be configured
from KafkaConfig.fetchMinBytes.
* Defaults new configuration
[
https://issues.apache.org/jira/browse/STORM-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15269570#comment-15269570
]
ASF GitHub Bot commented on STORM-1674:
---
GitHub user moesol opened a pull request:
[
https://issues.apache.org/jira/browse/STORM-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15269582#comment-15269582
]
ASF GitHub Bot commented on STORM-1674:
---
Github user harshach commented on the pull request:
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/1391#issuecomment-216663883
@moesol there is patch that merged into 1.0 release
https://github.com/apache/storm/pull/1309/files . Does that changes work for
you. Any reason for the MaxWait to be
Github user srdo commented on the pull request:
https://github.com/apache/storm/pull/1387#issuecomment-216490426
If this turns out to be a problem later, disabling the log cleaner thread
during tests is probably a better fix. The tests don't make logs long enough to
be compacted
GitHub user srdo opened a pull request:
https://github.com/apache/storm/pull/1390
STORM-1750 (0.10.x): Ensure worker dies when report-error-and-die is â¦
â¦called. Make cluster set-data try setting data if node creation fails
because the node exists.
Backport of
[
https://issues.apache.org/jira/browse/STORM-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stig Rohde Døssing resolved STORM-1756.
---
Resolution: Cannot Reproduce
Tried setting up some test classes with KafkaTestBroker
[
https://issues.apache.org/jira/browse/STORM-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268491#comment-15268491
]
ASF GitHub Bot commented on STORM-1756:
---
Github user srdo commented on the pull request:
[
https://issues.apache.org/jira/browse/STORM-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268574#comment-15268574
]
ASF GitHub Bot commented on STORM-1756:
---
Github user HeartSaVioR commented on the pull request:
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1387#issuecomment-216505586
Please reopen this issue if you saw intermittent test failure. What I asked
is that it's a theory or it occurred some issues.
---
If your project is set up for it,
Github user srdo commented on the pull request:
https://github.com/apache/storm/pull/1387#issuecomment-216508276
I did see OOME due to KafkaServer resources. 8x 130MB byte arrays caused
the VM to run out of memory. As I said, I can't reproduce it. It's probably not
an issue on master
GitHub user srdo reopened a pull request:
https://github.com/apache/storm/pull/1387
STORM-1756: Explicitly null KafkaServer reference in KafkaTestBroker â¦
â¦to prevent out of memory on large test classes.
I'm not clear on whether JUnit keeps the reference for the
[
https://issues.apache.org/jira/browse/STORM-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268514#comment-15268514
]
ASF GitHub Bot commented on STORM-1735:
---
Github user srdo commented on the pull request:
[
https://issues.apache.org/jira/browse/STORM-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268528#comment-15268528
]
ASF GitHub Bot commented on STORM-1745:
---
Github user srdo commented on the pull request:
Github user srdo commented on the pull request:
https://github.com/apache/storm/pull/1380#issuecomment-216496822
@HeartSaVioR Sure. The current logs look like this "Starting Kafka
10.4.5.1:0 from offset 15520", which doesn't tell you which topic it's
affecting. The logs in L259 and
GitHub user srdo opened a pull request:
https://github.com/apache/storm/pull/1389
STORM-1750: Ensure worker dies when report-error-and-die is called. Mâ¦
â¦ake zookeeper_state_factory set-data try setting data if node creation
fails because the node exists.
Backport of
[
https://issues.apache.org/jira/browse/STORM-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268593#comment-15268593
]
ASF GitHub Bot commented on STORM-1756:
---
GitHub user srdo reopened a pull request:
[
https://issues.apache.org/jira/browse/STORM-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268592#comment-15268592
]
ASF GitHub Bot commented on STORM-1756:
---
Github user srdo commented on the pull request:
Github user srdo commented on the pull request:
https://github.com/apache/storm/pull/1369#issuecomment-216493707
@HeartSaVioR Sure, please do :)
---
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
[
https://issues.apache.org/jira/browse/STORM-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268575#comment-15268575
]
ASF GitHub Bot commented on STORM-1750:
---
GitHub user srdo opened a pull request:
[
https://issues.apache.org/jira/browse/STORM-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268836#comment-15268836
]
Elisey Zanko commented on STORM-1758:
-
It works. Thanks!
> Distributed log search doesn't work in
Github user abhishekagarwal87 commented on the pull request:
https://github.com/apache/storm/pull/1386#issuecomment-216558668
Yes. Good thing is storm-kafka doesn't use any api only available in kafka
0.9.x and thus can still run with kafka 0.8.x by simply excluding dependency.
---
[
https://issues.apache.org/jira/browse/STORM-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268850#comment-15268850
]
ASF GitHub Bot commented on STORM-1755:
---
Github user abhishekagarwal87 commented on the pull
[
https://issues.apache.org/jira/browse/STORM-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268857#comment-15268857
]
ASF GitHub Bot commented on STORM-1700:
---
Github user unsleepy22 commented on a diff in the pull
[
https://issues.apache.org/jira/browse/STORM-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elisey Zanko updated STORM-1758:
Comment: was deleted
(was: It works. Thanks!)
> Distributed log search doesn't work in dockerized
[
https://issues.apache.org/jira/browse/STORM-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268834#comment-15268834
]
Elisey Zanko commented on STORM-1758:
-
It works. Thanks!
> Distributed log search doesn't work in
Github user abhishekagarwal87 commented on the pull request:
https://github.com/apache/storm/pull/1376#issuecomment-216560931
This would also break the compatibility of storm 1.0.0 with 0.8.x kafka
client API.
---
If your project is set up for it, you can reply to this email and
[
https://issues.apache.org/jira/browse/STORM-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268861#comment-15268861
]
ASF GitHub Bot commented on STORM-1736:
---
Github user abhishekagarwal87 commented on the pull
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1380#issuecomment-216465299
@srdo
Could you give an example of actual changes in logs?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
[
https://issues.apache.org/jira/browse/STORM-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268385#comment-15268385
]
ASF GitHub Bot commented on STORM-1707:
---
Github user HeartSaVioR commented on the pull request:
[
https://issues.apache.org/jira/browse/STORM-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268852#comment-15268852
]
Elisey Zanko commented on STORM-1758:
-
Actually it's only necessary to add this into the nimbus and
Github user unsleepy22 commented on a diff in the pull request:
https://github.com/apache/storm/pull/1324#discussion_r61898673
--- Diff:
storm-core/src/jvm/org/apache/storm/metric/filter/FilterByMetricName.java ---
@@ -0,0 +1,93 @@
+/**
+ * Licensed to the Apache Software
[
https://issues.apache.org/jira/browse/STORM-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elisey Zanko updated STORM-1758:
Comment: was deleted
(was: That would work.)
> Distributed log search doesn't work in dockerized
[
https://issues.apache.org/jira/browse/STORM-1761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15269948#comment-15269948
]
ASF GitHub Bot commented on STORM-1761:
---
Github user HeartSaVioR commented on the pull request:
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1394#issuecomment-216712023
+1 Nice finding.
Btw, I guess it's due to inconsistencies between sample / test topologies,
one argument for only specifying topology name, or two arguments
1 - 100 of 157 matches
Mail list logo