Re: January 2016 Report
Hi,
I see the report for Eagle has been updated on wiki -
http://wiki.apache.org/incubator/January2016.
Nicely summarised report!
Have a couple of comments :
- Following sentence is incomplete :
1. We have submitted papers and applied to conferences. We worked
with other open source projects like
- For Date of last release and When were last committers added - you can
put it as NONE.
Thanks
Amareshwari
On Thu, Dec 31, 2015 at 3:30 AM, Marvin Humphrey wrote:
> Greetings, {podling} developers!
>
> This is a reminder that your report is due next Wednesday, January
> 6th. Details below.
>
> Best,
>
> Marvin Humphrey, Report Manager for January, on behalf of the
> Incubator PMC
>
> ---
>
> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 20 January 2016, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, January 6th).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> * Your project name
> * A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> * A list of the three most important issues to address in the move
> towards graduation.
> * Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> * How has the community developed since the last report
> * How has the project developed since the last report.
>
> This should be appended to the Incubator Wiki page at:
>
> http://wiki.apache.org/incubator/January2016
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>
>
[jira] [Commented] (EAGLE-95) DAM HDFS topology fails to start, if there is invalid policy.
[ https://issues.apache.org/jira/browse/EAGLE-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15080864#comment-15080864 ] Murali Krishna commented on EAGLE-95: - Design is being tracked in this Wiki - https://cwiki.apache.org/confluence/display/EAG/Policy+Markdown+Feature. > DAM HDFS topology fails to start, if there is invalid policy. > - > > Key: EAGLE-95 > URL: https://issues.apache.org/jira/browse/EAGLE-95 > Project: Eagle > Issue Type: Bug >Reporter: hemanth dendukuri >Assignee: Senthilkumar >Priority: Critical > > Step 1: Create a invalid policy (from hdfsAuditLogEventStream[(cmd == 'open') > and (str:contains(src,'/tmp/p')==true)] select * insert into outputStream;) > Step 2 : Deploy Dam HDFS topology. > Actual : The HDFS topology could not start because of the invalid policy. > 2015-12-16 23:51:17 b.s.d.executor [INFO] Shutting down executor > AlertEntityDeduplicationExecutor_9:[2 2] 2015-12-16 23:51:17 b.s.util [INFO] > Async loop interrupted! > Expected: Topology should start ignoring the invalid policy. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request: EAGLE-79 Provide basic aggregation
GitHub user RalphSu opened a pull request: https://github.com/apache/incubator-eagle/pull/52 EAGLE-79 Provide basic aggregation https://issues.apache.org/jira/browse/EAGLE-79 1. Support aggregation api 2. Support persist Api 3. Refactor AlertExecutor to be policy wide. You can merge this pull request into a Git repository by running: $ git pull https://github.com/RalphSu/incubator-eagle aggregation Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/52.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #52 commit c8c8408ec7e02b1eb92b89770cc9838bb14dcf86 Author: Su Date: 2015-12-15T07:54:11Z EAGLE-88: Eagle web-service should have status url https://issues.apache.org/jira/browse/EAGLE-88 Clear the dependency to make dev able to start eagle-service with mvn tomcat7:run Add template monitor resource which returns OK for external monitoring commit e520e473542ae2a3eb95a5474ef38ce76f442336 Author: Su Date: 2015-12-15T08:22:23Z version as maven property commit 6fc745a4e1e27d93049275f170df25a544c5ed45 Author: Su Date: 2015-12-15T08:26:12Z add more scala templates commit d9edf6c6f882ba9f1a0f3d97a1c04e45daf91444 Author: Su Date: 2015-12-15T08:29:04Z remove author info commit 9331dda314497701c27548aae4de381594840aeb Author: Ralph, Su Date: 2015-12-17T08:26:48Z refactor the policy executor framework commit 3bdfb40299672ebf51e73adf12fc4d6ba0a056a4 Author: Ralph, Su Date: 2015-12-17T09:08:53Z refactor the dao implementation commit b754be8d368a6bc976702b992e1f53e7ef0831e1 Author: Ralph, Su Date: 2015-12-18T02:41:04Z merge with latest relase commit a42457eea4b5f9d9aca263368b9e28466358470f Author: Ralph, Su Date: 2015-12-18T09:26:29Z complete the executor abstraction commit cf7e8b4f825b1061ca5cb511f3376aaa1d3de00e Author: Ralph, Su Date: 2015-12-21T04:21:26Z add test for expansion commit f5532bf4d7ce408aefd7ecda43546139455c2a89 Author: Ralph, Su Date: 2015-12-21T06:25:54Z merge with latest code commit 5018cdbbb0df40db0d3f310ffe7b9142df266e78 Author: Ralph, Su Date: 2015-12-21T06:45:08Z rename the definition entity commit edc7ecf78b796bafbca007b403d4f242889427c7 Author: Ralph, Su Date: 2015-12-21T09:45:18Z add test for aggregation commit bf686fb3a468754969801ef27ecea67c085108a3 Author: Ralph, Su Date: 2015-12-21T10:13:50Z add more tests commit fc93c3b761fe24a74a72463fe433e9b447bd485a Author: ralphsu Date: 2015-12-24T05:43:37Z Update README.md commit 36848ef0ddf8f348e3f2d979cbc54f2c94ef03af Author: Ralph, Su Date: 2015-12-24T08:51:50Z rename analyze to aggregate commit 8130f808eae9a2cc95b295f9dd899d2efb724f54 Author: Ralph, Su Date: 2015-12-28T07:42:51Z rename the analyze to aggregate commit 1f53b8a8a413287a0aacf67fc441cfd19cbd9c80 Author: Ralph, Su Date: 2015-12-28T07:43:30Z Merge branch 'master' of https://github.com/RalphSu/incubator-eagle into aggergation commit 3f25cc256b862df20dae78558df78dbf6aa31046 Author: Ralph, Su Date: 2015-12-28T09:52:26Z add persist executor commit c714a8e572aa66ba5f21ba3fd35a00bf0e37db9a Author: Ralph, Su Date: 2015-12-28T13:00:25Z refactor commit 9d71417c7efd44ae05a8b0a244ecc959045f4ff7 Author: Ralph, Su Date: 2015-12-29T11:05:27Z compiled OK commit 931437e28aa1dc5b6283fa6b805be251ad1a0676 Author: Ralph, Su Date: 2016-01-03T07:19:22Z rename the package back commit 85994e73fc5276d77a46c238690583181f671992 Author: Ralph, Su Date: 2016-01-04T01:43:54Z add comments for executor commit 985047045e9e27329d02bae3cd7a31f0c698ad16 Author: Ralph, Su Date: 2016-01-04T03:46:36Z merge with latest code commit 76de45f751b00dd205c675d228ad0e3fab070a83 Author: Ralph, Su Date: 2016-01-04T05:57:49Z fix two unit test failure in local commit ca301afa49906674a8598c64d6f4e5d143f23ec7 Author: Ralph, Su Date: 2016-01-04T09:57:46Z add test projects commit 2e36c76be5519faf36f5297c9b7bef4380ca9da1 Author: Ralph, Su Date: 2016-01-04T10:51:42Z add service init.rb to create hbase table --- 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-79) Provide analytic DSL support
[ https://issues.apache.org/jira/browse/EAGLE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15081183#comment-15081183 ] ASF GitHub Bot commented on EAGLE-79: - GitHub user RalphSu opened a pull request: https://github.com/apache/incubator-eagle/pull/52 EAGLE-79 Provide basic aggregation https://issues.apache.org/jira/browse/EAGLE-79 1. Support aggregation api 2. Support persist Api 3. Refactor AlertExecutor to be policy wide. You can merge this pull request into a Git repository by running: $ git pull https://github.com/RalphSu/incubator-eagle aggregation Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/52.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #52 commit c8c8408ec7e02b1eb92b89770cc9838bb14dcf86 Author: Su Date: 2015-12-15T07:54:11Z EAGLE-88: Eagle web-service should have status url https://issues.apache.org/jira/browse/EAGLE-88 Clear the dependency to make dev able to start eagle-service with mvn tomcat7:run Add template monitor resource which returns OK for external monitoring commit e520e473542ae2a3eb95a5474ef38ce76f442336 Author: Su Date: 2015-12-15T08:22:23Z version as maven property commit 6fc745a4e1e27d93049275f170df25a544c5ed45 Author: Su Date: 2015-12-15T08:26:12Z add more scala templates commit d9edf6c6f882ba9f1a0f3d97a1c04e45daf91444 Author: Su Date: 2015-12-15T08:29:04Z remove author info commit 9331dda314497701c27548aae4de381594840aeb Author: Ralph, Su Date: 2015-12-17T08:26:48Z refactor the policy executor framework commit 3bdfb40299672ebf51e73adf12fc4d6ba0a056a4 Author: Ralph, Su Date: 2015-12-17T09:08:53Z refactor the dao implementation commit b754be8d368a6bc976702b992e1f53e7ef0831e1 Author: Ralph, Su Date: 2015-12-18T02:41:04Z merge with latest relase commit a42457eea4b5f9d9aca263368b9e28466358470f Author: Ralph, Su Date: 2015-12-18T09:26:29Z complete the executor abstraction commit cf7e8b4f825b1061ca5cb511f3376aaa1d3de00e Author: Ralph, Su Date: 2015-12-21T04:21:26Z add test for expansion commit f5532bf4d7ce408aefd7ecda43546139455c2a89 Author: Ralph, Su Date: 2015-12-21T06:25:54Z merge with latest code commit 5018cdbbb0df40db0d3f310ffe7b9142df266e78 Author: Ralph, Su Date: 2015-12-21T06:45:08Z rename the definition entity commit edc7ecf78b796bafbca007b403d4f242889427c7 Author: Ralph, Su Date: 2015-12-21T09:45:18Z add test for aggregation commit bf686fb3a468754969801ef27ecea67c085108a3 Author: Ralph, Su Date: 2015-12-21T10:13:50Z add more tests commit fc93c3b761fe24a74a72463fe433e9b447bd485a Author: ralphsu Date: 2015-12-24T05:43:37Z Update README.md commit 36848ef0ddf8f348e3f2d979cbc54f2c94ef03af Author: Ralph, Su Date: 2015-12-24T08:51:50Z rename analyze to aggregate commit 8130f808eae9a2cc95b295f9dd899d2efb724f54 Author: Ralph, Su Date: 2015-12-28T07:42:51Z rename the analyze to aggregate commit 1f53b8a8a413287a0aacf67fc441cfd19cbd9c80 Author: Ralph, Su Date: 2015-12-28T07:43:30Z Merge branch 'master' of https://github.com/RalphSu/incubator-eagle into aggergation commit 3f25cc256b862df20dae78558df78dbf6aa31046 Author: Ralph, Su Date: 2015-12-28T09:52:26Z add persist executor commit c714a8e572aa66ba5f21ba3fd35a00bf0e37db9a Author: Ralph, Su Date: 2015-12-28T13:00:25Z refactor commit 9d71417c7efd44ae05a8b0a244ecc959045f4ff7 Author: Ralph, Su Date: 2015-12-29T11:05:27Z compiled OK commit 931437e28aa1dc5b6283fa6b805be251ad1a0676 Author: Ralph, Su Date: 2016-01-03T07:19:22Z rename the package back commit 85994e73fc5276d77a46c238690583181f671992 Author: Ralph, Su Date: 2016-01-04T01:43:54Z add comments for executor commit 985047045e9e27329d02bae3cd7a31f0c698ad16 Author: Ralph, Su Date: 2016-01-04T03:46:36Z merge with latest code commit 76de45f751b00dd205c675d228ad0e3fab070a83 Author: Ralph, Su Date: 2016-01-04T05:57:49Z fix two unit test failure in local commit ca301afa49906674a8598c64d6f4e5d143f23ec7 Author: Ralph, Su Date: 2016-01-04T09:57:46Z add test projects commit 2e36c76be5519faf36f5297c9b7bef4380ca9da1 Author: Ralph, Su Date: 2016-01-04T10:51:42Z add service init.rb to create hbase table > Provide analytic DSL support > - > > Key: EAGLE-79 > URL: https://issues.apache.org/jira/browse/EAGLE-79 > Project: Eagle > Issue Type: New Feature >Affects Versions: 0.3.0 >Reporter: Su Ralph >Assignee: Su Ralph > Fix For: 0.3.0 > > > Eagle input comes with stream data (like security audit log), eagle p
[GitHub] incubator-eagle pull request: EAGLE-11111 This pr is for testing c...
Github user anyway1021 commented on the pull request: https://github.com/apache/incubator-eagle/pull/48#issuecomment-168744299 LGTM --- 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: January 2016 Report
+1 to the nice summary!
Perhaps the details under those sections, like new contributors and release
plan etc can be moved under "How has the community developed" section ?
thanks
Prasad
On Mon, Jan 4, 2016 at 12:49 AM, amareshwarisr .
wrote:
> Hi,
>
> I see the report for Eagle has been updated on wiki -
> http://wiki.apache.org/incubator/January2016.
>
> Nicely summarised report!
>
> Have a couple of comments :
>
>- Following sentence is incomplete :
>
> 1. We have submitted papers and applied to conferences. We worked
> with other open source projects like
>
>
>- For Date of last release and When were last committers added - you can
>put it as NONE.
>
> Thanks
> Amareshwari
>
> On Thu, Dec 31, 2015 at 3:30 AM, Marvin Humphrey
> wrote:
>
> > Greetings, {podling} developers!
> >
> > This is a reminder that your report is due next Wednesday, January
> > 6th. Details below.
> >
> > Best,
> >
> > Marvin Humphrey, Report Manager for January, on behalf of the
> > Incubator PMC
> >
> > ---
> >
> > Dear podling,
> >
> > This email was sent by an automated system on behalf of the Apache
> > Incubator PMC. It is an initial reminder to give you plenty of time to
> > prepare your quarterly board report.
> >
> > The board meeting is scheduled for Wed, 20 January 2016, 10:30 am PDT.
> > The report for your podling will form a part of the Incubator PMC
> > report. The Incubator PMC requires your report to be submitted 2 weeks
> > before the board meeting, to allow sufficient time for review and
> > submission (Wed, January 6th).
> >
> > Please submit your report with sufficient time to allow the Incubator
> > PMC, and subsequently board members to review and digest. Again, the
> > very latest you should submit your report is 2 weeks prior to the board
> > meeting.
> >
> > Thanks,
> >
> > The Apache Incubator PMC
> >
> > Submitting your Report
> >
> > --
> >
> > Your report should contain the following:
> >
> > * Your project name
> > * A brief description of your project, which assumes no knowledge of
> > the project or necessarily of its field
> > * A list of the three most important issues to address in the move
> > towards graduation.
> > * Any issues that the Incubator PMC or ASF Board might wish/need to be
> > aware of
> > * How has the community developed since the last report
> > * How has the project developed since the last report.
> >
> > This should be appended to the Incubator Wiki page at:
> >
> > http://wiki.apache.org/incubator/January2016
> >
> > Note: This is manually populated. You may need to wait a little before
> > this page is created from a template.
> >
> > Mentors
> > ---
> >
> > Mentors should review reports for their project(s) and sign them off on
> > the Incubator wiki page. Signing off reports shows that you are
> > following the project - projects that are not signed may raise alarms
> > for the Incubator PMC.
> >
> > Incubator PMC
> >
> >
>
[jira] [Created] (EAGLE-115) Fix licenses headers for webapp files
Prasad Mujumdar created EAGLE-115: - Summary: Fix licenses headers for webapp files Key: EAGLE-115 URL: https://issues.apache.org/jira/browse/EAGLE-115 Project: Eagle Issue Type: Bug Affects Versions: 0.3.0 Reporter: Prasad Mujumdar This is a followup ticket to EAGLE-114 to track the files in webapp under eagle-webservice. There are a large number of non source code files that needs to be handled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: January 2016 Report
Thanks folks.
I have updated the content based on the feedback.
On Mon, Jan 4, 2016 at 10:14 AM, Prasad Mujumdar wrote:
>+1 to the nice summary!
>
> Perhaps the details under those sections, like new contributors and release
> plan etc can be moved under "How has the community developed" section ?
>
> thanks
> Prasad
>
>
> On Mon, Jan 4, 2016 at 12:49 AM, amareshwarisr .
> wrote:
>
> > Hi,
> >
> > I see the report for Eagle has been updated on wiki -
> > http://wiki.apache.org/incubator/January2016.
> >
> > Nicely summarised report!
> >
> > Have a couple of comments :
> >
> >- Following sentence is incomplete :
> >
> > 1. We have submitted papers and applied to conferences. We worked
> > with other open source projects like
> >
> >
> >- For Date of last release and When were last committers added - you
> can
> >put it as NONE.
> >
> > Thanks
> > Amareshwari
> >
> > On Thu, Dec 31, 2015 at 3:30 AM, Marvin Humphrey
> > wrote:
> >
> > > Greetings, {podling} developers!
> > >
> > > This is a reminder that your report is due next Wednesday, January
> > > 6th. Details below.
> > >
> > > Best,
> > >
> > > Marvin Humphrey, Report Manager for January, on behalf of the
> > > Incubator PMC
> > >
> > > ---
> > >
> > > Dear podling,
> > >
> > > This email was sent by an automated system on behalf of the Apache
> > > Incubator PMC. It is an initial reminder to give you plenty of time to
> > > prepare your quarterly board report.
> > >
> > > The board meeting is scheduled for Wed, 20 January 2016, 10:30 am PDT.
> > > The report for your podling will form a part of the Incubator PMC
> > > report. The Incubator PMC requires your report to be submitted 2 weeks
> > > before the board meeting, to allow sufficient time for review and
> > > submission (Wed, January 6th).
> > >
> > > Please submit your report with sufficient time to allow the Incubator
> > > PMC, and subsequently board members to review and digest. Again, the
> > > very latest you should submit your report is 2 weeks prior to the board
> > > meeting.
> > >
> > > Thanks,
> > >
> > > The Apache Incubator PMC
> > >
> > > Submitting your Report
> > >
> > > --
> > >
> > > Your report should contain the following:
> > >
> > > * Your project name
> > > * A brief description of your project, which assumes no knowledge of
> > > the project or necessarily of its field
> > > * A list of the three most important issues to address in the move
> > > towards graduation.
> > > * Any issues that the Incubator PMC or ASF Board might wish/need to
> be
> > > aware of
> > > * How has the community developed since the last report
> > > * How has the project developed since the last report.
> > >
> > > This should be appended to the Incubator Wiki page at:
> > >
> > > http://wiki.apache.org/incubator/January2016
> > >
> > > Note: This is manually populated. You may need to wait a little before
> > > this page is created from a template.
> > >
> > > Mentors
> > > ---
> > >
> > > Mentors should review reports for their project(s) and sign them off on
> > > the Incubator wiki page. Signing off reports shows that you are
> > > following the project - projects that are not signed may raise alarms
> > > for the Incubator PMC.
> > >
> > > Incubator PMC
> > >
> > >
> >
>
--
Arun Karthick
201-850-9399
Re: [DISCUSS] - Adding RAT check to build for Apache lincese header check
I agree, it is better if it is enabled by default. At least in Ranger we have seen builds failing and we scrambling to fix the build. Bosco On 1/2/16, 11:51 PM, "Prasad Mujumdar" wrote: >Hey Hao, > > Thanks for clarifying that. > >When it's forced in the build, the owners is on every developer to ensure >that the new files have the correct license header. They can fix any >missing files locally (or add an exception when applicable). Keeping this >in CI or release build makes the process longer and requires more iteration >for each patch/release. >Let me know if it's still preferred in CI. The header updates in the PR are >still needed. > >thanks >Prasad > > >On Sat, Jan 2, 2016 at 10:36 PM, Hao Chen wrote: > >> Hi Prasad, >> >> Thanks for it. We declared RAT in pom plugin management and enable by >> command arguments when necessary but not forcefully, which would be added >> in CI. >> >> Thanks, >> Hao >> >> > On Jan 3, 2016, at 12:01 PM, Prasad Mujumdar >> wrote: >> > >> > Hello Hao, >> > >> > There's RAT plugin defined under plugin management, however it's not >> > enabled. Also there are a number of files that are missing the license >> > header. I just submitted the PR #51 [2] that adds license header to 26 >> > files, plus the ones under webapp still needs to be handled. >> > >> > thanks >> > Prasad >> > >> > [2] - https://github.com/apache/incubator-eagle/pull/51 >> > >> >> On Sat, Jan 2, 2016 at 7:18 PM, Hao Chen wrote: >> >> >> >> RAT has already been enabled in the pom when open source. >> >> >> On Jan 3, 2016, at 6:30 AM, Edward Zhang >> >>> wrote: >> >>> >> >>> Good point to have tools to identify missing license header, we should >> >> have >> >>> that. >> >>> >> >>> In terms of license headers under eagle-webservice, I remembered there >> >> was >> >>> some discussion on the license of those files, probably Jilin can >> provide >> >>> more details. >> >>> >> >>> Thanks >> >>> >> >>> Edward >> >>> >> On Sat, Jan 2, 2016 at 1:25 PM, Prasad Mujumdar >> >> wrote: >> >> Hi, >> >> Looks like we have a bunch of files that are missing the Apache >> >> license >> headers. IMO it's a good idea to add the Maven RAT plugin to ensure >> that >> every new file has license header. Otherwise the responsibility falls >> on >> the release manager's head to correct it and makes the release process >> longer and tedious. >> I have logged a ticket EAGLE-114 [1] to track it and got a working >> patch >> that I can submit a PR. One of the problem fileset is the webapp under >> eagle-webservice. There are a large number of files which don't have >> license header. I would like to create a separate ticket to track >> which >> files should have the header and which should be excluded. >> >> Let me know if that sounds reasonable. >> >> thanks >> Prasad >> >> [1] - https://issues.apache.org/jira/browse/EAGLE-114 >> >> >>
[jira] [Resolved] (EAGLE-106) UI use same chart component
[ https://issues.apache.org/jira/browse/EAGLE-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jilin, Jiang resolved EAGLE-106. Resolution: Fixed > UI use same chart component > --- > > Key: EAGLE-106 > URL: https://issues.apache.org/jira/browse/EAGLE-106 > Project: Eagle > Issue Type: Improvement >Reporter: Jilin, Jiang >Assignee: Jilin, Jiang >Priority: Minor > > Currently chart in policy & user profile page using flot which is none-update > more than 1 year. Some of the chart feature need addtional code effort. > Replace it with nvd3. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [DISCUSS] - Adding RAT check to build for Apache lincese header check
I think it’s a good suggestion, please move ahead to enable it by default and fix the missing license headers. Thanks, Hao On 1/5/16, 5:58 AM, "Don Bosco Durai" wrote: >I agree, it is better if it is enabled by default. At least in Ranger we have >seen builds failing and we scrambling to fix the build. > >Bosco > > > > >On 1/2/16, 11:51 PM, "Prasad Mujumdar" wrote: > >>Hey Hao, >> >> Thanks for clarifying that. >> >>When it's forced in the build, the owners is on every developer to ensure >>that the new files have the correct license header. They can fix any >>missing files locally (or add an exception when applicable). Keeping this >>in CI or release build makes the process longer and requires more iteration >>for each patch/release. >>Let me know if it's still preferred in CI. The header updates in the PR are >>still needed. >> >>thanks >>Prasad >> >> >>On Sat, Jan 2, 2016 at 10:36 PM, Hao Chen wrote: >> >>> Hi Prasad, >>> >>> Thanks for it. We declared RAT in pom plugin management and enable by >>> command arguments when necessary but not forcefully, which would be added >>> in CI. >>> >>> Thanks, >>> Hao >>> >>> > On Jan 3, 2016, at 12:01 PM, Prasad Mujumdar >>> wrote: >>> > >>> > Hello Hao, >>> > >>> > There's RAT plugin defined under plugin management, however it's not >>> > enabled. Also there are a number of files that are missing the license >>> > header. I just submitted the PR #51 [2] that adds license header to 26 >>> > files, plus the ones under webapp still needs to be handled. >>> > >>> > thanks >>> > Prasad >>> > >>> > [2] - https://github.com/apache/incubator-eagle/pull/51 >>> > >>> >> On Sat, Jan 2, 2016 at 7:18 PM, Hao Chen wrote: >>> >> >>> >> RAT has already been enabled in the pom when open source. >>> >> >>> On Jan 3, 2016, at 6:30 AM, Edward Zhang >>> >>> wrote: >>> >>> >>> >>> Good point to have tools to identify missing license header, we should >>> >> have >>> >>> that. >>> >>> >>> >>> In terms of license headers under eagle-webservice, I remembered there >>> >> was >>> >>> some discussion on the license of those files, probably Jilin can >>> provide >>> >>> more details. >>> >>> >>> >>> Thanks >>> >>> >>> >>> Edward >>> >>> >>> On Sat, Jan 2, 2016 at 1:25 PM, Prasad Mujumdar >>> >> wrote: >>> >>> Hi, >>> >>> Looks like we have a bunch of files that are missing the Apache >>> >> license >>> headers. IMO it's a good idea to add the Maven RAT plugin to ensure >>> that >>> every new file has license header. Otherwise the responsibility falls >>> on >>> the release manager's head to correct it and makes the release process >>> longer and tedious. >>> I have logged a ticket EAGLE-114 [1] to track it and got a working >>> patch >>> that I can submit a PR. One of the problem fileset is the webapp under >>> eagle-webservice. There are a large number of files which don't have >>> license header. I would like to create a separate ticket to track >>> which >>> files should have the header and which should be excluded. >>> >>> Let me know if that sounds reasonable. >>> >>> thanks >>> Prasad >>> >>> [1] - https://issues.apache.org/jira/browse/EAGLE-114 >>> >> >>> >
[GitHub] incubator-eagle pull request: EAGLE-79 Provide basic aggregation
Github user haoch commented on a diff in the pull request:
https://github.com/apache/incubator-eagle/pull/52#discussion_r48808851
--- Diff:
eagle-core/eagle-data-process/eagle-stream-process-api/src/main/java/org/apache/eagle/dataproc/impl/persist/druid/DruidPersistService.java
---
@@ -0,0 +1,119 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ *http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.eagle.dataproc.impl.persist.druid;
+
+import com.typesafe.config.Config;
+import com.typesafe.config.ConfigValue;
+import org.apache.eagle.dataproc.impl.aggregate.entity.AggregateEntity;
+import org.apache.eagle.dataproc.impl.persist.IPersistService;
+import org.apache.kafka.clients.producer.KafkaProducer;
+import org.apache.kafka.clients.producer.ProducerRecord;
+import org.apache.kafka.clients.producer.RecordMetadata;
+
+import java.util.*;
+import java.util.concurrent.Future;
+
+/**
+ * TODO : support more general entity input
+ * @since Dec 21, 2015
+ *
+ */
+public class DruidPersistService implements
IPersistService {
--- End diff --
How do you think to rename the `DruidPersistService` to
`KafkaPersistService` here as it's for kafka only in fact. We may have another
`DruidPersistService` using https://github.com/druid-io/tranquility later.
---
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-79) Provide analytic DSL support
[
https://issues.apache.org/jira/browse/EAGLE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15082286#comment-15082286
]
ASF GitHub Bot commented on EAGLE-79:
-
Github user haoch commented on a diff in the pull request:
https://github.com/apache/incubator-eagle/pull/52#discussion_r48808851
--- Diff:
eagle-core/eagle-data-process/eagle-stream-process-api/src/main/java/org/apache/eagle/dataproc/impl/persist/druid/DruidPersistService.java
---
@@ -0,0 +1,119 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ *http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.eagle.dataproc.impl.persist.druid;
+
+import com.typesafe.config.Config;
+import com.typesafe.config.ConfigValue;
+import org.apache.eagle.dataproc.impl.aggregate.entity.AggregateEntity;
+import org.apache.eagle.dataproc.impl.persist.IPersistService;
+import org.apache.kafka.clients.producer.KafkaProducer;
+import org.apache.kafka.clients.producer.ProducerRecord;
+import org.apache.kafka.clients.producer.RecordMetadata;
+
+import java.util.*;
+import java.util.concurrent.Future;
+
+/**
+ * TODO : support more general entity input
+ * @since Dec 21, 2015
+ *
+ */
+public class DruidPersistService implements
IPersistService {
--- End diff --
How do you think to rename the `DruidPersistService` to
`KafkaPersistService` here as it's for kafka only in fact. We may have another
`DruidPersistService` using https://github.com/druid-io/tranquility later.
> Provide analytic DSL support
> -
>
> Key: EAGLE-79
> URL: https://issues.apache.org/jira/browse/EAGLE-79
> Project: Eagle
> Issue Type: New Feature
>Affects Versions: 0.3.0
>Reporter: Su Ralph
>Assignee: Su Ralph
> Fix For: 0.3.0
>
>
> Eagle input comes with stream data (like security audit log), eagle provide
> alerting computation based on CEP DSL.
> Similar to this process, eagle should be able to provide same DSL support to
> expose the real-time monitoring feature, and furthermore could be integrated
> with some storage backend to provide dashboard/presentation to user.
> This would require
> 1. eagle programming API to support a new semantic of query(or aggregation),
> using the similar alert DSL.
> 2. a clear definition of time series storage interface (so that different
> storage engine could be adopted), currently we might start from the eagle
> built-in hbase implementation
> 3. Metric API/Dashboard.
> Currently, it require a lot of user customization and CEP engine capability
> could not be reused.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] incubator-eagle pull request: EAGLE-79 Provide basic aggregation
Github user haoch commented on a diff in the pull request: https://github.com/apache/incubator-eagle/pull/52#discussion_r48808982 --- Diff: eagle-core/eagle-policy/eagle-policy-base/pom.xml --- @@ -0,0 +1,62 @@ + --- End diff -- It's good to separate policy engine out for reusing in both alerting and aggregation. --- 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-79) Provide analytic DSL support
[ https://issues.apache.org/jira/browse/EAGLE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15082292#comment-15082292 ] ASF GitHub Bot commented on EAGLE-79: - Github user haoch commented on a diff in the pull request: https://github.com/apache/incubator-eagle/pull/52#discussion_r48808982 --- Diff: eagle-core/eagle-policy/eagle-policy-base/pom.xml --- @@ -0,0 +1,62 @@ + --- End diff -- It's good to separate policy engine out for reusing in both alerting and aggregation. > Provide analytic DSL support > - > > Key: EAGLE-79 > URL: https://issues.apache.org/jira/browse/EAGLE-79 > Project: Eagle > Issue Type: New Feature >Affects Versions: 0.3.0 >Reporter: Su Ralph >Assignee: Su Ralph > Fix For: 0.3.0 > > > Eagle input comes with stream data (like security audit log), eagle provide > alerting computation based on CEP DSL. > Similar to this process, eagle should be able to provide same DSL support to > expose the real-time monitoring feature, and furthermore could be integrated > with some storage backend to provide dashboard/presentation to user. > This would require > 1. eagle programming API to support a new semantic of query(or aggregation), > using the similar alert DSL. > 2. a clear definition of time series storage interface (so that different > storage engine could be adopted), currently we might start from the eagle > built-in hbase implementation > 3. Metric API/Dashboard. > Currently, it require a lot of user customization and CEP engine capability > could not be reused. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request: EAGLE-79 Provide basic aggregation
Github user haoch commented on a diff in the pull request:
https://github.com/apache/incubator-eagle/pull/52#discussion_r48809042
--- Diff:
eagle-core/eagle-policy/eagle-policy-base/src/test/java/org/apache/eagle/policy/dao/TestSchemaDao.java
---
@@ -0,0 +1,19 @@
+package org.apache.eagle.policy.dao;
+
+import org.apache.eagle.alert.entity.AlertStreamSchemaEntity;
+import org.junit.Test;
+
+import java.util.List;
+
+/**
+ * Created on 12/31/15.
+ */
+public class TestSchemaDao {
+
+@Test
+public void test() throws Exception {
+AlertStreamSchemaDAO dao = new
AlertStreamSchemaDAOImpl("eagle-c3-lvs01-1-9953.lvs01.dev.ebayc3.com", 9099,
"admin", "secret");
--- End diff --
Please clean sensitive info
---
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.
---
[GitHub] incubator-eagle pull request: EAGLE-79 Provide basic aggregation
Github user haoch commented on a diff in the pull request:
https://github.com/apache/incubator-eagle/pull/52#discussion_r48809070
--- Diff: eagle-samples/eagle-persist-sample/pom.xml ---
@@ -0,0 +1,43 @@
+
+
+http://maven.apache.org/POM/4.0.0";
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
+ xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
+
+eagle-samples
+eagle
+0.3.0
+
+4.0.0
+
+eagle-persist-sample
+
+
+eagle
+eagle-stream-process-api
+${project.version}
+
+
+eagle
+eagle-query-base
+0.3.0
--- End diff --
Please use ${project.version} to specify module version if not have to.
---
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-79) Provide analytic DSL support
[
https://issues.apache.org/jira/browse/EAGLE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15082294#comment-15082294
]
ASF GitHub Bot commented on EAGLE-79:
-
Github user haoch commented on a diff in the pull request:
https://github.com/apache/incubator-eagle/pull/52#discussion_r48809042
--- Diff:
eagle-core/eagle-policy/eagle-policy-base/src/test/java/org/apache/eagle/policy/dao/TestSchemaDao.java
---
@@ -0,0 +1,19 @@
+package org.apache.eagle.policy.dao;
+
+import org.apache.eagle.alert.entity.AlertStreamSchemaEntity;
+import org.junit.Test;
+
+import java.util.List;
+
+/**
+ * Created on 12/31/15.
+ */
+public class TestSchemaDao {
+
+@Test
+public void test() throws Exception {
+AlertStreamSchemaDAO dao = new
AlertStreamSchemaDAOImpl("eagle-c3-lvs01-1-9953.lvs01.dev.ebayc3.com", 9099,
"admin", "secret");
--- End diff --
Please clean sensitive info
> Provide analytic DSL support
> -
>
> Key: EAGLE-79
> URL: https://issues.apache.org/jira/browse/EAGLE-79
> Project: Eagle
> Issue Type: New Feature
>Affects Versions: 0.3.0
>Reporter: Su Ralph
>Assignee: Su Ralph
> Fix For: 0.3.0
>
>
> Eagle input comes with stream data (like security audit log), eagle provide
> alerting computation based on CEP DSL.
> Similar to this process, eagle should be able to provide same DSL support to
> expose the real-time monitoring feature, and furthermore could be integrated
> with some storage backend to provide dashboard/presentation to user.
> This would require
> 1. eagle programming API to support a new semantic of query(or aggregation),
> using the similar alert DSL.
> 2. a clear definition of time series storage interface (so that different
> storage engine could be adopted), currently we might start from the eagle
> built-in hbase implementation
> 3. Metric API/Dashboard.
> Currently, it require a lot of user customization and CEP engine capability
> could not be reused.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (EAGLE-79) Provide analytic DSL support
[
https://issues.apache.org/jira/browse/EAGLE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15082295#comment-15082295
]
ASF GitHub Bot commented on EAGLE-79:
-
Github user haoch commented on a diff in the pull request:
https://github.com/apache/incubator-eagle/pull/52#discussion_r48809070
--- Diff: eagle-samples/eagle-persist-sample/pom.xml ---
@@ -0,0 +1,43 @@
+
+
+http://maven.apache.org/POM/4.0.0";
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
+ xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
+
+eagle-samples
+eagle
+0.3.0
+
+4.0.0
+
+eagle-persist-sample
+
+
+eagle
+eagle-stream-process-api
+${project.version}
+
+
+eagle
+eagle-query-base
+0.3.0
--- End diff --
Please use ${project.version} to specify module version if not have to.
> Provide analytic DSL support
> -
>
> Key: EAGLE-79
> URL: https://issues.apache.org/jira/browse/EAGLE-79
> Project: Eagle
> Issue Type: New Feature
>Affects Versions: 0.3.0
>Reporter: Su Ralph
>Assignee: Su Ralph
> Fix For: 0.3.0
>
>
> Eagle input comes with stream data (like security audit log), eagle provide
> alerting computation based on CEP DSL.
> Similar to this process, eagle should be able to provide same DSL support to
> expose the real-time monitoring feature, and furthermore could be integrated
> with some storage backend to provide dashboard/presentation to user.
> This would require
> 1. eagle programming API to support a new semantic of query(or aggregation),
> using the similar alert DSL.
> 2. a clear definition of time series storage interface (so that different
> storage engine could be adopted), currently we might start from the eagle
> built-in hbase implementation
> 3. Metric API/Dashboard.
> Currently, it require a lot of user customization and CEP engine capability
> could not be reused.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] incubator-eagle pull request: EAGLE-79 Provide basic aggregation
Github user haoch commented on the pull request: https://github.com/apache/incubator-eagle/pull/52#issuecomment-168880882 Have you implemented the inline sql-based-policy interface? --- 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-79) Provide analytic DSL support
[ https://issues.apache.org/jira/browse/EAGLE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15082297#comment-15082297 ] ASF GitHub Bot commented on EAGLE-79: - Github user haoch commented on the pull request: https://github.com/apache/incubator-eagle/pull/52#issuecomment-168880882 Have you implemented the inline sql-based-policy interface? > Provide analytic DSL support > - > > Key: EAGLE-79 > URL: https://issues.apache.org/jira/browse/EAGLE-79 > Project: Eagle > Issue Type: New Feature >Affects Versions: 0.3.0 >Reporter: Su Ralph >Assignee: Su Ralph > Fix For: 0.3.0 > > > Eagle input comes with stream data (like security audit log), eagle provide > alerting computation based on CEP DSL. > Similar to this process, eagle should be able to provide same DSL support to > expose the real-time monitoring feature, and furthermore could be integrated > with some storage backend to provide dashboard/presentation to user. > This would require > 1. eagle programming API to support a new semantic of query(or aggregation), > using the similar alert DSL. > 2. a clear definition of time series storage interface (so that different > storage engine could be adopted), currently we might start from the eagle > built-in hbase implementation > 3. Metric API/Dashboard. > Currently, it require a lot of user customization and CEP engine capability > could not be reused. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [DISCUSS] - Adding RAT check to build for Apache lincese header check
Thanks! I guess we have enough consensus to add rat check by default. I will keep the current PR as is. We can discuss the details of the followup issue of about webapp files on the Jira ticket. We can close this thread. I would appreciate if somebody can take a look at PR #51 [3] thanks Prasad [3] - https://github.com/apache/incubator-eagle/pull/51 On Mon, Jan 4, 2016 at 6:41 PM, Chen, Hao wrote: > I think it’s a good suggestion, please move ahead to enable it by default > and fix the missing license headers. > > Thanks, > Hao > > > > On 1/5/16, 5:58 AM, "Don Bosco Durai" wrote: > > >I agree, it is better if it is enabled by default. At least in Ranger we > have seen builds failing and we scrambling to fix the build. > > > >Bosco > > > > > > > > > >On 1/2/16, 11:51 PM, "Prasad Mujumdar" wrote: > > > >>Hey Hao, > >> > >> Thanks for clarifying that. > >> > >>When it's forced in the build, the owners is on every developer to ensure > >>that the new files have the correct license header. They can fix any > >>missing files locally (or add an exception when applicable). Keeping this > >>in CI or release build makes the process longer and requires more > iteration > >>for each patch/release. > >>Let me know if it's still preferred in CI. The header updates in the PR > are > >>still needed. > >> > >>thanks > >>Prasad > >> > >> > >>On Sat, Jan 2, 2016 at 10:36 PM, Hao Chen wrote: > >> > >>> Hi Prasad, > >>> > >>> Thanks for it. We declared RAT in pom plugin management and enable by > >>> command arguments when necessary but not forcefully, which would be > added > >>> in CI. > >>> > >>> Thanks, > >>> Hao > >>> > >>> > On Jan 3, 2016, at 12:01 PM, Prasad Mujumdar > >>> wrote: > >>> > > >>> > Hello Hao, > >>> > > >>> > There's RAT plugin defined under plugin management, however it's > not > >>> > enabled. Also there are a number of files that are missing the > license > >>> > header. I just submitted the PR #51 [2] that adds license header to > 26 > >>> > files, plus the ones under webapp still needs to be handled. > >>> > > >>> > thanks > >>> > Prasad > >>> > > >>> > [2] - https://github.com/apache/incubator-eagle/pull/51 > >>> > > >>> >> On Sat, Jan 2, 2016 at 7:18 PM, Hao Chen > wrote: > >>> >> > >>> >> RAT has already been enabled in the pom when open source. > >>> >> > >>> On Jan 3, 2016, at 6:30 AM, Edward Zhang > > >>> >>> wrote: > >>> >>> > >>> >>> Good point to have tools to identify missing license header, we > should > >>> >> have > >>> >>> that. > >>> >>> > >>> >>> In terms of license headers under eagle-webservice, I remembered > there > >>> >> was > >>> >>> some discussion on the license of those files, probably Jilin can > >>> provide > >>> >>> more details. > >>> >>> > >>> >>> Thanks > >>> >>> > >>> >>> Edward > >>> >>> > >>> On Sat, Jan 2, 2016 at 1:25 PM, Prasad Mujumdar < > pras...@apache.org> > >>> >> wrote: > >>> > >>> Hi, > >>> > >>> Looks like we have a bunch of files that are missing the Apache > >>> >> license > >>> headers. IMO it's a good idea to add the Maven RAT plugin to > ensure > >>> that > >>> every new file has license header. Otherwise the responsibility > falls > >>> on > >>> the release manager's head to correct it and makes the release > process > >>> longer and tedious. > >>> I have logged a ticket EAGLE-114 [1] to track it and got a working > >>> patch > >>> that I can submit a PR. One of the problem fileset is the webapp > under > >>> eagle-webservice. There are a large number of files which don't > have > >>> license header. I would like to create a separate ticket to track > >>> which > >>> files should have the header and which should be excluded. > >>> > >>> Let me know if that sounds reasonable. > >>> > >>> thanks > >>> Prasad > >>> > >>> [1] - https://issues.apache.org/jira/browse/EAGLE-114 > >>> >> > >>> > > >
[jira] [Commented] (EAGLE-83) Integrate Jenkins with GitHub for checking pull requests
[ https://issues.apache.org/jira/browse/EAGLE-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15082319#comment-15082319 ] Michael Wu commented on EAGLE-83: - open a jira ticket for Infrastructure team: INFRA-11026 now is trying to write commands as a workaround. > Integrate Jenkins with GitHub for checking pull requests > > > Key: EAGLE-83 > URL: https://issues.apache.org/jira/browse/EAGLE-83 > Project: Eagle > Issue Type: Task >Reporter: Michael Wu >Assignee: Michael Wu > Labels: test > Original Estimate: 168h > Remaining Estimate: 168h > > We expect that when a pull request comes up, a Jenkins job is triggered to > verify the quality of new updates relevant to the PR, and automatically > provide advices for whether it should be applied, with the verification > result posted to github PR page for reference. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: January 2016 Report
Signed off!
On Tue, Jan 5, 2016 at 12:18 AM, arunkarthick m
wrote:
> Thanks folks.
>
> I have updated the content based on the feedback.
>
> On Mon, Jan 4, 2016 at 10:14 AM, Prasad Mujumdar
> wrote:
>
> >+1 to the nice summary!
> >
> > Perhaps the details under those sections, like new contributors and
> release
> > plan etc can be moved under "How has the community developed" section ?
> >
> > thanks
> > Prasad
> >
> >
> > On Mon, Jan 4, 2016 at 12:49 AM, amareshwarisr .
> > wrote:
> >
> > > Hi,
> > >
> > > I see the report for Eagle has been updated on wiki -
> > > http://wiki.apache.org/incubator/January2016.
> > >
> > > Nicely summarised report!
> > >
> > > Have a couple of comments :
> > >
> > >- Following sentence is incomplete :
> > >
> > > 1. We have submitted papers and applied to conferences. We worked
> > > with other open source projects like
> > >
> > >
> > >- For Date of last release and When were last committers added - you
> > can
> > >put it as NONE.
> > >
> > > Thanks
> > > Amareshwari
> > >
> > > On Thu, Dec 31, 2015 at 3:30 AM, Marvin Humphrey
> > > wrote:
> > >
> > > > Greetings, {podling} developers!
> > > >
> > > > This is a reminder that your report is due next Wednesday, January
> > > > 6th. Details below.
> > > >
> > > > Best,
> > > >
> > > > Marvin Humphrey, Report Manager for January, on behalf of the
> > > > Incubator PMC
> > > >
> > > > ---
> > > >
> > > > Dear podling,
> > > >
> > > > This email was sent by an automated system on behalf of the Apache
> > > > Incubator PMC. It is an initial reminder to give you plenty of time
> to
> > > > prepare your quarterly board report.
> > > >
> > > > The board meeting is scheduled for Wed, 20 January 2016, 10:30 am
> PDT.
> > > > The report for your podling will form a part of the Incubator PMC
> > > > report. The Incubator PMC requires your report to be submitted 2
> weeks
> > > > before the board meeting, to allow sufficient time for review and
> > > > submission (Wed, January 6th).
> > > >
> > > > Please submit your report with sufficient time to allow the Incubator
> > > > PMC, and subsequently board members to review and digest. Again, the
> > > > very latest you should submit your report is 2 weeks prior to the
> board
> > > > meeting.
> > > >
> > > > Thanks,
> > > >
> > > > The Apache Incubator PMC
> > > >
> > > > Submitting your Report
> > > >
> > > > --
> > > >
> > > > Your report should contain the following:
> > > >
> > > > * Your project name
> > > > * A brief description of your project, which assumes no knowledge
> of
> > > > the project or necessarily of its field
> > > > * A list of the three most important issues to address in the move
> > > > towards graduation.
> > > > * Any issues that the Incubator PMC or ASF Board might wish/need to
> > be
> > > > aware of
> > > > * How has the community developed since the last report
> > > > * How has the project developed since the last report.
> > > >
> > > > This should be appended to the Incubator Wiki page at:
> > > >
> > > > http://wiki.apache.org/incubator/January2016
> > > >
> > > > Note: This is manually populated. You may need to wait a little
> before
> > > > this page is created from a template.
> > > >
> > > > Mentors
> > > > ---
> > > >
> > > > Mentors should review reports for their project(s) and sign them off
> on
> > > > the Incubator wiki page. Signing off reports shows that you are
> > > > following the project - projects that are not signed may raise alarms
> > > > for the Incubator PMC.
> > > >
> > > > Incubator PMC
> > > >
> > > >
> > >
> >
>
>
>
> --
> Arun Karthick
> 201-850-9399
>
[GitHub] incubator-eagle pull request: EAGLE-114: Enable RAT check and fix ...
Github user haoch commented on a diff in the pull request: https://github.com/apache/incubator-eagle/pull/51#discussion_r48813408 --- Diff: eagle-assembly/src/main/README.md --- @@ -1,3 +1,18 @@ +# Licensed to the Apache Software Foundation (ASF) under one or more --- End diff -- In markdown files, the license headers should be added as ~~~ ~~~ --- 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-114) Enable RAT check and fix missing license headers
[ https://issues.apache.org/jira/browse/EAGLE-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15082406#comment-15082406 ] ASF GitHub Bot commented on EAGLE-114: -- Github user haoch commented on a diff in the pull request: https://github.com/apache/incubator-eagle/pull/51#discussion_r48813408 --- Diff: eagle-assembly/src/main/README.md --- @@ -1,3 +1,18 @@ +# Licensed to the Apache Software Foundation (ASF) under one or more --- End diff -- In markdown files, the license headers should be added as ~~~ ~~~ > Enable RAT check and fix missing license headers > > > Key: EAGLE-114 > URL: https://issues.apache.org/jira/browse/EAGLE-114 > Project: Eagle > Issue Type: Improvement >Affects Versions: 0.3.0 >Reporter: Prasad Mujumdar > > Enable maven rat check plugin to ensue that the source code has Apache > license header. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-114) Enable RAT check and fix missing license headers
[ https://issues.apache.org/jira/browse/EAGLE-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15082407#comment-15082407 ] ASF GitHub Bot commented on EAGLE-114: -- Github user haoch commented on the pull request: https://github.com/apache/incubator-eagle/pull/51#issuecomment-168902045 Everything seems good except the license header for markdown files. > Enable RAT check and fix missing license headers > > > Key: EAGLE-114 > URL: https://issues.apache.org/jira/browse/EAGLE-114 > Project: Eagle > Issue Type: Improvement >Affects Versions: 0.3.0 >Reporter: Prasad Mujumdar > > Enable maven rat check plugin to ensue that the source code has Apache > license header. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request: EAGLE-114: Enable RAT check and fix ...
Github user haoch commented on the pull request: https://github.com/apache/incubator-eagle/pull/51#issuecomment-168902045 Everything seems good except the license header for markdown files. --- 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. ---
[GitHub] incubator-eagle pull request: Should support sum aggregation in fr...
GitHub user zombieJ opened a pull request: https://github.com/apache/incubator-eagle/pull/53 Should support sum aggregation in front end for slide window function Also In front end, we should able to rename the aggregation value with a meaning name, so the downstream components like alert notification part could display more meaning full information You can merge this pull request into a Git repository by running: $ git pull https://github.com/zombieJ/incubator-eagle sumAgg Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/53.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #53 commit 2bc8e5ef17ae8ccf2808d42699db4a9bf132ead7 Author: jiljiang Date: 2016-01-05T05:31:02Z add sum of agg --- 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-112) Should support sum aggregation in front end for slide window function
[ https://issues.apache.org/jira/browse/EAGLE-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15082417#comment-15082417 ] ASF GitHub Bot commented on EAGLE-112: -- Github user haoch commented on the pull request: https://github.com/apache/incubator-eagle/pull/53#issuecomment-168904362 LGTM > Should support sum aggregation in front end for slide window function > - > > Key: EAGLE-112 > URL: https://issues.apache.org/jira/browse/EAGLE-112 > Project: Eagle > Issue Type: Improvement >Reporter: Libin, Sun >Assignee: Jilin, Jiang >Priority: Blocker > > In GC monitoring user case, > [EAGLE-97|https://issues.apache.org/jira/browse/EAGLE-97], we need to > calculate total GC paused time in a fixed interval, thus need create policy > with sum aggregation in front end -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request: EAGLE-112 Should support sum aggrega...
Github user haoch commented on the pull request: https://github.com/apache/incubator-eagle/pull/53#issuecomment-168904362 LGTM --- 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. ---
[GitHub] incubator-eagle pull request: EAGLE-114: Enable RAT check and fix ...
Github user pmujumdar commented on a diff in the pull request: https://github.com/apache/incubator-eagle/pull/51#discussion_r48814118 --- Diff: eagle-assembly/src/main/README.md --- @@ -1,3 +1,18 @@ +# Licensed to the Apache Software Foundation (ASF) under one or more --- End diff -- Thanks for catching that. I was not familiar with Markdown syntax. will update the patch shortly. --- 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-114) Enable RAT check and fix missing license headers
[ https://issues.apache.org/jira/browse/EAGLE-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15082426#comment-15082426 ] ASF GitHub Bot commented on EAGLE-114: -- Github user pmujumdar commented on a diff in the pull request: https://github.com/apache/incubator-eagle/pull/51#discussion_r48814118 --- Diff: eagle-assembly/src/main/README.md --- @@ -1,3 +1,18 @@ +# Licensed to the Apache Software Foundation (ASF) under one or more --- End diff -- Thanks for catching that. I was not familiar with Markdown syntax. will update the patch shortly. > Enable RAT check and fix missing license headers > > > Key: EAGLE-114 > URL: https://issues.apache.org/jira/browse/EAGLE-114 > Project: Eagle > Issue Type: Improvement >Affects Versions: 0.3.0 >Reporter: Prasad Mujumdar > > Enable maven rat check plugin to ensue that the source code has Apache > license header. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request: EAGLE-79 Provide basic aggregation
Github user RalphSu commented on a diff in the pull request:
https://github.com/apache/incubator-eagle/pull/52#discussion_r48814263
--- Diff:
eagle-core/eagle-data-process/eagle-stream-process-api/src/main/java/org/apache/eagle/dataproc/impl/persist/druid/DruidPersistService.java
---
@@ -0,0 +1,119 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ *http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.eagle.dataproc.impl.persist.druid;
+
+import com.typesafe.config.Config;
+import com.typesafe.config.ConfigValue;
+import org.apache.eagle.dataproc.impl.aggregate.entity.AggregateEntity;
+import org.apache.eagle.dataproc.impl.persist.IPersistService;
+import org.apache.kafka.clients.producer.KafkaProducer;
+import org.apache.kafka.clients.producer.ProducerRecord;
+import org.apache.kafka.clients.producer.RecordMetadata;
+
+import java.util.*;
+import java.util.concurrent.Future;
+
+/**
+ * TODO : support more general entity input
+ * @since Dec 21, 2015
+ *
+ */
+public class DruidPersistService implements
IPersistService {
--- End diff --
Nice suggestion, kafakpersistservice seems better.
---
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-79) Provide analytic DSL support
[
https://issues.apache.org/jira/browse/EAGLE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15082431#comment-15082431
]
ASF GitHub Bot commented on EAGLE-79:
-
Github user RalphSu commented on a diff in the pull request:
https://github.com/apache/incubator-eagle/pull/52#discussion_r48814263
--- Diff:
eagle-core/eagle-data-process/eagle-stream-process-api/src/main/java/org/apache/eagle/dataproc/impl/persist/druid/DruidPersistService.java
---
@@ -0,0 +1,119 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ *http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.eagle.dataproc.impl.persist.druid;
+
+import com.typesafe.config.Config;
+import com.typesafe.config.ConfigValue;
+import org.apache.eagle.dataproc.impl.aggregate.entity.AggregateEntity;
+import org.apache.eagle.dataproc.impl.persist.IPersistService;
+import org.apache.kafka.clients.producer.KafkaProducer;
+import org.apache.kafka.clients.producer.ProducerRecord;
+import org.apache.kafka.clients.producer.RecordMetadata;
+
+import java.util.*;
+import java.util.concurrent.Future;
+
+/**
+ * TODO : support more general entity input
+ * @since Dec 21, 2015
+ *
+ */
+public class DruidPersistService implements
IPersistService {
--- End diff --
Nice suggestion, kafakpersistservice seems better.
> Provide analytic DSL support
> -
>
> Key: EAGLE-79
> URL: https://issues.apache.org/jira/browse/EAGLE-79
> Project: Eagle
> Issue Type: New Feature
>Affects Versions: 0.3.0
>Reporter: Su Ralph
>Assignee: Su Ralph
> Fix For: 0.3.0
>
>
> Eagle input comes with stream data (like security audit log), eagle provide
> alerting computation based on CEP DSL.
> Similar to this process, eagle should be able to provide same DSL support to
> expose the real-time monitoring feature, and furthermore could be integrated
> with some storage backend to provide dashboard/presentation to user.
> This would require
> 1. eagle programming API to support a new semantic of query(or aggregation),
> using the similar alert DSL.
> 2. a clear definition of time series storage interface (so that different
> storage engine could be adopted), currently we might start from the eagle
> built-in hbase implementation
> 3. Metric API/Dashboard.
> Currently, it require a lot of user customization and CEP engine capability
> could not be reused.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] incubator-eagle pull request: EAGLE-79 Provide basic aggregation
Github user RalphSu commented on a diff in the pull request:
https://github.com/apache/incubator-eagle/pull/52#discussion_r48814299
--- Diff:
eagle-core/eagle-policy/eagle-policy-base/src/test/java/org/apache/eagle/policy/dao/TestSchemaDao.java
---
@@ -0,0 +1,19 @@
+package org.apache.eagle.policy.dao;
+
+import org.apache.eagle.alert.entity.AlertStreamSchemaEntity;
+import org.junit.Test;
+
+import java.util.List;
+
+/**
+ * Created on 12/31/15.
+ */
+public class TestSchemaDao {
+
+@Test
+public void test() throws Exception {
+AlertStreamSchemaDAO dao = new
AlertStreamSchemaDAOImpl("eagle-c3-lvs01-1-9953.lvs01.dev.ebayc3.com", 9099,
"admin", "secret");
--- End diff --
Removed
---
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.
---
[GitHub] incubator-eagle pull request: EAGLE-79 Provide basic aggregation
Github user RalphSu commented on a diff in the pull request: https://github.com/apache/incubator-eagle/pull/52#discussion_r48814294 --- Diff: eagle-core/eagle-policy/eagle-policy-base/pom.xml --- @@ -0,0 +1,62 @@ + --- End diff -- hm... what does this for? --- 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. ---
[GitHub] incubator-eagle pull request: EAGLE-79 Provide basic aggregation
Github user RalphSu commented on a diff in the pull request:
https://github.com/apache/incubator-eagle/pull/52#discussion_r48814318
--- Diff: eagle-samples/eagle-persist-sample/pom.xml ---
@@ -0,0 +1,43 @@
+
+
+http://maven.apache.org/POM/4.0.0";
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
+ xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
+
+eagle-samples
+eagle
+0.3.0
+
+4.0.0
+
+eagle-persist-sample
+
+
+eagle
+eagle-stream-process-api
+${project.version}
+
+
+eagle
+eagle-query-base
+0.3.0
--- End diff --
Missed ide generation, fixed.
---
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-79) Provide analytic DSL support
[
https://issues.apache.org/jira/browse/EAGLE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15082434#comment-15082434
]
ASF GitHub Bot commented on EAGLE-79:
-
Github user RalphSu commented on a diff in the pull request:
https://github.com/apache/incubator-eagle/pull/52#discussion_r48814318
--- Diff: eagle-samples/eagle-persist-sample/pom.xml ---
@@ -0,0 +1,43 @@
+
+
+http://maven.apache.org/POM/4.0.0";
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
+ xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
+
+eagle-samples
+eagle
+0.3.0
+
+4.0.0
+
+eagle-persist-sample
+
+
+eagle
+eagle-stream-process-api
+${project.version}
+
+
+eagle
+eagle-query-base
+0.3.0
--- End diff --
Missed ide generation, fixed.
> Provide analytic DSL support
> -
>
> Key: EAGLE-79
> URL: https://issues.apache.org/jira/browse/EAGLE-79
> Project: Eagle
> Issue Type: New Feature
>Affects Versions: 0.3.0
>Reporter: Su Ralph
>Assignee: Su Ralph
> Fix For: 0.3.0
>
>
> Eagle input comes with stream data (like security audit log), eagle provide
> alerting computation based on CEP DSL.
> Similar to this process, eagle should be able to provide same DSL support to
> expose the real-time monitoring feature, and furthermore could be integrated
> with some storage backend to provide dashboard/presentation to user.
> This would require
> 1. eagle programming API to support a new semantic of query(or aggregation),
> using the similar alert DSL.
> 2. a clear definition of time series storage interface (so that different
> storage engine could be adopted), currently we might start from the eagle
> built-in hbase implementation
> 3. Metric API/Dashboard.
> Currently, it require a lot of user customization and CEP engine capability
> could not be reused.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (EAGLE-79) Provide analytic DSL support
[
https://issues.apache.org/jira/browse/EAGLE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15082433#comment-15082433
]
ASF GitHub Bot commented on EAGLE-79:
-
Github user RalphSu commented on a diff in the pull request:
https://github.com/apache/incubator-eagle/pull/52#discussion_r48814299
--- Diff:
eagle-core/eagle-policy/eagle-policy-base/src/test/java/org/apache/eagle/policy/dao/TestSchemaDao.java
---
@@ -0,0 +1,19 @@
+package org.apache.eagle.policy.dao;
+
+import org.apache.eagle.alert.entity.AlertStreamSchemaEntity;
+import org.junit.Test;
+
+import java.util.List;
+
+/**
+ * Created on 12/31/15.
+ */
+public class TestSchemaDao {
+
+@Test
+public void test() throws Exception {
+AlertStreamSchemaDAO dao = new
AlertStreamSchemaDAOImpl("eagle-c3-lvs01-1-9953.lvs01.dev.ebayc3.com", 9099,
"admin", "secret");
--- End diff --
Removed
> Provide analytic DSL support
> -
>
> Key: EAGLE-79
> URL: https://issues.apache.org/jira/browse/EAGLE-79
> Project: Eagle
> Issue Type: New Feature
>Affects Versions: 0.3.0
>Reporter: Su Ralph
>Assignee: Su Ralph
> Fix For: 0.3.0
>
>
> Eagle input comes with stream data (like security audit log), eagle provide
> alerting computation based on CEP DSL.
> Similar to this process, eagle should be able to provide same DSL support to
> expose the real-time monitoring feature, and furthermore could be integrated
> with some storage backend to provide dashboard/presentation to user.
> This would require
> 1. eagle programming API to support a new semantic of query(or aggregation),
> using the similar alert DSL.
> 2. a clear definition of time series storage interface (so that different
> storage engine could be adopted), currently we might start from the eagle
> built-in hbase implementation
> 3. Metric API/Dashboard.
> Currently, it require a lot of user customization and CEP engine capability
> could not be reused.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (EAGLE-79) Provide analytic DSL support
[ https://issues.apache.org/jira/browse/EAGLE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15082432#comment-15082432 ] ASF GitHub Bot commented on EAGLE-79: - Github user RalphSu commented on a diff in the pull request: https://github.com/apache/incubator-eagle/pull/52#discussion_r48814294 --- Diff: eagle-core/eagle-policy/eagle-policy-base/pom.xml --- @@ -0,0 +1,62 @@ + --- End diff -- hm... what does this for? > Provide analytic DSL support > - > > Key: EAGLE-79 > URL: https://issues.apache.org/jira/browse/EAGLE-79 > Project: Eagle > Issue Type: New Feature >Affects Versions: 0.3.0 >Reporter: Su Ralph >Assignee: Su Ralph > Fix For: 0.3.0 > > > Eagle input comes with stream data (like security audit log), eagle provide > alerting computation based on CEP DSL. > Similar to this process, eagle should be able to provide same DSL support to > expose the real-time monitoring feature, and furthermore could be integrated > with some storage backend to provide dashboard/presentation to user. > This would require > 1. eagle programming API to support a new semantic of query(or aggregation), > using the similar alert DSL. > 2. a clear definition of time series storage interface (so that different > storage engine could be adopted), currently we might start from the eagle > built-in hbase implementation > 3. Metric API/Dashboard. > Currently, it require a lot of user customization and CEP engine capability > could not be reused. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request: EAGLE-79 Provide basic aggregation
Github user RalphSu commented on the pull request: https://github.com/apache/incubator-eagle/pull/52#issuecomment-168906286 For sql-based-policy, i think it mean an policy executor accept a fixed sql. This would be added later, not in this commit. --- 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-79) Provide analytic DSL support
[ https://issues.apache.org/jira/browse/EAGLE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15082435#comment-15082435 ] ASF GitHub Bot commented on EAGLE-79: - Github user RalphSu commented on the pull request: https://github.com/apache/incubator-eagle/pull/52#issuecomment-168906286 For sql-based-policy, i think it mean an policy executor accept a fixed sql. This would be added later, not in this commit. > Provide analytic DSL support > - > > Key: EAGLE-79 > URL: https://issues.apache.org/jira/browse/EAGLE-79 > Project: Eagle > Issue Type: New Feature >Affects Versions: 0.3.0 >Reporter: Su Ralph >Assignee: Su Ralph > Fix For: 0.3.0 > > > Eagle input comes with stream data (like security audit log), eagle provide > alerting computation based on CEP DSL. > Similar to this process, eagle should be able to provide same DSL support to > expose the real-time monitoring feature, and furthermore could be integrated > with some storage backend to provide dashboard/presentation to user. > This would require > 1. eagle programming API to support a new semantic of query(or aggregation), > using the similar alert DSL. > 2. a clear definition of time series storage interface (so that different > storage engine could be adopted), currently we might start from the eagle > built-in hbase implementation > 3. Metric API/Dashboard. > Currently, it require a lot of user customization and CEP engine capability > could not be reused. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request: EAGLE-79 Provide basic aggregation
Github user haoch commented on a diff in the pull request: https://github.com/apache/incubator-eagle/pull/52#discussion_r48814463 --- Diff: eagle-core/eagle-policy/eagle-policy-base/pom.xml --- @@ -0,0 +1,62 @@ + --- End diff -- Never mind, I mistake something. :-) --- 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-79) Provide analytic DSL support
[ https://issues.apache.org/jira/browse/EAGLE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15082438#comment-15082438 ] ASF GitHub Bot commented on EAGLE-79: - Github user haoch commented on a diff in the pull request: https://github.com/apache/incubator-eagle/pull/52#discussion_r48814463 --- Diff: eagle-core/eagle-policy/eagle-policy-base/pom.xml --- @@ -0,0 +1,62 @@ + --- End diff -- Never mind, I mistake something. :-) > Provide analytic DSL support > - > > Key: EAGLE-79 > URL: https://issues.apache.org/jira/browse/EAGLE-79 > Project: Eagle > Issue Type: New Feature >Affects Versions: 0.3.0 >Reporter: Su Ralph >Assignee: Su Ralph > Fix For: 0.3.0 > > > Eagle input comes with stream data (like security audit log), eagle provide > alerting computation based on CEP DSL. > Similar to this process, eagle should be able to provide same DSL support to > expose the real-time monitoring feature, and furthermore could be integrated > with some storage backend to provide dashboard/presentation to user. > This would require > 1. eagle programming API to support a new semantic of query(or aggregation), > using the similar alert DSL. > 2. a clear definition of time series storage interface (so that different > storage engine could be adopted), currently we might start from the eagle > built-in hbase implementation > 3. Metric API/Dashboard. > Currently, it require a lot of user customization and CEP engine capability > could not be reused. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request: EAGLE-79 Provide basic aggregation
Github user haoch commented on the pull request: https://github.com/apache/incubator-eagle/pull/52#issuecomment-168906723 Ok, i think the pull request is good for me. --- 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-79) Provide analytic DSL support
[ https://issues.apache.org/jira/browse/EAGLE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15082441#comment-15082441 ] ASF GitHub Bot commented on EAGLE-79: - Github user haoch commented on the pull request: https://github.com/apache/incubator-eagle/pull/52#issuecomment-168906723 Ok, i think the pull request is good for me. > Provide analytic DSL support > - > > Key: EAGLE-79 > URL: https://issues.apache.org/jira/browse/EAGLE-79 > Project: Eagle > Issue Type: New Feature >Affects Versions: 0.3.0 >Reporter: Su Ralph >Assignee: Su Ralph > Fix For: 0.3.0 > > > Eagle input comes with stream data (like security audit log), eagle provide > alerting computation based on CEP DSL. > Similar to this process, eagle should be able to provide same DSL support to > expose the real-time monitoring feature, and furthermore could be integrated > with some storage backend to provide dashboard/presentation to user. > This would require > 1. eagle programming API to support a new semantic of query(or aggregation), > using the similar alert DSL. > 2. a clear definition of time series storage interface (so that different > storage engine could be adopted), currently we might start from the eagle > built-in hbase implementation > 3. Metric API/Dashboard. > Currently, it require a lot of user customization and CEP engine capability > could not be reused. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request: EAGLE-114: Enable RAT check and fix ...
Github user haoch commented on a diff in the pull request: https://github.com/apache/incubator-eagle/pull/51#discussion_r48815577 --- Diff: eagle-assembly/src/main/docs/logstash-kafka-conf.md --- @@ -1,3 +1,18 @@ +# Licensed to the Apache Software Foundation (ASF) under one or more --- End diff -- ~~~ ~~~ --- 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-114) Enable RAT check and fix missing license headers
[ https://issues.apache.org/jira/browse/EAGLE-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15082481#comment-15082481 ] ASF GitHub Bot commented on EAGLE-114: -- Github user haoch commented on a diff in the pull request: https://github.com/apache/incubator-eagle/pull/51#discussion_r48815577 --- Diff: eagle-assembly/src/main/docs/logstash-kafka-conf.md --- @@ -1,3 +1,18 @@ +# Licensed to the Apache Software Foundation (ASF) under one or more --- End diff -- ~~~ ~~~ > Enable RAT check and fix missing license headers > > > Key: EAGLE-114 > URL: https://issues.apache.org/jira/browse/EAGLE-114 > Project: Eagle > Issue Type: Improvement >Affects Versions: 0.3.0 >Reporter: Prasad Mujumdar > > Enable maven rat check plugin to ensue that the source code has Apache > license header. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request: EAGLE-114: Enable RAT check and fix ...
Github user pmujumdar commented on a diff in the pull request: https://github.com/apache/incubator-eagle/pull/51#discussion_r48815750 --- Diff: eagle-assembly/src/main/docs/logstash-kafka-conf.md --- @@ -1,3 +1,18 @@ +# Licensed to the Apache Software Foundation (ASF) under one or more --- End diff -- My bad, didn't push the other two files. sorry about that. just updated the 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 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-114) Enable RAT check and fix missing license headers
[ https://issues.apache.org/jira/browse/EAGLE-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15082488#comment-15082488 ] ASF GitHub Bot commented on EAGLE-114: -- Github user pmujumdar commented on a diff in the pull request: https://github.com/apache/incubator-eagle/pull/51#discussion_r48815750 --- Diff: eagle-assembly/src/main/docs/logstash-kafka-conf.md --- @@ -1,3 +1,18 @@ +# Licensed to the Apache Software Foundation (ASF) under one or more --- End diff -- My bad, didn't push the other two files. sorry about that. just updated the PR > Enable RAT check and fix missing license headers > > > Key: EAGLE-114 > URL: https://issues.apache.org/jira/browse/EAGLE-114 > Project: Eagle > Issue Type: Improvement >Affects Versions: 0.3.0 >Reporter: Prasad Mujumdar > > Enable maven rat check plugin to ensue that the source code has Apache > license header. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request: EAGLE-114: Enable RAT check and fix ...
Github user haoch commented on the pull request: https://github.com/apache/incubator-eagle/pull/51#issuecomment-168920973 The pull request looks good for me. Only problem is that the apache-rat plugin hands forever when I run `mvn apache-rat:check`. Could you please help investigate and fix it? --- 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-114) Enable RAT check and fix missing license headers
[ https://issues.apache.org/jira/browse/EAGLE-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15082552#comment-15082552 ] ASF GitHub Bot commented on EAGLE-114: -- Github user haoch commented on the pull request: https://github.com/apache/incubator-eagle/pull/51#issuecomment-168920973 The pull request looks good for me. Only problem is that the apache-rat plugin hands forever when I run `mvn apache-rat:check`. Could you please help investigate and fix it? > Enable RAT check and fix missing license headers > > > Key: EAGLE-114 > URL: https://issues.apache.org/jira/browse/EAGLE-114 > Project: Eagle > Issue Type: Improvement >Affects Versions: 0.3.0 >Reporter: Prasad Mujumdar > > Enable maven rat check plugin to ensue that the source code has Apache > license header. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-114) Enable RAT check and fix missing license headers
[ https://issues.apache.org/jira/browse/EAGLE-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15082573#comment-15082573 ] ASF GitHub Bot commented on EAGLE-114: -- Github user pmujumdar commented on the pull request: https://github.com/apache/incubator-eagle/pull/51#issuecomment-168923561 @haoch I alway used mvn verify which invokes the rat check > Enable RAT check and fix missing license headers > > > Key: EAGLE-114 > URL: https://issues.apache.org/jira/browse/EAGLE-114 > Project: Eagle > Issue Type: Improvement >Affects Versions: 0.3.0 >Reporter: Prasad Mujumdar > > Enable maven rat check plugin to ensue that the source code has Apache > license header. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request: EAGLE-114: Enable RAT check and fix ...
Github user pmujumdar commented on the pull request: https://github.com/apache/incubator-eagle/pull/51#issuecomment-168923561 @haoch I alway used mvn verify which invokes the rat check --- 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. ---
