edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Unai P. Mendizabal (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (EDGENT-430) The way TWindow works
Date Wed, 20 Sep 2017 06:31:01 GMT

    [ https://issues.apache.org/jira/browse/EDGENT-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16172819#comment-16172819

Unai P. Mendizabal commented on EDGENT-430:

[~dlaboss] Thanks for the quick response! And you're right! I must have gotten confused with
the terminology. I tried the batch function out and it works like a charm. Keep it up, bye!

> The way TWindow works
> ---------------------
>                 Key: EDGENT-430
>                 URL: https://issues.apache.org/jira/browse/EDGENT-430
>             Project: Edgent
>          Issue Type: Improvement
>    Affects Versions: Apache Edgent 1.1.0
>            Reporter: Unai P. Mendizabal
>            Priority: Minor
> I've trying Edgent out lately and I can say that I see some potential to it. Keep it
> Anyway, I've been trying the TWindow and its aggregate method and I found out the TWindow
is constantly being created. For example, I have this line of code:
> {code:java}
> TWindow<Double, Integer> window = tempReadings.last(10, TimeUnit.SECONDS, Functions.unpartitioned());
> {code}
> This is non-stopingly filling the TWindow with the readings received within the 10 last
seconds. I can see that it's logical, but I think it would be way more useful if it "created"
a new TWindow with all the readings from the last 10 seconds. This way, I could aggregate
all those readings and send them to the MQTT broker every 10 seconds, instead of with every
new reading (this is, every 100ms), which I think fits better with the purpose of Edgent.
> That's it, thanks!

This message was sent by Atlassian JIRA

View raw message