[
https://issues.apache.org/jira/browse/STORM-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Haohui Mai updated STORM-1097:
--
Issue Type: New Feature (was: Bug)
> Compile IR to Java source code
> --
>
Haohui Mai created STORM-1097:
-
Summary: Compile IR to Java source code
Key: STORM-1097
URL: https://issues.apache.org/jira/browse/STORM-1097
Project: Apache Storm
Issue Type: Bug
Rep
[
https://issues.apache.org/jira/browse/STORM-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14948145#comment-14948145
]
ASF GitHub Bot commented on STORM-1085:
---
GitHub user haohui opened a pull request:
GitHub user haohui opened a pull request:
https://github.com/apache/storm/pull/789
STORM-1085. Compile comparison, arithmetic, and field reference expressions.
This PR augments the compilers to compile the comparison, arithmetic and
field references in SQL expressions.
You can merg
[
https://issues.apache.org/jira/browse/STORM-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Haohui Mai closed STORM-1080.
-
Resolution: Fixed
Thanks [~sriharsha] for the reviews and commits.
> Compiler SQL literals to LLVM consta
[
https://issues.apache.org/jira/browse/STORM-822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14948022#comment-14948022
]
Sriharsha Chintalapani commented on STORM-822:
--
hi [~wurstmeister] , are you
[
https://issues.apache.org/jira/browse/STORM-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani updated STORM-823:
-
Assignee: Hugo Louro
> As a storm developer I’d like to use ITuple interface consis
[
https://issues.apache.org/jira/browse/STORM-825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani updated STORM-825:
-
Assignee: Hugo Louro
> As a storm developer I’d like consistent, structured excepti
[
https://issues.apache.org/jira/browse/STORM-824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani updated STORM-824:
-
Assignee: Hugo Louro
> As a storm developer I’d like all loggers to be private
> --
[
https://issues.apache.org/jira/browse/STORM-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani updated STORM-1015:
--
Assignee: Hang Sun
> Store Kafka offsets with Kafka's consumer offset management
[
https://issues.apache.org/jira/browse/STORM-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani updated STORM-650:
-
Assignee: Hugo Louro
> Storm-Kafka Refactoring and Improvements
> -
[
https://issues.apache.org/jira/browse/STORM-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947773#comment-14947773
]
ASF GitHub Bot commented on STORM-1095:
---
Github user mjsax commented on the pull req
Github user mjsax commented on the pull request:
https://github.com/apache/storm/pull/786#issuecomment-146361062
Just updated this PR.
---
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 fea
[
https://issues.apache.org/jira/browse/STORM-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947717#comment-14947717
]
ASF GitHub Bot commented on STORM-1095:
---
Github user HeartSaVioR commented on the pu
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/786#issuecomment-146351227
@ptgoetz @mjsax
In order to keep backward compatibility, I think we need to decide when to
break backward compatibility.
After Storm 0.9.3, seems like we
[
https://issues.apache.org/jira/browse/STORM-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947662#comment-14947662
]
ASF GitHub Bot commented on STORM-1095:
---
Github user mjsax commented on the pull req
Github user mjsax commented on the pull request:
https://github.com/apache/storm/pull/786#issuecomment-146343033
It's up to you. I had this issues in mind, too... API breaking changes
might be inconvenient/problematic. Just let me know your decision.
---
If your project is set up for
[
https://issues.apache.org/jira/browse/STORM-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947648#comment-14947648
]
ASF GitHub Bot commented on STORM-1096:
---
GitHub user revans2 opened a pull request:
[
https://issues.apache.org/jira/browse/STORM-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947647#comment-14947647
]
ASF GitHub Bot commented on STORM-1096:
---
GitHub user revans2 opened a pull request:
GitHub user revans2 opened a pull request:
https://github.com/apache/storm/pull/787
STORM-1096: Fix some issues with impersonation on the UI
Conflicts:
storm-core/src/clj/backtype/storm/ui/core.clj
You can merge this pull request into a Git repository by running:
$ git
[
https://issues.apache.org/jira/browse/STORM-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947646#comment-14947646
]
ASF GitHub Bot commented on STORM-1095:
---
Github user ptgoetz commented on the pull r
GitHub user revans2 opened a pull request:
https://github.com/apache/storm/pull/788
STORM-1096: Fix some issues with impersonation on the UI
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/revans2/incubator-storm STORM-1096
Alte
Github user ptgoetz commented on the pull request:
https://github.com/apache/storm/pull/786#issuecomment-146341025
Should we consider overloading and deprecating vs. renaming to preserve
backwards compatibility for the short term?
---
If your project is set up for it, you can reply t
GitHub user mjsax opened a pull request:
https://github.com/apache/storm/pull/786
[STORM-1095] Tuple.getSourceGlobalStreamid() has wrong camel-case naming
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mjsax/storm storm-1095
Al
[
https://issues.apache.org/jira/browse/STORM-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947601#comment-14947601
]
ASF GitHub Bot commented on STORM-1095:
---
GitHub user mjsax opened a pull request:
[
https://issues.apache.org/jira/browse/STORM-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhuo Liu updated STORM-1093:
Description:
Currently, we have Resource Aware Scheduler (STORM-894) in nimbus, which can
allocate differen
[
https://issues.apache.org/jira/browse/STORM-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhuo Liu updated STORM-1093:
Description:
Currently, we have Resource Aware Scheduler (STORM-894) in nimbus, which can
allocate differen
[
https://issues.apache.org/jira/browse/STORM-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhuo Liu updated STORM-1093:
Description:
Currently, we have Resource Aware Scheduler (STORM-894) in nimbus, which can
allocate differen
[
https://issues.apache.org/jira/browse/STORM-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhuo Liu updated STORM-1093:
Description:
Currently, we have Resource Aware Scheduler (STORM-894) in nimbus, which can
allocate differen
[
https://issues.apache.org/jira/browse/STORM-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhuo Liu updated STORM-1093:
Description:
Currently, we have Resource Aware Scheduler (STORM-894) in nimbus, which can
allocate differen
[
https://issues.apache.org/jira/browse/STORM-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhuo Liu updated STORM-1093:
Description:
Currently, we have Resource Aware Scheduler (STORM-894) in nimbus, which can
allocate differen
Robert Joseph Evans created STORM-1096:
--
Summary: UI tries to impersonate wrong user when getting topology
conf for authorization, impersonation is allowed by default
Key: STORM-1096
URL: https://issues.apach
Matthias J. Sax created STORM-1095:
--
Summary: Tuple.getSourceGlobalStreamid() has wrong camel-case
naming
Key: STORM-1095
URL: https://issues.apache.org/jira/browse/STORM-1095
Project: Apache Storm
[
https://issues.apache.org/jira/browse/STORM-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947251#comment-14947251
]
ASF GitHub Bot commented on STORM-1084:
---
Github user jerrypeng commented on the pull
Github user jerrypeng commented on the pull request:
https://github.com/apache/storm/pull/785#issuecomment-146272172
@revans2 your suggestion are great, but the parameters passed into java
annotations have to declared to be a specific type thus we could not have:
@MapType(key
[
https://issues.apache.org/jira/browse/STORM-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947229#comment-14947229
]
ASF GitHub Bot commented on STORM-893:
--
Github user jerrypeng commented on the pull re
Github user jerrypeng commented on the pull request:
https://github.com/apache/storm/pull/746#issuecomment-146266179
@erikdw thank you for your review. I reformated some of the files based on
your suggestions
---
If your project is set up for it, you can reply to this email and have
[
https://issues.apache.org/jira/browse/STORM-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947147#comment-14947147
]
ASF GitHub Bot commented on STORM-893:
--
Github user jerrypeng commented on a diff in t
Github user jerrypeng commented on a diff in the pull request:
https://github.com/apache/storm/pull/746#discussion_r41412262
--- Diff: storm-core/src/jvm/backtype/storm/scheduler/Cluster.java ---
@@ -438,6 +451,35 @@ public SupervisorDetails getSupervisorById(String
nodeId) {
[
https://issues.apache.org/jira/browse/STORM-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947135#comment-14947135
]
ASF GitHub Bot commented on STORM-1084:
---
Github user revans2 commented on the pull r
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/785#issuecomment-146250340
@jerrypeng I agree that we want a base set of annotations, and we can
adjust what they do. I am just concerned about making that base set as
flexible and complete as pos
[
https://issues.apache.org/jira/browse/STORM-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947130#comment-14947130
]
ASF GitHub Bot commented on STORM-1084:
---
Github user revans2 commented on the pull r
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/785#issuecomment-146249930
Could we use nested annotations for the complex types?
https://blogs.oracle.com/toddfast/entry/creating_nested_complex_java_annotations
```
@MapType(
Github user jerrypeng commented on the pull request:
https://github.com/apache/storm/pull/785#issuecomment-146248821
Writing another validator like IntegerValidator(min=0, nullAllowed=true) is
a trivial task, but I think we need to first focus on setting a standard of
using annotation
[
https://issues.apache.org/jira/browse/STORM-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947123#comment-14947123
]
ASF GitHub Bot commented on STORM-1084:
---
Github user jerrypeng commented on the pull
[
https://issues.apache.org/jira/browse/STORM-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947119#comment-14947119
]
ASF GitHub Bot commented on STORM-1084:
---
Github user jerrypeng commented on the pull
Github user jerrypeng commented on the pull request:
https://github.com/apache/storm/pull/785#issuecomment-146248606
Well for some for annotations I call a common validator and just pass in
the type that needs to be validated, such as @String @Boolean validators.
---
If your projec
Github user jerrypeng commented on a diff in the pull request:
https://github.com/apache/storm/pull/746#discussion_r41410090
--- Diff:
storm-core/src/jvm/backtype/storm/networktopography/DNSToSwitchMapping.java ---
@@ -0,0 +1,50 @@
+/**
+ * Licensed to the Apache Software F
[
https://issues.apache.org/jira/browse/STORM-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947104#comment-14947104
]
ASF GitHub Bot commented on STORM-1084:
---
Github user revans2 commented on the pull r
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/785#issuecomment-146246638
@jerrypeng
I keep going back and forth on how we want the annotations to work. Right
now they are more or less a one to one translation of what we had before.
Admit
[
https://issues.apache.org/jira/browse/STORM-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947101#comment-14947101
]
ASF GitHub Bot commented on STORM-893:
--
Github user jerrypeng commented on a diff in t
[
https://issues.apache.org/jira/browse/STORM-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947098#comment-14947098
]
ASF GitHub Bot commented on STORM-893:
--
Github user jerrypeng commented on a diff in t
Github user jerrypeng commented on a diff in the pull request:
https://github.com/apache/storm/pull/746#discussion_r41409816
--- Diff:
storm-core/src/jvm/backtype/storm/scheduler/resource/strategies/IStrategy.java
---
@@ -0,0 +1,37 @@
+/**
+ * Licensed to the Apache Softwa
Github user prokopowicz commented on the pull request:
https://github.com/apache/storm/pull/758#issuecomment-146227524
I issued this JIRA regarding the bug:
https://issues.apache.org/jira/browse/STORM-1094
On Tue, Oct 6, 2015 at 3:40 PM, Jungtaek Lim
wrote:
[
https://issues.apache.org/jira/browse/STORM-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947006#comment-14947006
]
ASF GitHub Bot commented on STORM-1094:
---
Github user prokopowicz commented on the pu
Pete Prokopowicz created STORM-1094:
---
Summary: kafka offset does not advance when deserializer yields no
object
Key: STORM-1094
URL: https://issues.apache.org/jira/browse/STORM-1094
Project: Apache
Github user jerrypeng commented on a diff in the pull request:
https://github.com/apache/storm/pull/785#discussion_r41399786
--- Diff:
storm-core/src/jvm/backtype/storm/validation/ConfigValidation.java ---
@@ -0,0 +1,359 @@
+package backtype.storm.validation;
+
+import
[
https://issues.apache.org/jira/browse/STORM-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946972#comment-14946972
]
ASF GitHub Bot commented on STORM-1084:
---
Github user jerrypeng commented on a diff i
[
https://issues.apache.org/jira/browse/STORM-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946968#comment-14946968
]
ASF GitHub Bot commented on STORM-1084:
---
Github user jerrypeng commented on a diff i
Github user jerrypeng commented on a diff in the pull request:
https://github.com/apache/storm/pull/785#discussion_r41399571
--- Diff:
storm-core/src/jvm/backtype/storm/validation/ConfigValidation.java ---
@@ -0,0 +1,359 @@
+package backtype.storm.validation;
--- End diff -
[
https://issues.apache.org/jira/browse/STORM-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhuo Liu updated STORM-1093:
Description:
Currently, we have Resource Aware Scheduler (STORM-894) in nimbus, which can
allocate differen
[
https://issues.apache.org/jira/browse/STORM-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946946#comment-14946946
]
ASF GitHub Bot commented on STORM-1084:
---
Github user revans2 commented on a diff in
[
https://issues.apache.org/jira/browse/STORM-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946944#comment-14946944
]
ASF GitHub Bot commented on STORM-1084:
---
Github user revans2 commented on a diff in
Github user revans2 commented on a diff in the pull request:
https://github.com/apache/storm/pull/785#discussion_r41397489
--- Diff:
storm-core/src/jvm/backtype/storm/validation/ConfigValidation.java ---
@@ -0,0 +1,359 @@
+package backtype.storm.validation;
+
+import or
Github user revans2 commented on a diff in the pull request:
https://github.com/apache/storm/pull/785#discussion_r41397418
--- Diff:
storm-core/src/jvm/backtype/storm/validation/ConfigValidation.java ---
@@ -0,0 +1,359 @@
+package backtype.storm.validation;
--- End diff --
[
https://issues.apache.org/jira/browse/STORM-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhuo Liu updated STORM-1093:
Description:
Currently, we have Resource Aware Scheduler (STORM-894) in nimbus, which can
allocate differen
[
https://issues.apache.org/jira/browse/STORM-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhuo Liu updated STORM-1093:
Description:
Currently, we have Resource Aware Scheduler (STORM-894) in nimbus, which can
allocate differen
[
https://issues.apache.org/jira/browse/STORM-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhuo Liu updated STORM-1093:
Description:
Currently, we have Resource Aware Scheduler (STORM-894) in nimbus, which can
allocate differen
Zhuo Liu created STORM-1093:
---
Summary: Launching Workers with resources specified in
resource-aware schedulers
Key: STORM-1093
URL: https://issues.apache.org/jira/browse/STORM-1093
Project: Apache Storm
Github user Crim commented on the pull request:
https://github.com/apache/storm/pull/758#issuecomment-146187081
+1 running into this issue as well
---
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 h
NickXu created STORM-1092:
-
Summary: Writing issue on
https://storm.apache.org/about/fault-tolerant.html
Key: STORM-1092
URL: https://issues.apache.org/jira/browse/STORM-1092
Project: Apache Storm
I
Github user erikdw commented on a diff in the pull request:
https://github.com/apache/storm/pull/746#discussion_r41366711
--- Diff: storm-core/src/jvm/backtype/storm/scheduler/Cluster.java ---
@@ -438,6 +451,35 @@ public SupervisorDetails getSupervisorById(String
nodeId) {
[
https://issues.apache.org/jira/browse/STORM-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946544#comment-14946544
]
ASF GitHub Bot commented on STORM-893:
--
Github user erikdw commented on a diff in the
[
https://issues.apache.org/jira/browse/STORM-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946537#comment-14946537
]
ASF GitHub Bot commented on STORM-893:
--
Github user erikdw commented on a diff in the
Github user erikdw commented on a diff in the pull request:
https://github.com/apache/storm/pull/746#discussion_r41366483
--- Diff:
storm-core/src/jvm/backtype/storm/networktopography/DNSToSwitchMapping.java ---
@@ -0,0 +1,50 @@
+/**
+ * Licensed to the Apache Software Foun
[
https://issues.apache.org/jira/browse/STORM-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946531#comment-14946531
]
Eee Wang commented on STORM-718:
seems that storm.taobao.org has a zk error which causes th
[
https://issues.apache.org/jira/browse/STORM-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946528#comment-14946528
]
ASF GitHub Bot commented on STORM-893:
--
Github user erikdw commented on a diff in the
Github user erikdw commented on a diff in the pull request:
https://github.com/apache/storm/pull/746#discussion_r41366160
--- Diff:
storm-core/src/jvm/backtype/storm/scheduler/resource/strategies/IStrategy.java
---
@@ -0,0 +1,37 @@
+/**
+ * Licensed to the Apache Software
Github user caishize commented on the pull request:
https://github.com/apache/storm/pull/667#issuecomment-146106627
Yes,there's an update haven't been submitted, but it still only works on
an Linux operating system which has the cgroup installed..
Sent from my iPhone
[
https://issues.apache.org/jira/browse/STORM-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946452#comment-14946452
]
ASF GitHub Bot commented on STORM-1080:
---
Github user asfgit closed the pull request
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/778
---
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 enabl
81 matches
Mail list logo
