[
https://issues.apache.org/jira/browse/EDGENT-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16171655#comment-16171655
]
Dale LaBossiere commented on EDGENT-430:
----------------------------------------
Thanks for the encouragement :-)
Sounds like you're using `continuous/sliding` style window aggregations (via
`TWindow.aggregate()`) but should be using `batch` style aggregations (via
`TWindow.batch()`) in order to get the "trigger aggregations / produce result
tuple every 10sec" behavior it sounds like you're asking for?
> 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 up!
> 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
(v6.4.14#64029)
