[jira] [Updated] (STORM-1925) Nimbus fails to start in secure mode

[ https://issues.apache.org/jira/browse/STORM-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-1925: Component/s: storm-core > Nimbus fails to start in secure m

[jira] [Updated] (STORM-1925) Nimbus fails to start in secure mode

[ https://issues.apache.org/jira/browse/STORM-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-1925: Affects Version/s: 1.1.0 2.0.0 > Nimbus fails to start in secure m

[jira] [Updated] (STORM-1766) A better algorithm server rack selection for RAS

[ https://issues.apache.org/jira/browse/STORM-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-1766: Fix Version/s: 2.0.0 > A better algorithm server rack selection for

[jira] [Resolved] (STORM-1911) Inconsistency of timestamp between IMetricsConsumer and IClusterMetricsConsumer

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

[jira] [Resolved] (STORM-1920) version of parent pom for storm-kafka-monitor is set 1.0.2-SNAPSHOT in master branch

[ https://issues.apache.org/jira/browse/STORM-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim resolved STORM-1920. - Resolution: Fixed Fix Version/s: 2.0.0 > version of parent pom for storm-kafka-moni

[jira] [Updated] (STORM-1920) version of parent pom for storm-kafka-monitor is set 1.0.2-SNAPSHOT in master branch

[ https://issues.apache.org/jira/browse/STORM-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-1920: Affects Version/s: 2.0.0 > version of parent pom for storm-kafka-monitor is set 1.0.2-SNAPS

[jira] [Updated] (STORM-1920) version of parent pom for storm-kafka-monitor is set 1.0.2-SNAPSHOT in master branch

[ https://issues.apache.org/jira/browse/STORM-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-1920: Description: Recent Travis CI builds for pull requests are all failed due to this. https://travis

[jira] [Created] (STORM-1920) version of parent pom for storm-kafka-monitor is set 1.0.2-SNAPSHOT in master branch

Jungtaek Lim created STORM-1920: --- Summary: version of parent pom for storm-kafka-monitor is set 1.0.2-SNAPSHOT in master branch Key: STORM-1920 URL: https://issues.apache.org/jira/browse/STORM-1920

[jira] [Created] (STORM-1919) Introduce FilterBolt on storm-redis

Jungtaek Lim created STORM-1919: --- Summary: Introduce FilterBolt on storm-redis Key: STORM-1919 URL: https://issues.apache.org/jira/browse/STORM-1919 Project: Apache Storm Issue Type: New

[jira] [Commented] (STORM-1719) Introduce REST API: Topology metric stats for stream

[ https://issues.apache.org/jira/browse/STORM-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15343219#comment-15343219 ] Jungtaek Lim commented on STORM-1719: - Merged to 1.x-branch but still need to work to apply master

[jira] [Updated] (STORM-1719) Introduce REST API: Topology metric stats for stream

[ https://issues.apache.org/jira/browse/STORM-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-1719: Fix Version/s: 1.1.0 > Introduce REST API: Topology metric stats for str

Re: Storm Redis TTL Control

control is not matched to the intention of these classes. And as we talked from initial pull request for storm-redis, 1 on 1 transition on Redis commands doesn't make sense, and we already provide Jedis instance so it would be easy to make own Bolt for flexibility. Thanks, Jungtaek Lim (HeartSaVioR

[jira] [Created] (STORM-1911) Inconsistency of timestamp between IMetricsConsumer and IClusterMetricsConsumer

Jungtaek Lim created STORM-1911: --- Summary: Inconsistency of timestamp between IMetricsConsumer and IClusterMetricsConsumer Key: STORM-1911 URL: https://issues.apache.org/jira/browse/STORM-1911 Project

[jira] [Updated] (STORM-1773) Utils.javaDeserialize() doesn't work with primitive types

[ https://issues.apache.org/jira/browse/STORM-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-1773: Fix Version/s: 1.1.0 > Utils.javaDeserialize() doesn't work with primitive ty

Friendly reminder: Release vote for 1.0.2 RC2 is now in progress

Please note that 1.0.2 resolves some critical issues which are reported by users. Thanks, Jungtaek Lim (HeartSaVioR)

[jira] [Updated] (STORM-1853) Deserialization issues in Utils.javaDeserialize()

[ https://issues.apache.org/jira/browse/STORM-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-1853: Fix Version/s: (was: 1.0.1) 1.0.2 > Deserialization iss

[jira] [Resolved] (STORM-1841) Address a few minor issues in windowing and doc

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

[jira] [Resolved] (STORM-1868) Modify TridentKafkaWordCount to run in distributed mode

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

[jira] [Resolved] (STORM-1723) Introduce ClusterMetricsConsumer

[ https://issues.apache.org/jira/browse/STORM-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim resolved STORM-1723. - Resolution: Fixed Merged to master and 1.x-branch. > Introduce ClusterMetricsConsu

[jira] [Resolved] (STORM-1699) Improve MetricsConsumer

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

[jira] [Resolved] (STORM-1700) Introduce 'whitelist' / 'blacklist' option to MetricsConsumer

[ https://issues.apache.org/jira/browse/STORM-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim resolved STORM-1700. - Resolution: Fixed Fix Version/s: 1.1.0 2.0.0 Merged into master and 1.x

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

clicking on 'show' button create a new visualization form, and non-first forms are created with empty content. - logviewer: navigation buttons on daemon log goes 404 since it doesn't add daemon option. Thanks, Jungtaek Lim (HeartSaVioR) 2016년 6월 11일 (토) 오전 4:26, P. Taylor Goetz <ptgo...@gmail.com>

[jira] [Updated] (STORM-1895) blobstore replication-factor argument

[ https://issues.apache.org/jira/browse/STORM-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-1895: Issue Type: Documentation (was: Bug) > blobstore replication-factor argum

[jira] [Updated] (STORM-1674) Idle KafkaSpout consumes more bandwidth than needed

[ https://issues.apache.org/jira/browse/STORM-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-1674: Assignee: Robert Hastings > Idle KafkaSpout consumes more bandwidth than nee

[jira] [Updated] (STORM-1859) Late tuples are not acked in windowed mode

[ https://issues.apache.org/jira/browse/STORM-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-1859: Assignee: Balazs Kossovics > Late tuples are not acked in windowed m

[jira] [Updated] (STORM-1874) Update Logger access permissions

[ https://issues.apache.org/jira/browse/STORM-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-1874: Assignee: darion yaphet > Update Logger access permissi

[jira] [Updated] (STORM-1887) Help message for the set_log_level command does not have the topology name parameter

[ https://issues.apache.org/jira/browse/STORM-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-1887: Assignee: Francisco Lopes > Help message for the set_log_level command does not have the topol

[jira] [Updated] (STORM-1882) Expose TextFileReader public

[ https://issues.apache.org/jira/browse/STORM-1882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-1882: Assignee: darion yaphet > Expose TextFileReader pub

[jira] [Updated] (STORM-1884) In RedisKeyValueState.prepareCommit keys in pendingPrepare should have priority over pendingCommit

[ https://issues.apache.org/jira/browse/STORM-1884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-1884: Assignee: Balazs Kossovics > In RedisKeyValueState.prepareCommit keys in pendingPrepare should h

[jira] [Updated] (STORM-1876) Provide option to build storm-kafka against different kafka clients

[ https://issues.apache.org/jira/browse/STORM-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-1876: Issue Type: Improvement (was: Documentation) > Provide option to build storm-kafka agai

[jira] [Resolved] (STORM-1705) Cap on number of retries for a failed message in kafka spout

[ https://issues.apache.org/jira/browse/STORM-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim resolved STORM-1705. - Resolution: Fixed Marking as 'resolved'. > Cap on number of retries for a failed mess

[jira] [Updated] (STORM-1873) Reemit late tuples in windowed mode

[ https://issues.apache.org/jira/browse/STORM-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-1873: Assignee: Balazs Kossovics > Reemit late tuples in windowed m

[jira] [Commented] (STORM-1724) Fill up lacking contents to Metrics documentation

[ https://issues.apache.org/jira/browse/STORM-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15321963#comment-15321963 ] Jungtaek Lim commented on STORM-1724: - Please hold on resolving / closing. I'm in progress of updating

Re: New Committers/PMC Members: John Fang and Abhishek Agarwal

Congraturations! Welcome both of you, and thanks for the great work. 2016년 6월 8일 (수) 오전 5:12, Bobby Evans 님이 작성: > Congratulations to both of you. Well deserved. > - Bobby > > On Tuesday, June 7, 2016 3:02 PM, P. Taylor Goetz > wrote: > > >

Re: [Discussion] Release Apache Storm 1.0.2

and improvements were introduced with bugfix versions. But starting with 0.10.0, I believe we're respecting semantic versioning implicitly, especially Apache Storm graduates 0.x which is occasionally treated as 'beta'. Thanks, Jungtaek Lim (HeartSaVioR) 2016년 6월 2일 (목) 오후 5:21, darion.yaphet <fly...@163.

[Discussion] Release Apache Storm 1.0.2

expect it will be resolved soon so we'll be prepared soon. What do you think? Thanks, Jungtaek Lim (HeartSaVioR)

[jira] [Deleted] (STORM-1877) jira-github-join.py doesn't work since Apache JIRA doesn't work with python default user agent

[ https://issues.apache.org/jira/browse/STORM-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim deleted STORM-1877: > jira-github-join.py doesn't work since Apache JIRA doesn't work with python > default user

[jira] [Created] (STORM-1877) jira-github-join.py doesn't work since Apache JIRA doesn't work with python default user agent

Jungtaek Lim created STORM-1877: --- Summary: jira-github-join.py doesn't work since Apache JIRA doesn't work with python default user agent Key: STORM-1877 URL: https://issues.apache.org/jira/browse/STORM-1877

[jira] [Updated] (STORM-1698) Asynchronous MetricsConsumerBolt

[ https://issues.apache.org/jira/browse/STORM-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-1698: Priority: Critical (was: Major) > Asynchronous MetricsConsumerB

[jira] [Commented] (STORM-1755) Revert the kafka client version upgrade in storm-kafka module

[ https://issues.apache.org/jira/browse/STORM-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15309937#comment-15309937 ] Jungtaek Lim commented on STORM-1755: - [~abhishek.agarwal] Thanks! Could you please file a new issue

[jira] [Resolved] (STORM-1755) Revert the kafka client version upgrade in storm-kafka module

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

[jira] [Comment Edited] (STORM-1832) Consistently slow metrics consumer triggers backpressure which will be never back to normal

[ https://issues.apache.org/jira/browse/STORM-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15309898#comment-15309898 ] Jungtaek Lim edited comment on STORM-1832 at 6/1/16 8:06 AM: - [~BaconSeason

[jira] [Commented] (STORM-1832) Consistently slow metrics consumer triggers backpressure which will be never back to normal

[ https://issues.apache.org/jira/browse/STORM-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15309898#comment-15309898 ] Jungtaek Lim commented on STORM-1832: - [~BaconSeason] Sorry for the delay. You can see the capacity

[jira] [Commented] (STORM-1875) Separate Jedis/JedisCluster Config

[ https://issues.apache.org/jira/browse/STORM-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15309866#comment-15309866 ] Jungtaek Lim commented on STORM-1875: - I'm aware of this, and I think it's not critical, but kind

[jira] [Updated] (STORM-1875) Separate Jedis/JedisCluster Config

[ https://issues.apache.org/jira/browse/STORM-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-1875: Priority: Major (was: Critical) > Separate Jedis/JedisCluster Con

[Notice] Website rebuilt and published

s from reflected site. Thanks, Jungtaek Lim (HeartSaVioR)

[jira] [Resolved] (STORM-1749) Fix storm-starter links in the github code

[ https://issues.apache.org/jira/browse/STORM-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim resolved STORM-1749. - Resolution: Fixed Reflect changeset to website and confirm that changeset is published. ex

[jira] [Commented] (STORM-1861) Storm submit command returns exit code of 0 even when it fails

[ https://issues.apache.org/jira/browse/STORM-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15309074#comment-15309074 ] Jungtaek Lim commented on STORM-1861: - This is only merged to 1.x-branch. Need to merge to master

[jira] [Updated] (STORM-1859) Late tuples are not acked in windowed mode

[ https://issues.apache.org/jira/browse/STORM-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-1859: I think it should be fixed and released in the next bugfix. > Late tuples are not acked in windo

Re: [DISCUSSION] opinions on breaking changes on metrics for 1.x

Inlined my thought, but totally agreed with Bobby. Starting with good questions seems more important than trying to measure more parts. Thanks for bring up your opinion. Thanks, Jungtaek Lim (HeartSaVioR) 2016년 5월 23일 (월) 오후 10:36, Bobby Evans <ev...@yahoo-inc.com>님이 작성: > From JSto

[jira] [Updated] (STORM-1742) More accurate 'complete latency'

[ https://issues.apache.org/jira/browse/STORM-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-1742: Description: I already initiated talking thread on dev@ list. Below is copy of the content in my

Re: Merging to Multiple Branches

merging process so we need to build our own if we want to keep it as is. - Jungtaek Lim (HeartSaVioR) On Monday, May 23, 2016, Bobby Evans <ev...@yahoo-inc.com.invalid> wrote: > I filed https://issues.apache.org/jira/browse/STORM-1490 for this, but > never found time to get to i

Re: [DISCUSSION] opinions on breaking changes on metrics for 1.x

plementation of Spout can provide, but it's just my 2 cent. Thanks, Jungtaek Lim (HeartSaVioR) 2016년 5월 23일 (월) 오후 6:33, Abhishek Agarwal <abhishc...@gmail.com>님이 작성: > So I am assuming that there is a general consensus on adding new api for > metrics and gradually phasing out the old on

[jira] [Commented] (STORM-1842) Forward references in storm.thrift cause tooling issues

[ https://issues.apache.org/jira/browse/STORM-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15295895#comment-15295895 ] Jungtaek Lim commented on STORM-1842: - Merged. Thanks [~ptgoetz] for reviewing and merging! > Forw

[jira] [Commented] (STORM-1842) Forward references in storm.thrift cause tooling issues

[ https://issues.apache.org/jira/browse/STORM-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15295890#comment-15295890 ] Jungtaek Lim commented on STORM-1842: - [~ptgoetz] Seems like you missed to merge this to master. (pull

Re: [DISCUSSION] opinions on breaking changes on metrics for 1.x

metrics on Storm will be moved to new metrics feature. While some behavioral changes could be occurred (for example, IMetricsConsumer could be changed to no longer receive built-in metrics on Storm), it will not break backward compatibility from the API side anyway. Thanks, Jungtaek Lim (HeartSaVioR

Re: Regarding types of DataPoint value for Metrics Consumer

on worker level. There're some ideas in mind to help reducing the problem with keeping backward compatibility, but I also agree that we should take a new approach if we want to clear out all these problems. Seems like we need to initiate thread for discussion or vote. Thanks, Jungtaek Lim (HeartSaVioR

Re: Regarding types of DataPoint value for Metrics Consumer

or a thin wrapper around it based on the same > concepts. Or if there is a different API that someone here would prefer > that we use that is fine with me too. But lets not write it ourselves, > lets take from the experts who have spent a long time building something > that works. > - Bobby &g

[jira] [Comment Edited] (STORM-1846) Need a smoke test for the generated Python code

[ https://issues.apache.org/jira/browse/STORM-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15288181#comment-15288181 ] Jungtaek Lim edited comment on STORM-1846 at 5/18/16 5:37 AM: -- I thought it's

[jira] [Comment Edited] (STORM-1846) Need a smoke test for the generated Python code

[ https://issues.apache.org/jira/browse/STORM-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15288181#comment-15288181 ] Jungtaek Lim edited comment on STORM-1846 at 5/18/16 4:22 AM: -- I thought it's

[jira] [Commented] (STORM-1846) Need a smoke test for the generated Python code

[ https://issues.apache.org/jira/browse/STORM-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15288181#comment-15288181 ] Jungtaek Lim commented on STORM-1846: - I thought it's easy to handle since we just set the pythonpath

Regarding types of DataPoint value for Metrics Consumer

value for storing metrics to time-series DB via metrics consumer it would be great. It can be used to protocol between IMetric users and metrics consumer developers. What do you think? Thanks, Jungtaek Lim (HeartSaVioR) ps. I'm not heavy user of time-series DBs (I researched some, but they don't do

[jira] [Comment Edited] (STORM-1842) Forward references in storm.thrift cause tooling issues

[ https://issues.apache.org/jira/browse/STORM-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15286594#comment-15286594 ] Jungtaek Lim edited comment on STORM-1842 at 5/17/16 8:54 PM: -- [~barrywhart

[jira] [Commented] (STORM-1842) Forward references in storm.thrift cause tooling issues

[ https://issues.apache.org/jira/browse/STORM-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15286594#comment-15286594 ] Jungtaek Lim commented on STORM-1842: - [~barrywhart] Here's custom build of Storm 1.0.2 SNAPSHOT

[jira] [Commented] (STORM-1842) Forward references in storm.thrift cause tooling issues

[ https://issues.apache.org/jira/browse/STORM-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15286580#comment-15286580 ] Jungtaek Lim commented on STORM-1842: - Yeah, good to have a new JIRA issue, and if you would

[jira] [Commented] (STORM-1842) Forward references in storm.thrift cause tooling issues

[ https://issues.apache.org/jira/browse/STORM-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15286491#comment-15286491 ] Jungtaek Lim commented on STORM-1842: - [~barrywhart] [~CogumelosMaravilha] I submitted pull requests

[jira] [Assigned] (STORM-1842) Forward references in storm.thrift cause tooling issues

[ https://issues.apache.org/jira/browse/STORM-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim reassigned STORM-1842: --- Assignee: Jungtaek Lim > Forward references in storm.thrift cause tooling iss

[jira] [Resolved] (STORM-1745) Add partition to PartitionManager logs where it's missing

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

[jira] [Resolved] (STORM-1773) Utils.javaDeserialize() doesn't work with primitive types

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

[jira] [Resolved] (STORM-1709) Add group by support in storm-sql standalone mode

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

[jira] [Resolved] (STORM-1735) Nimbus logs that replication was not reached when min-replication-count was reached exactly

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

[jira] [Reopened] (STORM-1749) Fix storm-starter links in the github code

[ https://issues.apache.org/jira/browse/STORM-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim reopened STORM-1749: - I merged change to repo, but still not reflect this changes to website. I'll close this issue once I

[jira] [Resolved] (STORM-1835) add lock info in thread dump

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

[jira] [Resolved] (STORM-1749) Fix storm-starter links in the github code

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

[jira] [Resolved] (STORM-1764) Pacemaker is throwing some stack traces

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

[jira] [Resolved] (STORM-1761) Storm-Solr Example Throws ArrayIndexOutOfBoundsException in Remote Cluster Mode

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

[jira] [Updated] (STORM-1761) Storm-Solr Example Throws ArrayIndexOutOfBoundsException in Remote Cluster Mode

[ https://issues.apache.org/jira/browse/STORM-1761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-1761: Affects Version/s: (was: 0.10.2) 2.0.0 > Storm-Solr Example Thr

[jira] [Resolved] (STORM-1756) Storm-kafka tests leak resources due to retained references to KafkaServer

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

[jira] [Reopened] (STORM-1756) Storm-kafka tests leak resources due to retained references to KafkaServer

[ https://issues.apache.org/jira/browse/STORM-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim reopened STORM-1756: - Reopen since it's intermittent test failure. > Storm-kafka tests leak resources due to retai

[jira] [Resolved] (STORM-1754) Correct java version in 0.10.x storm-starter

[ https://issues.apache.org/jira/browse/STORM-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim resolved STORM-1754. - Resolution: Fixed Fix Version/s: 0.10.2 Thanks [~vesense], I merged into 0.10.x branch

[jira] [Resolved] (STORM-1750) Report-error-and-die may not kill the worker

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

[jira] [Resolved] (STORM-1715) Jedis Default Host

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

[jira] [Commented] (STORM-1713) Don't use proprietary NotImplementedException in storm-kafka

[ https://issues.apache.org/jira/browse/STORM-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15284237#comment-15284237 ] Jungtaek Lim commented on STORM-1713: - Btw, due to lockdown of ASF JIRA, anyone who are not registered

[jira] [Resolved] (STORM-1713) Don't use proprietary NotImplementedException in storm-kafka

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

[jira] [Resolved] (STORM-1678) abstract batch processing to common api `BatchHelper`

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

[jira] [Resolved] (STORM-1676) NullPointerException while serializing ClusterWorkerHearbeat

[ https://issues.apache.org/jira/browse/STORM-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim resolved STORM-1676. - Resolution: Fixed Thanks [~abhi1509], I merged into master. > NullPointerException wh

[jira] [Resolved] (STORM-1672) Stats not get class cast exception

[ https://issues.apache.org/jira/browse/STORM-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim resolved STORM-1672. - Resolution: Fixed Fix Version/s: 2.0.0 Thanks [~revans2], I merged into master. > St

[jira] [Resolved] (STORM-1720) Support GEO in storm-redis

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

[jira] [Resolved] (STORM-1661) Introduce a config to turn off blobstore acl validation in insecure mode

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

[jira] [Commented] (STORM-1767) metrics log entries are being appended to root log

[ https://issues.apache.org/jira/browse/STORM-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15284109#comment-15284109 ] Jungtaek Lim commented on STORM-1767: - I don't see this issue. metrics logs are properly logged

Re: does anyone else hate the verbose logging of all PR comments in the Storm JIRAs?

might go unnoticed for long time. Harsha -1 to what Abhishek said. notifications important for everyone else. if you are getting spammed by this create a mail rule. Aaron 3* Agree that limiting duplicate emails would be good. Thanks, Jungtaek Lim (HeartSaVioR) 2016년 5월 16일 (월) 오전 11:23

Re: does anyone else hate the verbose logging of all PR comments in the Storm JIRAs?

6:03 PM, 임정택 <kabh...@gmail.com> wrote: >> > >> >> Hi Erik, >> >> >> >> I think verbose logging of PR comments could be OK. I didn't >> experience any >> >> confusing. >> >> Maybe referring sample JIRA issues could help

Re: [DISCUSSION] More convenient way to maintain committer / contributor list and changelogs

:'%an' | sort -u (borrowed from OpenTSDB/AsyncBase) I even think mentioning contributors for each release news is more honorable compared to just listing up with README forever. There's also contributors tab in Github so we could even get rid of it. Thanks, Jungtaek Lim (HeartSaVioR) 2016년 1월 21일 (목

Re: [DISCUSSION] Squashing commits before merging in.

://storm.apache.org/contribute/Contributing-to-Storm.html. Aaron 1* I like the idea of squashing to a single commit and tagging that commit and PR with the JIRA ID. Thanks, Jungtaek Lim (HeartSaVioR) 2016년 5월 16일 (월) 오전 11:01, Jungtaek Lim <kabh...@gmail.com>님이 작성: > This thread was forgotten, but I w

Re: [DISCUSSION] Squashing commits before merging in.

t; > > > Btw, real pain point from cherry-picking is conflicts. > > Jedis uses same approach, and we have to believe collaborators and unit > > tests, and we did some mistakes while cherry-picking and unit tests > > couldn't catch it. > > It would be not resolved th

Re: Revisiting forgotten discussions regarding more convenience way to maintain project

thread, too. I'll move opinions which Abhishek and Aaron gave to origin threads, too. Thanks, Jungtaek Lim (HeartSaVioR) 2016년 5월 14일 (토) 오후 12:58, Harsha <st...@harsha.io>님이 작성: > Jungtaek, > If we didn't get any conclusion. Lets continue discussion on >

Revisiting forgotten discussions regarding more convenience way to maintain project

ne new comment from github, which is really bad for me. I strongly agree with Erik, and linking github PR with JIRA is enough for me. Sorry and thanks for reading really long mail. Please let me know if you think it would be better to discuss them separated (each mail thread) so that I can post them. Thanks, Jungtaek Lim (HeartSaVioR)

Re: STORM JIRA being spammed - CANNOT comment on JIRA (as a result of the counter spam measures)

.@hortonworks.com> wrote: > > > > > > Please add me to committer list. id: arunmahadevan > > > > > > > > > > > > > > > On 5/13/16, 9:19 AM, "Arun Iyer" <ai...@hortonworks.com> wrote: > > > > > >> R

[jira] [Created] (STORM-1832) Consistently slow metrics consumer triggers backpressure which will be never back to normal

Jungtaek Lim created STORM-1832: --- Summary: Consistently slow metrics consumer triggers backpressure which will be never back to normal Key: STORM-1832 URL: https://issues.apache.org/jira/browse/STORM-1832

Re: STORM JIRA being spammed - CANNOT comment on JIRA (as a result of the counter spam measures)

hurt. We should create version 1.0.2 and 1.1.0 to go forward. Thanks, Jungtaek Lim (HeartSaVioR) 2016년 5월 13일 (금) 오전 7:55, Harsha <st...@harsha.io>님이 작성: > Bobby, > Can you check if I am part of commiters list. I don't see admin > page for STORM project jira. >

<    3   4   5   6   7   8   9   10   11   12   >