Re: [DISCUSS] Receiving branch(es) for storm-jms

For me master and 1.x would be good places to land, given that we are planning to release 1.1.0 soon. - Jungtaek Lim (HeartSaVioR) On Wed, 5 Oct 2016 at 2:34 AM Bobby Evans <ev...@yahoo-inc.com.invalid> wrote: > +1 on those. Not sure if 1.0.x is the best place as it is a ne

Re: Error while building locally

mmit but untracked files present (use "git add" to > track) > > - > > git diff doesn't show anything either. > > > > > On Thu, Sep 29, 2016 at 2:15 P

FYI: backported excluding logs to rat plugin

It's fixed to master branch but not other branches. I backported this to 1.x and 1.0.x branch and pushed. cherry-picked commit is 9165b603985c0c158821cd5a20e6c509ee63342a <https://github.com/apache/storm/pull/1161/commits/9165b603985c0c158821cd5a20e6c509ee63342a> Thanks, Jungta

Re: [DISCUSS] Release Storm 1.1.0

1.1.0. Thanks, Jungtaek Lim 2016년 9월 30일 (금) 오후 11:09, Bobby Evans <ev...@yahoo-inc.com.invalid>님이 작성: > Sounds good to me. It would be nice to get some of the new features out. > Do we expect to maintain both 1.0.x and 1.1.x lines with bug fixes? And if > so for how long do we want to

[DISCUSS] Release Storm 1.1.0

to review and test), and release 1.1.0 soon. What do you think? I'm also open to volunteer release manager for 1.1.0 after we document the process of official release. Thanks, Jungtaek Lim (HeartSaVioR)

Re: [DISCUSS] Plan for merge SQE and Storm SQL

