[jira] [Closed] (STORM-2096) Error creating jar file with maven
[ https://issues.apache.org/jira/browse/STORM-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaitanya closed STORM-2096. Resolution: Not A Problem > Error creating jar file with maven > -- > > Key: STORM-2096 > URL: https://issues.apache.org/jira/browse/STORM-2096 > Project: Apache Storm > Issue Type: Bug > Components: examples >Affects Versions: 1.0.2 > Environment: Ubuntu Linux 16.04 >Reporter: Chaitanya > Labels: maven, newbie, test > Fix For: 1.0.2 > > > I tried to alter the Wordcount file inside storm in order to make it take a > file path externally in the command line. Then, I tried to make the jar file > for operation using maven. > First i ran mvn compile. The output is:- > [INFO] Scanning for projects... > [INFO] > > [INFO] > > [INFO] Building storm-starter 1.0.2 > [INFO] > > [INFO] > [INFO] --- maven-remote-resources-plugin:1.2.1:process (default) @ > storm-starter --- > [INFO] > [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ > storm-starter --- > [debug] execute contextualize > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 5 resources > [INFO] Copying 3 resources > [INFO] > [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ > storm-starter --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 52 source files to > /opt/storm/examples/storm-starter/target/classes > [INFO] > [INFO] --- clojure-maven-plugin:1.7.1:compile (compile) @ storm-starter --- > [INFO] > > [INFO] BUILD SUCCESS > [INFO] > > [INFO] Total time: 9.178 s > [INFO] Finished at: 2016-09-15T11:18:13+00:00 > [INFO] Final Memory: 52M/691M > [INFO] > > The i ran mvn test. The output is:- > [INFO] Scanning for projects... > [INFO] > > [INFO] > > [INFO] Building storm-starter 1.0.2 > [INFO] > > [INFO] > [INFO] --- maven-remote-resources-plugin:1.2.1:process (default) @ > storm-starter --- > [INFO] > [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ > storm-starter --- > [debug] execute contextualize > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 5 resources > [INFO] Copying 3 resources > [INFO] > [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ > storm-starter --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 52 source files to > /opt/storm/examples/storm-starter/target/classes > [INFO] > [INFO] --- clojure-maven-plugin:1.7.1:compile (compile) @ storm-starter --- > [INFO] > [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ > storm-starter --- > [debug] execute contextualize > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] skip non existing resourceDirectory > /opt/storm/examples/storm-starter/src/test/resources > [INFO] Copying 3 resources > [INFO] > [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ > storm-starter --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 8 source files to > /opt/storm/examples/storm-starter/target/test-classes > [INFO] - > [ERROR] COMPILATION ERROR : > [INFO] - > [ERROR] > /opt/storm/examples/storm-starter/test/jvm/org/apache/storm/starter/tools/RankingsTest.java:[34,24] > cannot find symbol > symbol: class Rankable > location: class org.apache.storm.starter.tools.RankingsTest > [ERROR] > /opt/storm/examples/storm-starter/test/jvm/org/apache/storm/starter/tools/RankingsTest.java:[35,24] > cannot find symbol > symbol: class Rankable > location: class org.apache.storm.starter.tools.RankingsTest > [ERROR] > /opt/storm/examples/storm-starter/test/jvm/org/apache/storm/starter/tools/RankingsTest.java:[36,24] > cannot find symbol > symbol: class Rankable > location: class org.apache.storm.starter.tools.RankingsTest > [ERROR] > /opt/storm/examples/storm-starter/test/jvm/org/apache/storm/starter/tools/RankingsTest.java:[37,24] > cannot find symbol > symbol: class Rankable > location: class org.apache.storm.starter.t
[jira] [Created] (STORM-2116) [Storm SQL] Support 'CASE' statement
Jungtaek Lim created STORM-2116: --- Summary: [Storm SQL] Support 'CASE' statement Key: STORM-2116 URL: https://issues.apache.org/jira/browse/STORM-2116 Project: Apache Storm Issue Type: Improvement Components: storm-sql Reporter: Jungtaek Lim As we don't support it yet. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (STORM-2115) [Storm SQL] 'IN' with subquery making implicit aggregate calls which is having 'null' as name
[
https://issues.apache.org/jira/browse/STORM-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim updated STORM-2115:
Summary: [Storm SQL] 'IN' with subquery making implicit aggregate calls
which is having 'null' as name (was: [Storm SQL] 'IN' with subquery making
implicit aggregate calls which is having no name)
> [Storm SQL] 'IN' with subquery making implicit aggregate calls which is
> having 'null' as name
> -
>
> Key: STORM-2115
> URL: https://issues.apache.org/jira/browse/STORM-2115
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-sql
>Reporter: Jungtaek Lim
>
> "SELECT ID FROM FOO WHERE ID NOT IN (SELECT 1 AS ID FROM FOO)" throws
> duplicated field 'null'.
> Here is logical plan from Calcite.
> {code}
> LogicalFilter(condition=[NOT(CASE(=($3, 0), false, IS NOT NULL($7), true, IS
> NULL($5), null, <($4, $3), null, false))]): rowcount = 1.0, cumulative cost =
> {10.375 rows, 16.0 cpu, 0.0 io}, id = 24
> LogicalJoin(condition=[=($5, $6)], joinType=[left]): rowcount = 1.0,
> cumulative cost = {9.375 rows, 15.0 cpu, 0.0 io}, id = 23
> LogicalProject($f0=[$0], $f1=[$1], $f2=[$2], $f3=[$3], $f4=[$4],
> $f5=[$0]): rowcount = 1.0, cumulative cost = {5.25 rows, 11.0 cpu, 0.0 io},
> id = 18
> LogicalJoin(condition=[true], joinType=[inner]): rowcount = 1.0,
> cumulative cost = {4.25 rows, 5.0 cpu, 0.0 io}, id = 17
> EnumerableTableScan(table=[[FOO]]): rowcount = 1.0, cumulative cost =
> {0.0 rows, 1.0 cpu, 0.0 io}, id = 12
> LogicalAggregate(group=[{}], agg#0=[COUNT()], agg#1=[COUNT($0)]):
> rowcount = 1.0, cumulative cost = {3.25 rows, 4.0 cpu, 0.0 io}, id = 16
> LogicalProject($f0=[$0], $f1=[true]): rowcount = 1.0, cumulative
> cost = {2.0 rows, 4.0 cpu, 0.0 io}, id = 15
> LogicalProject(ID=[1]): rowcount = 1.0, cumulative cost = {1.0
> rows, 2.0 cpu, 0.0 io}, id = 14
> EnumerableTableScan(table=[[FOO]]): rowcount = 1.0, cumulative
> cost = {0.0 rows, 1.0 cpu, 0.0 io}, id = 13
> LogicalAggregate(group=[{0}], agg#0=[MIN($1)]): rowcount = 1.0,
> cumulative cost = {3.125 rows, 4.0 cpu, 0.0 io}, id = 22
> LogicalProject($f0=[$0], $f1=[true]): rowcount = 1.0, cumulative cost =
> {2.0 rows, 4.0 cpu, 0.0 io}, id = 21
> LogicalProject(ID=[1]): rowcount = 1.0, cumulative cost = {1.0 rows,
> 2.0 cpu, 0.0 io}, id = 20
> EnumerableTableScan(table=[[FOO]]): rowcount = 1.0, cumulative cost
> = {0.0 rows, 1.0 cpu, 0.0 io}, id = 19
> {code}
> In this case AggregateCall.name could be null, so there could be duplicated
> fields in trident tuple which are having 'null' as name.
> We should refer the RowType of LogicalAggregate, but another issue is that
> its name could be same as upstream's output field name, so it makes another
> duplication.
> One way to resolve this is assigning temporal field names while aggregating,
> and finally replace them with fields name in RowType of LocalAggregate.
> We can achieve this easier when STORM-2072 will be merged.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (STORM-2115) [Storm SQL] 'IN' with subquery making implicit aggregate calls which is having no name
Jungtaek Lim created STORM-2115:
---
Summary: [Storm SQL] 'IN' with subquery making implicit aggregate
calls which is having no name
Key: STORM-2115
URL: https://issues.apache.org/jira/browse/STORM-2115
Project: Apache Storm
Issue Type: Bug
Components: storm-sql
Reporter: Jungtaek Lim
"SELECT ID FROM FOO WHERE ID NOT IN (SELECT 1 AS ID FROM FOO)" throws
duplicated field 'null'.
Here is logical plan from Calcite.
{code}
LogicalFilter(condition=[NOT(CASE(=($3, 0), false, IS NOT NULL($7), true, IS
NULL($5), null, <($4, $3), null, false))]): rowcount = 1.0, cumulative cost =
{10.375 rows, 16.0 cpu, 0.0 io}, id = 24
LogicalJoin(condition=[=($5, $6)], joinType=[left]): rowcount = 1.0,
cumulative cost = {9.375 rows, 15.0 cpu, 0.0 io}, id = 23
LogicalProject($f0=[$0], $f1=[$1], $f2=[$2], $f3=[$3], $f4=[$4], $f5=[$0]):
rowcount = 1.0, cumulative cost = {5.25 rows, 11.0 cpu, 0.0 io}, id = 18
LogicalJoin(condition=[true], joinType=[inner]): rowcount = 1.0,
cumulative cost = {4.25 rows, 5.0 cpu, 0.0 io}, id = 17
EnumerableTableScan(table=[[FOO]]): rowcount = 1.0, cumulative cost =
{0.0 rows, 1.0 cpu, 0.0 io}, id = 12
LogicalAggregate(group=[{}], agg#0=[COUNT()], agg#1=[COUNT($0)]):
rowcount = 1.0, cumulative cost = {3.25 rows, 4.0 cpu, 0.0 io}, id = 16
LogicalProject($f0=[$0], $f1=[true]): rowcount = 1.0, cumulative cost
= {2.0 rows, 4.0 cpu, 0.0 io}, id = 15
LogicalProject(ID=[1]): rowcount = 1.0, cumulative cost = {1.0
rows, 2.0 cpu, 0.0 io}, id = 14
EnumerableTableScan(table=[[FOO]]): rowcount = 1.0, cumulative
cost = {0.0 rows, 1.0 cpu, 0.0 io}, id = 13
LogicalAggregate(group=[{0}], agg#0=[MIN($1)]): rowcount = 1.0, cumulative
cost = {3.125 rows, 4.0 cpu, 0.0 io}, id = 22
LogicalProject($f0=[$0], $f1=[true]): rowcount = 1.0, cumulative cost =
{2.0 rows, 4.0 cpu, 0.0 io}, id = 21
LogicalProject(ID=[1]): rowcount = 1.0, cumulative cost = {1.0 rows,
2.0 cpu, 0.0 io}, id = 20
EnumerableTableScan(table=[[FOO]]): rowcount = 1.0, cumulative cost =
{0.0 rows, 1.0 cpu, 0.0 io}, id = 19
{code}
In this case AggregateCall.name could be null, so there could be duplicated
fields in trident tuple which are having 'null' as name.
We should refer the RowType of LogicalAggregate, but another issue is that its
name could be same as upstream's output field name, so it makes another
duplication.
One way to resolve this is assigning temporal field names while aggregating,
and finally replace them with fields name in RowType of LocalAggregate.
We can achieve this easier when STORM-2072 will be merged.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (STORM-2114) [Storm SQL] Support 'Date' and 'Timestamp' literal
[ https://issues.apache.org/jira/browse/STORM-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-2114: Summary: [Storm SQL] Support 'Date' and 'Timestamp' literal (was: Support 'Date' and 'Timestamp' literal) > [Storm SQL] Support 'Date' and 'Timestamp' literal > -- > > Key: STORM-2114 > URL: https://issues.apache.org/jira/browse/STORM-2114 > Project: Apache Storm > Issue Type: Improvement > Components: storm-sql >Reporter: Jungtaek Lim > > We don't support it yet so we can't use '2016-01-01' as date literal and also > '2016-01-01 00:00:00' as timestamp literal. > Adding it also would make testing functions with Date type easier. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (STORM-2114) Support 'Date' and 'Timestamp' literal
Jungtaek Lim created STORM-2114: --- Summary: Support 'Date' and 'Timestamp' literal Key: STORM-2114 URL: https://issues.apache.org/jira/browse/STORM-2114 Project: Apache Storm Issue Type: Improvement Components: storm-sql Reporter: Jungtaek Lim We don't support it yet so we can't use '2016-01-01' as date literal and also '2016-01-01 00:00:00' as timestamp literal. Adding it also would make testing functions with Date type easier. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (STORM-2113) [Storm SQL] 'OR' operator cannot handle more than 2 arguments
Jungtaek Lim created STORM-2113: --- Summary: [Storm SQL] 'OR' operator cannot handle more than 2 arguments Key: STORM-2113 URL: https://issues.apache.org/jira/browse/STORM-2113 Project: Apache Storm Issue Type: Bug Components: storm-sql Reporter: Jungtaek Lim When we use 'IN' statement, Calcite is converting this statement of 'OR' with multiple arguments. While testing I found current 'OR' implementation cannot handle more than 2 parameters, which effectively introduce a bug on 'IN' (and 'NOT IN'). It should be fixed to support 'IN' properly. Also need to consider applying 'short curcuit' on that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (STORM-2112) Catch up 'SQL Reference' page on Calcite to provide as many features as we can
[ https://issues.apache.org/jira/browse/STORM-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-2112: Epic Name: Storm SQL - cover the page 'SQL Reference' on Calcite (was: [Storm SQL] Cover the page 'SQL Reference' on Calcite) > Catch up 'SQL Reference' page on Calcite to provide as many features as we can > -- > > Key: STORM-2112 > URL: https://issues.apache.org/jira/browse/STORM-2112 > Project: Apache Storm > Issue Type: Epic > Components: storm-sql >Reporter: Jungtaek Lim > > https://calcite.apache.org/docs/reference.html > Above page represents Calcite availability to parse and handle SQL statements > and also types and built-in functions. We need to catch up this for providing > as many feature as we can based on Calcite. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (STORM-2112) Catch up 'SQL Reference' page on Calcite to provide as many features as we can
[ https://issues.apache.org/jira/browse/STORM-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-2112: Summary: Catch up 'SQL Reference' page on Calcite to provide as many features as we can (was: catch up 'SQL Reference' page on Calcite to provide as many features as we can) > Catch up 'SQL Reference' page on Calcite to provide as many features as we can > -- > > Key: STORM-2112 > URL: https://issues.apache.org/jira/browse/STORM-2112 > Project: Apache Storm > Issue Type: Epic > Components: storm-sql >Reporter: Jungtaek Lim > > https://calcite.apache.org/docs/reference.html > Above page represents Calcite availability to parse and handle SQL statements > and also types and built-in functions. We need to catch up this for providing > as many feature as we can based on Calcite. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (STORM-2112) catch up 'SQL Reference' page on Calcite to provide as many features as we can
Jungtaek Lim created STORM-2112: --- Summary: catch up 'SQL Reference' page on Calcite to provide as many features as we can Key: STORM-2112 URL: https://issues.apache.org/jira/browse/STORM-2112 Project: Apache Storm Issue Type: Epic Components: storm-sql Reporter: Jungtaek Lim https://calcite.apache.org/docs/reference.html Above page represents Calcite availability to parse and handle SQL statements and also types and built-in functions. We need to catch up this for providing as many feature as we can based on Calcite. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (STORM-2111) [Storm SQL] support 'LIKE' and 'SIMILAR TO'
[ https://issues.apache.org/jira/browse/STORM-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-2111: Issue Type: Improvement (was: Bug) > [Storm SQL] support 'LIKE' and 'SIMILAR TO' > --- > > Key: STORM-2111 > URL: https://issues.apache.org/jira/browse/STORM-2111 > Project: Apache Storm > Issue Type: Improvement > Components: storm-sql >Reporter: Jungtaek Lim > > Currently Storm SQL doesn't support 'LIKE' and 'SIMILAR TO' keywords. > Its implementation is existing on SqlFunctions so what we need to do is just > registering them to ImpTable and make some unit tests. > NOT LIKE and NOT SIMILAR TO is represented as NOT(LIKE) and NOT(SIMILAR TO) > so it should be automatically supported after. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (STORM-2111) [Storm SQL] support 'LIKE' and 'SIMILAR TO'
Jungtaek Lim created STORM-2111: --- Summary: [Storm SQL] support 'LIKE' and 'SIMILAR TO' Key: STORM-2111 URL: https://issues.apache.org/jira/browse/STORM-2111 Project: Apache Storm Issue Type: Bug Components: storm-sql Reporter: Jungtaek Lim Currently Storm SQL doesn't support 'LIKE' and 'SIMILAR TO' keywords. Its implementation is existing on SqlFunctions so what we need to do is just registering them to ImpTable and make some unit tests. NOT LIKE and NOT SIMILAR TO is represented as NOT(LIKE) and NOT(SIMILAR TO) so it should be automatically supported after. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (STORM-2100) Few tests are getting failed in external/sql module with JDK 7
[ https://issues.apache.org/jira/browse/STORM-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-2100: Fix Version/s: 1.1.0 2.0.0 > Few tests are getting failed in external/sql module with JDK 7 > --- > > Key: STORM-2100 > URL: https://issues.apache.org/jira/browse/STORM-2100 > Project: Apache Storm > Issue Type: Bug > Components: storm-sql >Affects Versions: 1.x >Reporter: Satish Duggana >Assignee: Jungtaek Lim > Fix For: 2.0.0, 1.1.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Tests run: 11, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 31.095 sec > <<< FAILURE! - in > org.apache.storm.sql.compiler.backends.trident.TestPlanCompiler > testCompileEquiJoinWithRightOuterJoin(org.apache.storm.sql.compiler.backends.trident.TestPlanCompiler) > Time elapsed: 2.434 sec <<< FAILURE! > org.junit.internal.ArrayComparisonFailure: arrays first differed at element > [0]; expected:<[2, null]> but was:<[3, null]> > at > org.junit.internal.ComparisonCriteria.arrayEquals(ComparisonCriteria.java:50) > at org.junit.Assert.internalArrayEquals(Assert.java:473) > at org.junit.Assert.assertArrayEquals(Assert.java:265) > at org.junit.Assert.assertArrayEquals(Assert.java:280) > at > org.apache.storm.sql.compiler.backends.trident.TestPlanCompiler.testCompileEquiJoinWithRightOuterJoin(TestPlanCompiler.java:161) > testCompileEquiJoinWithFullOuterJoin(org.apache.storm.sql.compiler.backends.trident.TestPlanCompiler) > Time elapsed: 2.447 sec <<< FAILURE! > org.junit.internal.ArrayComparisonFailure: arrays first differed at element > [0]; expected:<[null, dept-2]> but was:<[null, dept-3]> > at > org.junit.internal.ComparisonCriteria.arrayEquals(ComparisonCriteria.java:50) > at org.junit.Assert.internalArrayEquals(Assert.java:473) > at org.junit.Assert.assertArrayEquals(Assert.java:265) > at org.junit.Assert.assertArrayEquals(Assert.java:280) > at > org.apache.storm.sql.compiler.backends.trident.TestPlanCompiler.testCompileEquiJoinWithFullOuterJoin(TestPlanCompiler.java:179) > testCompileEquiJoinWithLeftOuterJoin(org.apache.storm.sql.compiler.backends.trident.TestPlanCompiler) > Time elapsed: 2.381 sec <<< FAILURE! > org.junit.internal.ArrayComparisonFailure: arrays first differed at element > [0]; expected:<[2, null]> but was:<[3, null]> > at > org.junit.internal.ComparisonCriteria.arrayEquals(ComparisonCriteria.java:50) > at org.junit.Assert.internalArrayEquals(Assert.java:473) > at org.junit.Assert.assertArrayEquals(Assert.java:265) > at org.junit.Assert.assertArrayEquals(Assert.java:280) > at > org.apache.storm.sql.compiler.backends.trident.TestPlanCompiler.testCompileEquiJoinWithLeftOuterJoin(TestPlanCompiler.java:143) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STORM-580) Tunnel logviewer through nimbus so public IPs aren't required for supervisor nodes
[ https://issues.apache.org/jira/browse/STORM-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15510500#comment-15510500 ] Chris Clarke commented on STORM-580: Also, I suspect this might solve STORM-1758 and STORM-1759 > Tunnel logviewer through nimbus so public IPs aren't required for supervisor > nodes > -- > > Key: STORM-580 > URL: https://issues.apache.org/jira/browse/STORM-580 > Project: Apache Storm > Issue Type: New Feature > Components: storm-core >Reporter: Luke Rohde >Assignee: Luke Rohde >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STORM-580) Tunnel logviewer through nimbus so public IPs aren't required for supervisor nodes
[ https://issues.apache.org/jira/browse/STORM-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15510489#comment-15510489 ] Chris Clarke commented on STORM-580: I solved this with a complicated Nginx hack. It would be nice to have this handled in the UI itself, which would require adding configuration for the public domain name, and cleaning up a lot of links in the code. See https://gist.github.com/xofer/e2a703d80979108c76ce53e5361fbc4d > Tunnel logviewer through nimbus so public IPs aren't required for supervisor > nodes > -- > > Key: STORM-580 > URL: https://issues.apache.org/jira/browse/STORM-580 > Project: Apache Storm > Issue Type: New Feature > Components: storm-core >Reporter: Luke Rohde >Assignee: Luke Rohde >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (STORM-2110) in supervisor v2 filter out empty command line args
Robert Joseph Evans created STORM-2110: -- Summary: in supervisor v2 filter out empty command line args Key: STORM-2110 URL: https://issues.apache.org/jira/browse/STORM-2110 Project: Apache Storm Issue Type: Bug Components: storm-core Affects Versions: 2.0.0 Reporter: Robert Joseph Evans Assignee: Robert Joseph Evans Priority: Critical Just found this in Staging as well. In the old supervisor code we would filter out all empty command line args. This was missed in the new supervisor, but only when we split a String opts on white space. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (STORM-2109) Under supervisor V2 SUPERVISOR_MEMORY_CAPACITY_MB and SUPERVISOR_CPU_CAPACITY must be Doubles
Robert Joseph Evans created STORM-2109: -- Summary: Under supervisor V2 SUPERVISOR_MEMORY_CAPACITY_MB and SUPERVISOR_CPU_CAPACITY must be Doubles Key: STORM-2109 URL: https://issues.apache.org/jira/browse/STORM-2109 Project: Apache Storm Issue Type: Bug Components: storm-core Affects Versions: 2.0.0 Reporter: Robert Joseph Evans Assignee: Robert Joseph Evans Just found this rolling out Supervisor V2 to staging env, but it is a simple fix. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (STORM-2109) Under supervisor V2 SUPERVISOR_MEMORY_CAPACITY_MB and SUPERVISOR_CPU_CAPACITY must be Doubles
[ https://issues.apache.org/jira/browse/STORM-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans updated STORM-2109: --- Priority: Critical (was: Major) > Under supervisor V2 SUPERVISOR_MEMORY_CAPACITY_MB and SUPERVISOR_CPU_CAPACITY > must be Doubles > - > > Key: STORM-2109 > URL: https://issues.apache.org/jira/browse/STORM-2109 > Project: Apache Storm > Issue Type: Bug > Components: storm-core >Affects Versions: 2.0.0 >Reporter: Robert Joseph Evans >Assignee: Robert Joseph Evans >Priority: Critical > > Just found this rolling out Supervisor V2 to staging env, but it is a simple > fix. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
