Re: Subscribe me to eagle mailing list

[Edward Zhang]

Hi Deepak,

Please send one email to dev-subscr...@eagle.incubator.apache.org with any
subject/content and follow the instructions to confirm the subscription.

Thanks
Edward

On Sat, Dec 19, 2015 at 12:25 AM, Deepak Dixit 
wrote:

> Hello Team,
>
> Kindly subscribe me to the eagle mailing list.
>
> Thanks,
>
> --
> From:
>
> Deepak D Dixit
> deepakdixit2...@gmail.com
> +919028507537
>

Re: Subscribe me to eagle mailing list

[Edward Zhang]

Thanks so much, will verify it soon.

Thanks
Edward

On Sat, Dec 19, 2015 at 12:25 AM, Deepak Dixit 
wrote:

> Hello Team,
>
> Kindly subscribe me to the eagle mailing list.
>
> Thanks,
>
> --
> From:
>
> Deepak D Dixit
> deepakdixit2...@gmail.com
> +919028507537
>

[GitHub] incubator-eagle pull request: EAGLE-75: Integrate dropwizard metri...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-eagle/pull/28


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [Dev] [Siddhi] what events is left in the window

[Sriskandarajah Suhothayan]

Find the fix here [1]
Do re-open the issue if issue prevails.

If you have any other issues please report.
After fixing them we can also do a Siddhi patch release if you need one.

Regards
Suho

[1]https://wso2.org/jira/browse/CEP-1433

On Thu, Dec 10, 2015 at 11:00 PM, Sriskandarajah Suhothayan 
wrote:

> Thanks for pointing it out,
>
> We are looking into this.
> Will update you ASAP
>
> Suho
>
> On Thu, Dec 10, 2015 at 12:58 AM, Zhang, Edward (GDI Hadoop) <
> yonzh...@ebay.com> wrote:
>
>> By the way, we use siddhi version 3.0.2.
>>
>> Also for tracking this issue, I created jira
>> https://wso2.org/jira/browse/CEP-1433 snapshot/restore does not work for
>> aggregation on time based window
>>
>> Thanks
>> Edward
>>
>> On 12/8/15, 17:57, "Zhang, Edward (GDI Hadoop)" 
>> wrote:
>>
>> >Thanks for this suggestion, Suho.
>> >
>> >I did some testing on state persist and restore, looks most of use cases
>> >are working except group by. I am not if Siddhi team has known this.
>> >
>> >Please look at my test cases : testTimeSlideWindowWithGroupby
>> >
>> https://github.com/yonzhang/incubator-eagle/commit/606b65705ea20ce1592a20d
>> >f9a1f85758168efcb
>> >
>> >The query is like the following
>> >String cseEventStream = "define stream testStream (timeStamp long, user
>> >string, cmd string);";
>> >+ String query = "@info(name = 'query1') from
>> >testStream[cmd == 'open']#window.externalTime(timeStamp,3 sec)"
>> >+ + " select user, timeStamp, count() as cnt"
>> >+ + " group by user"
>> >+ + " having cnt > 2"
>> >+ + " insert all events into outputStream;";
>> >
>> >The basic issue could be the following:
>> >1) when taking snapshot, it will persist all Count executor per key. But
>> >looks Siddhi adds same Count executor into snapshot list multiple
>> >times(The count aggregator elementId is $planName+keyname)
>> >2) when restoring snapshot, it will not restore the Count executor for
>> >key because snopshotableList does not have the above key.  That key only
>> >is generated when event comes in. When do restoration, we don¹t know
>> >previous events.
>> >
>> >for (Snapshotable snapshotable : snapshotableList) {
>> >
>> snapshotable.restoreState(snapshots.get(snapshotable.getElementId()));
>> >}
>> >
>> >Please let me know if there is some issue with my test program or
>> >something is wrong with Siddhi group by/aggregator snapshot
>> >
>> >Thanks
>> >Edward
>> >
>> >From: Sriskandarajah Suhothayan >
>> >Date: Wednesday, November 25, 2015 at 21:07
>> >To: Edward Zhang > >>
>> >Cc: Srinath Perera >, WSO2
>> >Developers' List >
>> >Subject: Re: [Dev] [Siddhi] what events is left in the window
>> >
>> >Hi
>> >
>> >Currently the concept of current event & expired events live within the
>> >query and all events going out to a stream are converted back to current
>> >events. So its hard for the application to keep track of the window and
>> >aggregation states like count, avg, std, etc...
>> >Further window implementations can very based on its implementations
>> >hence in some cases knowing what events entered and existed will not be
>> >enough to recreate the window during failure.
>> >
>> >The recommended way to keep track of state in Siddhi is via snapshots,
>> >you can take snapshots of the siddhi Runtime with a reasonable time
>> >frame. and also buffer a copy of the events sent to siddhi after that
>> >snapshot, with this method when there is a failure we should restore the
>> >latest snapshot and replay the events which are sent after the last
>> >snapshot. The tricky part is the way you buffer events after snapshot,
>> >using Kafka and replaying is one option.
>> >
>> >Regards
>> >Suho
>> >
>> >On Thu, Nov 26, 2015 at 10:01 AM, Edward Zhang
>> >> wrote:
>> >I tried expired events before, it only works for the query without
>> >groupby. If the query contains groupby and having clause, then it only
>> >emit just expired event when having conditions is satisfied.
>> >
>> >For example
>> >
>> >String cseEventStream = "define stream TempStream (user string, cmd
>> >string);";
>> >String query = "@info(name = 'query1') from TempStream#window.length(4) "
>> >+ " select user, cmd, count(user) as cnt " +
>> >" group by user " +
>> >"having cnt > 3 "
>> >+ " insert all events into DelayedTempStream";
>> >
>> >If we send events as follows, it will not generate expired events at all.
>> >
>> >inputHandler.send(new Object[]{"user", "open1"});
>> >inputHandler.send(new Object[]{"user", "open2"});
>> >inputHandler.send(new Object[]{"user", "open3"});
>> >inputHandler.send(new Object[]{"user", "open4"});
>> >inputHandler.send(new Object[]{"user", "open5"});
>> 