The change on storm-redis seems to require breaking backward compatibility, so I would love to see another pull request to integrate it via general review process. If it can be integrated to SQE without changing storm-redis, that would be nice. Does it make sense? - Jungtaek Lim (HeartSaVioR

Re: Error while building locally

Hi Sonu, if you clone the code, could you check git status and / or git diff to see the change if any? I'm not an Windows user, but showing version as 2.0.0 is strange and I haven't heard similar issues. - Jungtaek Lim

Re: [DISCUSS] Plan for merge SQE and Storm SQL

as passed and we are now able to import the > SQE > > >> code. > > >>> > > >>> The question now is to where do we want to import the code? > > >>> > > >>> My inclination is to import it to “external” in the 1.x branch. It > can &

Re: Strange behavior on MAP and ARRAY type

Sorry wrong recipients. It should be sent to Calcite dev. mailing list. 2016년 9월 24일 (토) 오후 3:51, Jungtaek Lim <kabh...@gmail.com>님이 작성: > Hi devs, > > I'm experimenting with ARRAY and MAP type with Calcite's JaninoRexCompiler. > (with Calcite 1.9.0) > > While testing I

Strange behavior on MAP and ARRAY type

cess the array with out of index. I don't know there's a standard rule on this, but at least PostgreSQL doesn't throw an Exception but just treats it as null. https://www.postgresql.org/docs/9.1/static/arrays.html (This means the result of ITEM operator is nullable.) Any ideas on these behaviors

[DISCUSS] Plan for merge SQE and Storm SQL

, or other things about the merging. Thanks, Jungtaek Lim (HeartSaVioR)

Re: [DISCUSS] ElasticSearch 2.x support

e with Bobby, +1 for supporting both versions till EOL and findout > how > >> many users are really using 1.7.x. > >> > >> ~Satish. > >> > >> > >> On Mon, Sep 19, 2016 at 7:50 PM, Bobby Evans > <ev...@yahoo-inc.com.invalid> > >&g

Re: Sharing sketched idea: Alternative way of upload topology REST API

could use to communicate with kafka. The SSL CA > stuff is just off the top of my head and I honestly don't know how feasible > that really would be, or have users include those certs in with their > topology. > If we want to start down the delegation token route I would be fine with

Sharing sketched idea: Alternative way of upload topology REST API

security issue on upload topology REST API? Thanks in advance, Jungtaek Lim (HeartSaVioR)

Re: [DISCUSS] ElasticSearch 2.x support

, Jungtaek Lim (HeartSaVioR) 2016년 9월 16일 (금) 오후 10:03, Aaron Niskodé-Dossett <doss...@gmail.com>님이 작성: > ES1 is close to end of life in terms of commercial support from Elastic, > but not quite there (https://www.elastic.co/support/eol). Unfortunately > the ES1 and ES2 clients won

Re: JIRI Notifications Moved to iss...@storm.apache.org

will need to watch the > Storm github repo and select a notification option. > > -Taylor > > > On Sep 12, 2016, at 5:20 PM, Jungtaek Lim <kabh...@gmail.com> wrote: > > > > Nice work. > > > > Will Github notification (posted to dev@) be also moved to issues@?

Re: JIRI Notifications Moved to iss...@storm.apache.org

Nice work. Will Github notification (posted to dev@) be also moved to issues@? Or will keep posted to dev@? On 2016년 9월 13일 (화) at 오전 6:00 P. Taylor Goetz wrote: > Infra has now moved JIRA notifications from dev@storm.apache.org to > issues.storm.apache.org. > > If you would

[jira] [Created] (STORM-2089) Replace Consumer of ISqlTridentDataSource with StateFactory and StateUpdater

Jungtaek Lim created STORM-2089: --- Summary: Replace Consumer of ISqlTridentDataSource with StateFactory and StateUpdater Key: STORM-2089 URL: https://issues.apache.org/jira/browse/STORM-2089 Project

[jira] [Commented] (STORM-2075) Storm SQL Phase III

[ https://issues.apache.org/jira/browse/STORM-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484071#comment-15484071 ] Jungtaek Lim commented on STORM-2075: - Below is Trident support for external modules. || module

[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

[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

[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=15482777#comment-15482777 ] Jungtaek Lim commented on STORM-1444: - No opinion received for this. I'll just add 'explain mode

[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

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 <ev...@yahoo-inc.com.invalid>님이 작성: > +1 - Bobby > > On Thursday, September 8, 2016 3:53 PM, P. Taylor Goetz < > ptg

Re: [VOTE] Accept storm-jms Code Donation

+1 (binding) Thanks, Jungtaek Lim (HeartSaVioR) On Friday, September 9, 2016, S G <sg.online.em...@gmail.com> wrote: > +1 > > On Thu, Sep 8, 2016 at 1:50 PM, P. Taylor Goetz <ptgo...@gmail.com > <javascript:;>> wrote: > > > Following an earlier discu

Re: [DISCUSS] Accept JW Player SQE Code Donation

+1 (binding) Thanks, Jungtaek Lim (HeartSaVioR) On Friday, September 9, 2016, P. Taylor Goetz <ptgo...@gmail.com> wrote: > Following an earlier discussion thread, I’d like to start of VOTE on > whether to accept the SQE donation from JW Player. > > The codebase being donated

[jira] [Resolved] (STORM-2079) Unneccessary readStormConfig operation

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

[jira] [Updated] (STORM-2074) NPE bug in storm-kafka-monitor

[ https://issues.apache.org/jira/browse/STORM-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-2074: Component/s: storm-kafka-monitor > NPE bug in storm-kafka-moni

[jira] [Resolved] (STORM-2074) NPE bug in storm-kafka-monitor

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

[jira] [Resolved] (STORM-2081) create external directory for storm-sql various data sources and move storm-sql-kafka to it

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

[jira] [Updated] (STORM-2081) create external directory for storm-sql various data sources and move storm-sql-kafka to it

[ https://issues.apache.org/jira/browse/STORM-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-2081: Component/s: storm-sql > create external directory for storm-sql various data sources and m

[jira] [Resolved] (STORM-2059) storm-submit-tools is getting rat failures.

[ https://issues.apache.org/jira/browse/STORM-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim resolved STORM-2059. - Resolution: Fixed Fix Version/s: 1.1.0 Fixed via STORM-2054 > storm-submit-to

[jira] [Resolved] (STORM-2054) DependencyResolver should be aware of relative path and absolute path

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

Re: [DISCUSS] Accept JW Player SQE Code Donation

s to Storm SQL. If making SQE to support SQL is easier, I'm also positive to go ahead that direction. (Btw, my vision for Storm SQL is moving to core - tuple based - with windowing, not relying on Trident. It might be after that Storm introduces higher-level API for Beam or another purposes.) - Ju

Re: [DISCUSS] storm-jms Code Donation

are more than a year). If we adopt this to Apache Storm someone should handle these and further works. - Jungtaek Lim (HeartSaVioR) 2016년 9월 3일 (토) 오전 8:36, S G <sg.online.em...@gmail.com>님이 작성: > I would love to see it part of storm/external and can volunteer to provide > any help if req

Re: Storm SQL Phase 3 created

Yeah that would be nice. Thanks for the suggestion Xin. - Jungtaek Lim (HeartSaVioR) 2016년 9월 2일 (금) 오후 6:47, Xin Wang <data.xinw...@gmail.com>님이 작성: > how about move storm-sql-kafka to a new directory like storm-sql-external > which contains various storm-sql data sources? > >

Storm SQL Phase 3 created

ny questions or suggestions. Thanks, Jungtaek Lim (HeartSaVioR)

[jira] [Resolved] (STORM-1344) storm-jdbc build error "object name already exists: USER_DETAILS in statement"

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

[jira] [Resolved] (STORM-1459) Allow not specifying producer properties in read-only Kafka table in StormSQL

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

[jira] [Closed] (STORM-2080) storm-submit-tools license check failure

[ https://issues.apache.org/jira/browse/STORM-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim closed STORM-2080. --- Resolution: Duplicate > storm-submit-tools license check fail

[jira] [Updated] (STORM-2075) Storm SQL Phase III

[ https://issues.apache.org/jira/browse/STORM-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-2075: Description: This epic tracks the effort of the phase III development of StormSQL. For now Storm

Re: please help: maven complie error

if problem still persists. Thanks, Jungtaek Lim (HeartSaVioR) 2016년 9월 2일 (금) 오전 12:14, 양석우 <ysw...@gmail.com>님이 작성: > 1. git clone https://github.com/apache/storm.git storm-master > 2. in storm-master -> mvn clean install -DskipTests=true -e > this command rise errors like

[jira] [Closed] (STORM-2046) Errors when using TOPOLOGY_TESTING_ALWAYS_TRY_SERIALIZE in local mode.

[ https://issues.apache.org/jira/browse/STORM-2046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim closed STORM-2046. --- Resolution: Duplicate Duplicated via STORM-2040 > Errors when us

[jira] [Resolved] (STORM-2070) Sigar native binary download link went 404

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

[jira] [Updated] (STORM-2075) Storm SQL Phase III

[ https://issues.apache.org/jira/browse/STORM-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-2075: Description: This epic tracks the effort of the phase III development of StormSQL. For now Storm

[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=15454308#comment-15454308 ] Jungtaek Lim commented on STORM-1444: - It might need to have different approach. Storm SQL

[jira] [Created] (STORM-2075) Storm SQL Phase III

Jungtaek Lim created STORM-2075: --- Summary: Storm SQL Phase III Key: STORM-2075 URL: https://issues.apache.org/jira/browse/STORM-2075 Project: Apache Storm Issue Type: Epic Components

[jira] [Resolved] (STORM-2056) Bugs in logviewer

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

[jira] [Resolved] (STORM-1646) Intermittent test failures in storm-kafka unit tests

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

[jira] [Resolved] (STORM-2039) Backpressure refactoring in worker and executor

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

[jira] [Updated] (STORM-2042) Nimbus client connections not closed properly causing connection leaks

[ https://issues.apache.org/jira/browse/STORM-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-2042: Fix Version/s: 0.10.3 > Nimbus client connections not closed properly causing connection le

Re: Question regarding design of the Trident (operations)

FYI: Just worked to have one - http://issues.apache.org/jira/browse/STORM-2072 This adds map and flatMap to have additional parameter: outputFields. If outputFields are specified, it replaces origin fields with output fields. - Jungtaek Lim (HeartSaVioR) 2016년 8월 31일 (수) 오전 10:27, Jungtaek Lim

[jira] [Resolved] (STORM-2064) Add storm name and function, access result and function to log-thrift-access

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

[jira] [Resolved] (STORM-2063) Add thread name in worker logs

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

[jira] [Closed] (STORM-1703) In local mode, process is not shutting down clearly

[ https://issues.apache.org/jira/browse/STORM-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim closed STORM-1703. --- Resolution: Duplicate > In local mode, process is not shutting down clea

[jira] [Created] (STORM-2073) Reduce multi-steps on visitProject into one

Jungtaek Lim created STORM-2073: --- Summary: Reduce multi-steps on visitProject into one Key: STORM-2073 URL: https://issues.apache.org/jira/browse/STORM-2073 Project: Apache Storm Issue Type

[jira] [Commented] (STORM-2071) nimbus-test test-leadership failing with Exception

[ https://issues.apache.org/jira/browse/STORM-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15451044#comment-15451044 ] Jungtaek Lim commented on STORM-2071: - Just found that building master branch (2.0.0) also fails

[jira] [Updated] (STORM-2071) nimbus-test test-leadership failing with Exception

[ https://issues.apache.org/jira/browse/STORM-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-2071: Affects Version/s: 2.0.0 > nimbus-test test-leadership failing with Except

[jira] [Commented] (STORM-2072) Add map, flatMap with different outputs (T->V) in Trident

[ https://issues.apache.org/jira/browse/STORM-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15451030#comment-15451030 ] Jungtaek Lim commented on STORM-2072: - And I have use case of MapFunction which needs

[jira] [Created] (STORM-2072) Add map, flatMap with different outputs (T->V) in Trident

Jungtaek Lim created STORM-2072: --- Summary: Add map, flatMap with different outputs (T->V) in Trident Key: STORM-2072 URL: https://issues.apache.org/jira/browse/STORM-2072 Project: Apache St

Re: Question regarding design of the Trident (operations)

to be a just missing feature. Thanks, Jungtaek Lim (HeartSaVioR) 2016년 8월 31일 (수) 오전 7:29, Jungtaek Lim <kabh...@gmail.com>님이 작성: > Hi Manu, > > I'm finding for 1:1 tuple transition, not aggregation. In other words, I'm > finding like 'V map(T, Function<T, V>)' which see

[jira] [Commented] (STORM-2071) nimbus-test test-leadership failing with Exception

[ https://issues.apache.org/jira/browse/STORM-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450483#comment-15450483 ] Jungtaek Lim commented on STORM-2071: - Does this occur from 1.0.1, or 1.0.x-branch (I mean 1.0.2

[jira] [Created] (STORM-2070) Sigar native binary download link went 404

Jungtaek Lim created STORM-2070: --- Summary: Sigar native binary download link went 404 Key: STORM-2070 URL: https://issues.apache.org/jira/browse/STORM-2070 Project: Apache Storm Issue Type

Re: Question regarding design of the Trident (operations)

Hi Manu, I'm finding for 1:1 tuple transition, not aggregation. In other words, I'm finding like 'V map(T, Function<T, V>)' which seems fit for many use case but Trident doesn't support this yet so I'd like to find out why. Thanks, Jungtaek Lim (HeartSaVioR) 2016년 8월 31일 (수) 오전 7:09, Manu

Re: [DISCUSS] Accept JW Player SQE Code Donation

atures, the difficult part for Storm SQL is SQL optimizations. There seems lots of SQL optimizations (like filter pushdown) but I'm not expert on that and it apparently needs more deep understanding of Calcite. Other parts also need contributors but we strongly need contributors in this area. Thank

[jira] [Resolved] (STORM-1881) storm-redis is missing dependant libraries in distribution

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

[jira] [Commented] (STORM-2068) org.apache.storm.utils.NimbusLeaderNotFoundException

[ https://issues.apache.org/jira/browse/STORM-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15448439#comment-15448439 ] Jungtaek Lim commented on STORM-2068: - Please post this question to user@ mailing list so that one

[jira] [Closed] (STORM-2068) org.apache.storm.utils.NimbusLeaderNotFoundException

[ https://issues.apache.org/jira/browse/STORM-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim closed STORM-2068. --- Resolution: Won't Fix > org.apache.storm.utils.NimbusLeaderNotFoundExcept

Question regarding design of the Trident (operations)

' and 'flatMap' use same output fields, so no luck. Is this a missing feature, or there's a reason for doing so? Trident uses TridentTupleView so I guess this is related but I didn't have a deep look for Trident itself. If anyone knows about the history please let me know. Thanks, Jungtaek Lim

[jira] [Updated] (STORM-2067) "array element type mismatch" from compute-executors in nimbus.clj

[ https://issues.apache.org/jira/browse/STORM-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-2067: Affects Version/s: 2.0.0 > "array element type mismatch" from compute-executors

[jira] [Commented] (STORM-2067) "array element type mismatch" from compute-executors in nimbus.clj

[ https://issues.apache.org/jira/browse/STORM-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447500#comment-15447500 ] Jungtaek Lim commented on STORM-2067: - This is due to Clojure's optimization. Clojure has two implicit

[jira] [Created] (STORM-2067) "array element type mismatch" from compute-executors in nimbus.clj

Jungtaek Lim created STORM-2067: --- Summary: "array element type mismatch" from compute-executors in nimbus.clj Key: STORM-2067 URL: https://issues.apache.org/jira/browse/STORM-2067 Project: Ap

Re: Package name changes for 3rd party storm dependencies

Hi, Could you enumerate which projects don't catch up the change of Apache Storm 1.0.0+? I think we need to get in touch and let them follow up (or we could help) recent change. Thanks, Jungtaek Lim (HeartSaVioR) 2016년 8월 26일 (금) 오후 5:36, Abhishek Agarwal <abhishc...@gmail.com>님이 작성: >

Re: Storm nimbus election

We need to see Nimbus log to find out why Nimbus is down. Pasting or attaching Nimbus log would be better. And please explain your Storm version too. Jungtaek Lim (HeartSaVioR) 2016년 8월 26일 (금) 오후 1:16, pradeep s <sreekumar.prad...@gmail.com>님이 작성: > Hi , > While restarting nimbus

[jira] [Commented] (STORM-2059) storm-submit-tools is getting rat failures.

[ https://issues.apache.org/jira/browse/STORM-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15439173#comment-15439173 ] Jungtaek Lim commented on STORM-2059: - STORM-2054 is for resolving this. Could you review pull request

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

, would we want to include STORM-2042 to 0.10.2? I agree this is definitely not a blocker, but we have been releasing 0.10.x line slowly so might be worth to consider. As I voted +1 I'm also OK to not include it. Thanks, Jungtaek Lim (HeartSaVioR) 2016년 8월 25일 (목) 오전 5:22, P. Taylor Goetz <p

Re: [VOTE] Release Apache Storm 0.9.7 (RC1)

WordCountTopology (multilang, remote) : OK Thanks, Jungtaek Lim (HeartSaVioR) 2016년 8월 25일 (목) 오전 5:39, P. Taylor Goetz <ptgo...@gmail.com>님이 작성: > Here’s my +1 (binding). > > I’d appreciate if other PMC members vote on this release (for or against > doesn’t matter, as long as you

[jira] [Created] (STORM-2057) Support JOIN statement in Storm SQL

Jungtaek Lim created STORM-2057: --- Summary: Support JOIN statement in Storm SQL Key: STORM-2057 URL: https://issues.apache.org/jira/browse/STORM-2057 Project: Apache Storm Issue Type: New

Re: [DISCUSS] Accept JW Player SQE Code Donation

th experts, or more contributors to share the load and learn together. Authors of SQE could be. - Jungtaek Lim (HeartSaVioR) 2016년 8월 25일 (목) 오후 10:30, Bobby Evans <ev...@yahoo-inc.com.invalid>님이 작성: > I agree that committership should not come form a code donation, but on > the othe

[jira] [Commented] (STORM-1446) Compile the Calcite logical plan to Storm physical plan

[ https://issues.apache.org/jira/browse/STORM-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15436979#comment-15436979 ] Jungtaek Lim commented on STORM-1446: - Just posted a question to Calcite dev@ list to hear explanation

[jira] [Resolved] (STORM-2050) [storm-sql] Support User Defined Aggregate Function for Trident mode

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

Re: [DISCUSS] Accept JW Player SQE Code Donation

other commiters/PMCs, similar to John Fang. Regarding future of storm-sql after SQE, it would be better to discuss again when the process of code donation is in place, so that we can discuss with comparison between storm-sql and SQE at that time. Thanks, Jungtaek Lim (HeartSaVIoR) 2016년 8월 25일 (목

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

[ https://issues.apache.org/jira/browse/STORM-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15436500#comment-15436500 ] Jungtaek Lim edited comment on STORM-1444 at 8/25/16 8:39 AM: -- Since we

[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=15436500#comment-15436500 ] Jungtaek Lim commented on STORM-1444: - Since we construct TridentTopology to submit to Nimbus, for now

[jira] [Commented] (STORM-1433) StormSQL Phase II

[ https://issues.apache.org/jira/browse/STORM-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15436252#comment-15436252 ] Jungtaek Lim commented on STORM-1433: - Added you to contributor list. You can assign yourself to issue

[jira] [Commented] (STORM-1433) StormSQL Phase II

[ https://issues.apache.org/jira/browse/STORM-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15436173#comment-15436173 ] Jungtaek Lim commented on STORM-1433: - If you're seeing older codebase you can see that Storm SQL

[jira] [Commented] (STORM-1433) StormSQL Phase II

[ https://issues.apache.org/jira/browse/STORM-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15435879#comment-15435879 ] Jungtaek Lim commented on STORM-1433: - [~mauzhang] Manu, are you still interested to contribute storm

[jira] [Resolved] (STORM-1434) Support the GROUP BY clause in StormSQL

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

Re: [DISCUSS] Accept JW Player SQE Code Donation

ves the IP clearance so should be easy to do). I'd be more appreciated if this is a signal for them to contribute Storm SQL directly. Thanks, Jungtaek Lim (HeartSaVioR) 2016년 8월 25일 (목) 오전 12:17, P. Taylor Goetz <ptgo...@gmail.com>님이 작성: > JW Player has offered to donate SQE (Streaming Query E

[jira] [Created] (STORM-2054) DependencyResolver should be aware of relative path and absolute path

Jungtaek Lim created STORM-2054: --- Summary: DependencyResolver should be aware of relative path and absolute path Key: STORM-2054 URL: https://issues.apache.org/jira/browse/STORM-2054 Project: Apache

[jira] [Commented] (STORM-1870) Allow FluxShellBolt/Spout set custom "componentConfig" via yaml.

[ https://issues.apache.org/jira/browse/STORM-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15434124#comment-15434124 ] Jungtaek Lim commented on STORM-1870: - [~darkless] Sorry it seems a bit late to visit. I found

[jira] [Assigned] (STORM-1870) Allow FluxShellBolt/Spout set custom "componentConfig" via yaml.

[ https://issues.apache.org/jira/browse/STORM-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim reassigned STORM-1870: --- Assignee: Jungtaek Lim > Allow FluxShellBolt/Spout set custom "componentConfig&q

[jira] [Created] (STORM-2053) Support connection between existing Trident Stream and Storm SQL (Input / Output)

Jungtaek Lim created STORM-2053: --- Summary: Support connection between existing Trident Stream and Storm SQL (Input / Output) Key: STORM-2053 URL: https://issues.apache.org/jira/browse/STORM-2053

[jira] [Resolved] (STORM-1435) Build a single jar with dependency for StormSQL dependency

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

[jira] [Resolved] (STORM-1993) Update storm-sql README to have actual dependencies

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

[jira] [Resolved] (STORM-2016) Topology submission improvement: support adding local jars and maven artifacts on submission

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

[jira] [Resolved] (STORM-2047) In secure setup the log page can't be viewed

[ https://issues.apache.org/jira/browse/STORM-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim resolved STORM-2047. - Resolution: Fixed Published. Marking as fixed. > In secure setup the log page can't be vie

[jira] [Commented] (STORM-2047) In secure setup the log page can't be viewed

[ https://issues.apache.org/jira/browse/STORM-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15431884#comment-15431884 ] Jungtaek Lim commented on STORM-2047: - Thanks [~arunmahadevan], I merged the change to master, 1.x

[jira] [Updated] (STORM-2047) In secure setup the log page can't be viewed

[ https://issues.apache.org/jira/browse/STORM-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-2047: Fix Version/s: 1.0.3 1.1.0 2.0.0 > In secure setup the

<    1   2   3   4   5   6   7   8   9   10   >