[
https://issues.apache.org/jira/browse/STORM-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234547#comment-15234547
]
ASF GitHub Bot commented on STORM-979:
--
GitHub user subhankarb opened a pull request:
GitHub user subhankarb opened a pull request:
https://github.com/apache/storm/pull/1328
[STORM-979][storm-elasticsearch] BaseQueryFunction to query to ES for
trident
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/subhankarb/sto
[
https://issues.apache.org/jira/browse/STORM-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim updated STORM-1703:
Attachment: RollingTopWords-2.0.0-SNAPSHOT.log
RollingTopWords-2.0.0-SNAPSHOT.jstack
[
https://issues.apache.org/jira/browse/STORM-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim updated STORM-1703:
Affects Version/s: 2.0.0
> In local mode, process is not shutting down clearly
> ---
Jungtaek Lim created STORM-1704:
---
Summary: When logviewer.html opens daemon file, next search always
show no result
Key: STORM-1704
URL: https://issues.apache.org/jira/browse/STORM-1704
Project: Apache
[
https://issues.apache.org/jira/browse/STORM-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim updated STORM-1703:
Attachment: RollingTopWords-thread-dump.jstack
RollingTopWords.log
> In local mode,
Jungtaek Lim created STORM-1703:
---
Summary: In local mode, process is not shutting down clearly
Key: STORM-1703
URL: https://issues.apache.org/jira/browse/STORM-1703
Project: Apache Storm
Issue
This vote is now closed, and passes with 5 binding +1 votes, 3 non-binding +1
votes, and 1 non-binding -1 vote.
Vote tally (* indicates a binding vote):
+1:
- P. Taylor Goetz*
- Arun Mahadevan*
- Satish Duggana
- Jungtaek Lim*
- Bobby Evans*
- John Fang
- Xin Wang
- Sriharsha Chintalapani*
-1:
Randy Gelhausen created STORM-1702:
--
Summary: DirectGrouping
Key: STORM-1702
URL: https://issues.apache.org/jira/browse/STORM-1702
Project: Apache Storm
Issue Type: Bug
Components
[
https://issues.apache.org/jira/browse/STORM-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234448#comment-15234448
]
ASF GitHub Bot commented on STORM-1701:
---
Github user dossett commented on a diff in
Github user dossett commented on a diff in the pull request:
https://github.com/apache/storm/pull/1327#discussion_r59150105
--- Diff:
external/storm-hbase/src/main/java/org/apache/storm/hbase/bolt/HBaseLookupBolt.java
---
@@ -68,7 +69,13 @@ public void execute(Tuple tuple) {
[
https://issues.apache.org/jira/browse/STORM-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234439#comment-15234439
]
Kristopher Kane commented on STORM-1701:
Need guidance on whether ParseException i
[
https://issues.apache.org/jira/browse/STORM-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234437#comment-15234437
]
ASF GitHub Bot commented on STORM-1701:
---
GitHub user kristopherkane opened a pull re
GitHub user kristopherkane opened a pull request:
https://github.com/apache/storm/pull/1327
STORM-1701 simple JSON mapping
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kristopherkane/storm master
Alternatively you can review
Kristopher Kane created STORM-1701:
--
Summary: Add simple JSON mapping to storm-hbase
Key: STORM-1701
URL: https://issues.apache.org/jira/browse/STORM-1701
Project: Apache Storm
Issue Type: I
HI Arun,
thank you for your reply.
But my problem is that I need to add up the values over all devices, but I am
only allowed to use the most recent value of each device. A value is valid as
long as there is no new value for this device available.
So if I receive a message with device A with
Hi Matthias,
WindowedBolt does support event time. In trident its is not yet exposed.
Hi Daniela,
You could solve your use cases in different ways. One would be to have a
WindowedBolt with a 1 min tumbling window, do your custom aggregation (e.g.
sum) every time the window tumbles and emit th
Hi
Would the following scenario be reasonable:
1.)Kafka Spout
2.)Storm Bolt for storing active devices in and deleting inactive
devices from Redis
3.)Storm Bolt with tick tuple for pulling the active devices from Redis
every minute
4.)Storm Bolt to calculate from the act
[
https://issues.apache.org/jira/browse/STORM-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234178#comment-15234178
]
ASF GitHub Bot commented on STORM-1693:
---
GitHub user abhishekagarwal87 opened a pull
GitHub user abhishekagarwal87 opened a pull request:
https://github.com/apache/storm/pull/1326
STORM-1693: Do not cancel the task after stats are rendered
Fresher task is cancelled right after 3 seconds when executor heartbeat is
sent. getValueAndReset can rotate the buckets but it
Thank you very much for your reply.
And within the window function I can pull the data from Redis? So would the
window bolt and the bolt which pulls the data from Redis be the same one?
What exactly is the difference between processing time window and event time
window?
Thank you in advance.
R
A tumbling window (ie, non-overlapping window) is the right approach (a
sliding window is overlapping).
The window goes into your aggregation bolt (windowing and aggregation
goes hand in hand, ie, when the window gets closed, the aggregation is
triggered and the window content is handed over to th
Hi,
thank you for your reply.
How can I ensure that the latest values are pulled from Redis the sum is
updated every minute? Do I need a sliding window with an interval of 1
minute? Where would this sliding window be located in my topology?
Thank you in advance.
Regards,
Daniela
-Ursprüng
23 matches
Mail list logo