[jira] [Commented] (EAGLE-75) Leverage dropwizard metrics for generating Eagle Topology and DataSource Metrics

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065813#comment-15065813
 ] 

ASF GitHub Bot commented on EAGLE-75:
-

Github user sunlibin commented on the pull request:

https://github.com/apache/incubator-eagle/pull/28#issuecomment-166130809
  
Added metric wiki: 
https://cwiki.apache.org/confluence/display/EAG/Eagle+Metric+Framework


> Leverage dropwizard metrics for generating Eagle Topology and DataSource 
> Metrics
> 
>
> Key: EAGLE-75
> URL: https://issues.apache.org/jira/browse/EAGLE-75
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: 0.3.0
>Reporter: Libin, Sun
>Assignee: Libin, Sun
> Fix For: 0.3.0
>
>
> As a monitoring system, eagle need to report & record both the datasource 
> data distribution metric & topology running status metrics to let user have 
> better understanding of the system running status.
> Previously we added a simple metric framework to support user cases like 
> [EAGLE-2](https://issues.apache.org/jira/browse/EAGLE-2) , 
> [EAGLE-24](https://issues.apache.org/jira/browse/EAGLE-24)
> Considering we will have a lot metric user cases to onboard later, we need a 
> better metric framework to make it easier to support these cases, and after 
> some investigation, we found [Dropwizard 
> metrics](https://github.com/dropwizard/metrics) is a good one that can match 
> our needs, So we want to integrate Dropwizard metrics with eagle 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request: EAGLE-75: Integrate dropwizard metri...

[sunlibin]

Github user sunlibin commented on the pull request:

https://github.com/apache/incubator-eagle/pull/28#issuecomment-166130809
  
Added metric wiki: 
https://cwiki.apache.org/confluence/display/EAG/Eagle+Metric+Framework


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-75) Leverage dropwizard metrics for generating Eagle Topology and DataSource Metrics

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065814#comment-15065814
 ] 

ASF GitHub Bot commented on EAGLE-75:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-eagle/pull/28


> Leverage dropwizard metrics for generating Eagle Topology and DataSource 
> Metrics
> 
>
> Key: EAGLE-75
> URL: https://issues.apache.org/jira/browse/EAGLE-75
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: 0.3.0
>Reporter: Libin, Sun
>Assignee: Libin, Sun
> Fix For: 0.3.0
>
>
> As a monitoring system, eagle need to report & record both the datasource 
> data distribution metric & topology running status metrics to let user have 
> better understanding of the system running status.
> Previously we added a simple metric framework to support user cases like 
> [EAGLE-2](https://issues.apache.org/jira/browse/EAGLE-2) , 
> [EAGLE-24](https://issues.apache.org/jira/browse/EAGLE-24)
> Considering we will have a lot metric user cases to onboard later, we need a 
> better metric framework to make it easier to support these cases, and after 
> some investigation, we found [Dropwizard 
> metrics](https://github.com/dropwizard/metrics) is a good one that can match 
> our needs, So we want to integrate Dropwizard metrics with eagle 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-84) Create scripts for merging PRs automatically

[Michael Wu (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065881#comment-15065881
 ] 

Michael Wu commented on EAGLE-84:
-

All functionalities of the script have been completed, including. Have to 
review it with the team to determine:
1. if there is any workflow issue omitted.
2. if the criteria inside the script makes sense.
3. in conjunction with github site, if the defined review flow makes sense.
4. where it should be place.

After all are solved and clear, it should be the time to check-in.

> Create scripts for merging PRs automatically
> 
>
> Key: EAGLE-84
> URL: https://issues.apache.org/jira/browse/EAGLE-84
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
>Assignee: Hao Chen
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> While a pull request gets passed the testing steps, and is verified as 
> good-to-merge, people are willing to merge it with scripts to go through 
> necessary steps automatically, and can form the message of final aggregated 
> commit in a unified format. To achieve this, we are attempted to create the 
> script.
> As discussed, the format of message should be like below (ignore the lines 
> consisted of asterisks):
> **
> EAGLE-${ticket_number} ${ticket_title}
> ${ticket_url}
> Author: ${commiter}
> Reviewer: ${reviewer}
> Closes #${pr_number} from ${do_person}
> **



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)