[jira] [Commented] (EAGLE-251) Run eagle on flink/samza

[Edward Zhang (JIRA)]

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

Edward Zhang commented on EAGLE-251:


[~milap.wadhwa] looks this jira ticket is pretty long and probably we need 
revisit the request for running eagle on flink/samza.

In current development branch, Eagle now evolves to have applications and alert 
engine separated. And application can be on top of apache storm, spark etc. and 
alert engine is designed to run on top of apache storm.

So when we look at this ticket, we need make sure what we are going to do, is 
that application's runtime or alert engine runtime.

> Run eagle on flink/samza
> 
>
> Key: EAGLE-251
> URL: https://issues.apache.org/jira/browse/EAGLE-251
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.3.0
>Reporter: Su Ralph
>Priority: Minor
>  Labels: new
>
> Eagle is running on storm. One might want to do some interesting port to 
> other stream framework like flink/samza.



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

Re: [Discuss] what will be the decent way to remove jars from source code for releases

[Julian Hyde]

Great - thanks!

On Thu, Jul 14, 2016 at 2:44 AM, Michael Wu  wrote:
> Hi Julian,
>
> Ticket EAGLE-377  has been
> created. We'll fix it in 0.5.0-incubating version. Thanks for your kindly
> reminding. Anything missed, please do let me know.
>
> Michael
>
> On Thu, Jul 14, 2016 at 11:21 AM, Julian Hyde  wrote:
>
>> I understand now. But I have to say, even though I have read the git
>> commit logs and JIRA cases it’s very difficult to figure out why this
>> particular solution was chosen. And asking users to download a patch from
>> github is still a hack, yes? If you agree it’s a hack, why didn’t anyone
>> think to log a JIRA case to clean up?
>>
>> Julian
>>
>> [1] https://issues.apache.org/jira/browse/EAGLE-365 <
>> https://issues.apache.org/jira/browse/EAGLE-365>
>> [2]
>> https://github.com/apache/incubator-eagle/commit/9cd75b188941bf476878a2210984546e4e257c7a
>> <
>> https://github.com/apache/incubator-eagle/commit/9cd75b188941bf476878a2210984546e4e257c7a
>> >
>> [3] http://eagle.incubator.apache.org/docs/quick-start.html <
>> http://eagle.incubator.apache.org/docs/quick-start.html>
>> [4] https://github.com/apache/incubator-eagle/pull/180 <
>> https://github.com/apache/incubator-eagle/pull/180>
>>
>>
>> > On Jul 13, 2016, at 7:41 PM, Michael Wu  wrote:
>> >
>> > Hi Henry,
>> >
>> > The solution is we removed the jars out of the project source code
>> folder,
>> > and will use a PR patch to hold the files for downloading, so that
>> > customers can succeed to build in this flow: download source code
>> tar-ball
>> > -> extract tar-ball -> apply the patch -> maven build.
>> >
>> > This approach has been documented on apache eagle quick-start guide page.
>> >
>> > Thanks.
>> > Michael
>> >
>> > On Thu, Jul 14, 2016 at 12:33 AM, Henry Saputra > >
>> > wrote:
>> >
>> >> So what was the solution for this? Could someone points to JIRA or
>> Github
>> >> PR to fix this?
>> >>
>> >> Thanks much!
>> >>
>> >> - Henry
>> >>
>> >> On Mon, Jul 11, 2016 at 1:30 AM, Julian Hyde  wrote:
>> >>
>> >>> Can someone explain why these jar files have to be checked into git?
>> >>> Many other jar (and other binary) files are retrieved from a maven
>> >>> repo when you build; why not these? You can use maven magic to
>> >>> extract/filter/copy these files exactly where you need them on the
>> >>> first build.
>> >>>
>> >>> Source files have a sacred role in open source because (a) they can be
>> >>> edited (a fundamental right granted by an open source license), (b)
>> >>> they can be audited during a release.
>> >>>
>> >>> And, leaving the open source issues aside and just looking at the
>> >>> software engineering, checking non-source files into a source-control
>> >>> system, and especially into git, is often a bad idea. For instance,
>> >>> projects hotly debate whether to check in java files generated by
>> >>> protobuf, because the .proto file is the "source", and the .java files
>> >>> are generated. Git doesn't handle binary files particularly well, and
>> >>> if the binary is modified a few times the git repo starts to become
>> >>> bloated in size.
>> >>>
>> >>> Julian
>> >>>
>> >>>
>> >>> On Sun, Jul 10, 2016 at 8:28 PM, Zhang, Edward (GDI Hadoop)
>> >>>  wrote:
>>  In 0.3 release, Hemanth uses a patch to work around this issue. Can we
>> >>> use the same approach in 0.4 and in 0.5 we have decided to remove
>> >>> dependency on tomcat.
>> 
>> 
>>  Thanks
>> 
>>  Edward
>> 
>>  
>>  From: Hao Chen 
>>  Sent: Sunday, July 10, 2016 8:17:48 PM
>>  To: dev@eagle.incubator.apache.org
>>  Subject: Re: [Discuss] what will be the decent way to remove jars from
>> >>> source code for releases
>> 
>>  Yes, the jars are added into the source package intentionally, which
>> is
>>  necessary for bootstrapping eagle service. So maybe it possible for us
>> >>> the
>>  keep the jars following apache way? Otherwise we may need some
>> >> additional
>>  work to refactoring our package method.
>> 
>>  - Hao
>> 
>>  On Mon, Jul 11, 2016 at 11:07 AM, Michael Wu 
>> >> wrote:
>> 
>> > Hi guys,
>> >
>> > Further tested and verified, the 3 jar dependencies are NECESSARY for
>> >>> the
>> > eagle-service to start up. Without them, we can build the project but
>> >>> when
>> > we deploy it, eagle-service fails to start up complaining the lack of
>> >>> the
>> > dependencies. So, we cannot simply remove them before packaging the
>> >>> source
>> > tar ball.
>> >
>> > @PPMC, so far, we can tell that the 3 remaining jars are intended to
>> >> be
>> > there for the project's normal functionalities, they are important
>> and
>> > cannot be removed, can we just vote them as passed, 

[GitHub] incubator-eagle pull request #267: Eagle 376 skip false failing hbase relate...

[anyway1021]

GitHub user anyway1021 opened a pull request:

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

Eagle 376 skip false failing hbase related UT code

These faulty UT cases constantly failed because the embeded hbase 
environment cannot be started up properly, thus they have produced many false 
failures for long and wasted a lot of building time. Now skip them to so that 
the normal UT cases can expose true issues if there is any.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/anyway1021/incubator-eagle EAGLE-376

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/267.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 #267


commit 10cc46395a1b98e798ea6704a03ae9c938800335
Author: anyway1021 
Date:   2016-07-14T08:02:20Z

skip hbase related UT in sub-module: eagle-embed-hbase, to avoid false 
failures

commit de884c9480c606533c14843ae2afff040fdccdb2
Author: anyway1021 
Date:   2016-07-14T08:56:17Z

skip hbase related UT in sub-module: eagle-entity-base, to avoid false 
failures




---
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-376) remove faulty hbase related UT code

[Michael Wu (JIRA)]

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

Michael Wu commented on EAGLE-376:
--

PR #267 has been created at: https://github.com/apache/incubator-eagle/pull/267

> remove faulty hbase related UT code
> ---
>
> Key: EAGLE-376
> URL: https://issues.apache.org/jira/browse/EAGLE-376
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
>Assignee: Michael Wu
>




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

[jira] [Updated] (EAGLE-376) skip faulty hbase related UT code

[Michael Wu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Wu updated EAGLE-376:
-
Summary: skip faulty hbase related UT code  (was: remove faulty hbase 
related UT code)

> skip faulty hbase related UT code
> -
>
> Key: EAGLE-376
> URL: https://issues.apache.org/jira/browse/EAGLE-376
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
>Assignee: Michael Wu
>




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

[RESULT][VOTE] Release: Apache Eagle 0.4.0-incubating (Release Candidate 3)

[Michael Wu]

Hi all,

Voting is now closed and has passed with the following tally:
- PPMC +1: Julian Hyde, Hao Chen, Edward Zhang, Qinwen Zhao (sum: 4)
- Others +1: Huizhi Lu (sum: 1)

A vote will now be called on gene...@incubator.apache.org. Thank you all
for voting for this release candidate.

Michael




On Wed, Jul 13, 2016 at 11:33 AM, Zhao Qingwen  wrote:

> +1 (binding)
>
> * Download & built successfully with Java HotSpot(TM) 64-Bit Server VM &
> java version "1.7.0_79"
> * All unit tests passed
> * License check passed
> * Jars files reported in apache-eagle-0.4.0-incubating rc2 have been
> resolved
>
>
>
> Best Regards,
> Qingwen Zhao | 赵晴雯
>
>
>
>
> 2016-07-13 9:03 GMT+08:00 Edward Zhang :
>
> > +1 (binding)
> >
> > * Downloaded & built successfully with Hotspot JDK1.7 on OSX
> > * Signature checked, md5, sha1 verified (
> > https://httpd.apache.org/dev/verification.html)
> > * Apache rat:check passed (mvn apache-rat:check)
> >
> > * no jar files included.
> >
> >
> > Thanks
> >
> > Edward
> >
> > On Mon, Jul 11, 2016 at 10:34 PM, Hao Chen  wrote:
> >
> > > +1 (binding)
> > >
> > > Invalid JAR files issue reported in previous
> > apache-eagle-0.4.0-incubating
> > > rc2 have been resolved.
> > >
> > > * Downloaded & Built successfully on MacOSX 10.10.5 with Java
> > > HotSpot 1.7.0_75.
> > > * Verified signature
> > > * Ran rat:check and passed
> > >
> > > - Hao
> > >
> > > On Tue, Jul 12, 2016 at 6:39 AM, Lu, Huizhi  wrote:
> > >
> > > > +1 (non-binding)
> > > >
> > > > * Downloaded & built successfully on HotSpot 64-bit JDK 1.7 OS X
> > > > * Signature checked, md5, sha1 verified
> > > > * Apache rat:check passed (mvn apache-rat:check)
> > > > * Release matches tag.
> > > >
> > > >
> > > > -Huizhi
> > > >
> > > > > On Jul 11, 2016, at 2:40 AM, Michael Wu 
> wrote:
> > > > >
> > > > > Hi all,
> > > > >
> > > > > This is a release vote for Apache Eagle, version 0.4.0-incubating,
> > > > release
> > > > > candidate 3.
> > > > >
> > > > > Highlighted changes in this release are as the following:
> > > > >  * JBDC Metadata Storage Extension
> > > > >  * Topology management in remote mode including start/stop/status
> > > > > operations
> > > > >  * Auditlogparser for MapR's audit log
> > > > >  * Oozie auditlog integration for Oozie security monitoring
> > > > >  * Add applicaiton "maprFSAuditLog"
> > > > >  * Refactor bin/eagle-sandbox-starter.sh to make it easier to use
> > > > >
> > > > > Thanks to everyone who has contributed to this release.
> > > > >
> > > > > Here's the release note:
> > > > > *
> > > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-eagle.git;a=blob_plain;f=CHANGELOG.txt;hb=refs/heads/branch-0.4.0
> > > > > <
> > > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-eagle.git;a=blob_plain;f=CHANGELOG.txt;hb=refs/heads/branch-0.4.0
> > > > >*
> > > > >
> > > > > The artifacts to be voted on are located at:
> > > > > *
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/eagle/0.4.0-incubating-rc3/
> > > > > <
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/eagle/0.4.0-incubating-rc3/
> > > > >*
> > > > >
> > > > > The commit to be voted upon:
> > > > > *
> > > >
> > >
> >
> https://github.com/apache/incubator-eagle/commit/eac0f27958f2ed8c6842938dad0a995a87fd0715
> > > > > <
> > > >
> > >
> >
> https://github.com/apache/incubator-eagle/commit/eac0f27958f2ed8c6842938dad0a995a87fd0715
> > > > >*
> > > > >
> > > > > Release tag is:
> > > > > *
> > > >
> > >
> >
> https://github.com/apache/incubator-eagle/releases/tag/v0.4.0-incubating-rc3
> > > > > <
> > > >
> > >
> >
> https://github.com/apache/incubator-eagle/releases/tag/v0.4.0-incubating-rc3
> > > > >*
> > > > >
> > > > > Release artifacts are signed with the following key:
> > > > > http://people.apache.org/keys/committer/mw.asc
> > > > >
> > > > > The hashes of the artifacts are as follows:
> > > > > apache-eagle-0.4.0-incubating-src-rc3.tar.gz.md5:
> > > > > 5781048a2fc2b3dcfe5e30a09be86d25
> > > > > apache-eagle-0.4.0-incubating-src-rc3.tar.gz.sha1:
> > > > > a98b565604b3921a4ea5c53e30479427b227e1e2
> > > > >
> > > > > Please vote on releasing this package as: Apache Eagle
> > > 0.4.0-incubating.
> > > > >
> > > > > The vote is open for the next 72 hours and passes if a majority of
> at
> > > > least
> > > > > three +1 PPMC votes are cast.
> > > > >
> > > > > [ ] +1 Release this Apache Eagle 0.4.0-incubating Release Candidate
> > 3.
> > > > >
> > > > > [ ]  0 I don't feel strongly about it, but I'm okay with the
> release
> > > > >
> > > > > [ ] -1 Do not release this package because...
> > > > >
> > > > >
> > > > > Thanks.
> > > > > Michael
> > > >
> > > >
> > >
> >
>

[jira] [Commented] (EAGLE-251) Run eagle on flink/samza

[Milap Wadhwa (JIRA)]

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

Milap Wadhwa commented on EAGLE-251:


Hi,

I am newbie to Eagle Community. I would like to pick up this task and try to 
get my hands dirty.

Please assign me this task. Please let me know If you need some info.


Regards,
Milap Wadhwa

> Run eagle on flink/samza
> 
>
> Key: EAGLE-251
> URL: https://issues.apache.org/jira/browse/EAGLE-251
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.3.0
>Reporter: Su Ralph
>Priority: Minor
>  Labels: new
>
> Eagle is running on storm. One might want to do some interesting port to 
> other stream framework like flink/samza.



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

Re: [Discuss] what will be the decent way to remove jars from source code for releases

[Michael Wu]

Hi Julian,

Ticket EAGLE-377  has been
created. We'll fix it in 0.5.0-incubating version. Thanks for your kindly
reminding. Anything missed, please do let me know.

Michael

On Thu, Jul 14, 2016 at 11:21 AM, Julian Hyde  wrote:

> I understand now. But I have to say, even though I have read the git
> commit logs and JIRA cases it’s very difficult to figure out why this
> particular solution was chosen. And asking users to download a patch from
> github is still a hack, yes? If you agree it’s a hack, why didn’t anyone
> think to log a JIRA case to clean up?
>
> Julian
>
> [1] https://issues.apache.org/jira/browse/EAGLE-365 <
> https://issues.apache.org/jira/browse/EAGLE-365>
> [2]
> https://github.com/apache/incubator-eagle/commit/9cd75b188941bf476878a2210984546e4e257c7a
> <
> https://github.com/apache/incubator-eagle/commit/9cd75b188941bf476878a2210984546e4e257c7a
> >
> [3] http://eagle.incubator.apache.org/docs/quick-start.html <
> http://eagle.incubator.apache.org/docs/quick-start.html>
> [4] https://github.com/apache/incubator-eagle/pull/180 <
> https://github.com/apache/incubator-eagle/pull/180>
>
>
> > On Jul 13, 2016, at 7:41 PM, Michael Wu  wrote:
> >
> > Hi Henry,
> >
> > The solution is we removed the jars out of the project source code
> folder,
> > and will use a PR patch to hold the files for downloading, so that
> > customers can succeed to build in this flow: download source code
> tar-ball
> > -> extract tar-ball -> apply the patch -> maven build.
> >
> > This approach has been documented on apache eagle quick-start guide page.
> >
> > Thanks.
> > Michael
> >
> > On Thu, Jul 14, 2016 at 12:33 AM, Henry Saputra  >
> > wrote:
> >
> >> So what was the solution for this? Could someone points to JIRA or
> Github
> >> PR to fix this?
> >>
> >> Thanks much!
> >>
> >> - Henry
> >>
> >> On Mon, Jul 11, 2016 at 1:30 AM, Julian Hyde  wrote:
> >>
> >>> Can someone explain why these jar files have to be checked into git?
> >>> Many other jar (and other binary) files are retrieved from a maven
> >>> repo when you build; why not these? You can use maven magic to
> >>> extract/filter/copy these files exactly where you need them on the
> >>> first build.
> >>>
> >>> Source files have a sacred role in open source because (a) they can be
> >>> edited (a fundamental right granted by an open source license), (b)
> >>> they can be audited during a release.
> >>>
> >>> And, leaving the open source issues aside and just looking at the
> >>> software engineering, checking non-source files into a source-control
> >>> system, and especially into git, is often a bad idea. For instance,
> >>> projects hotly debate whether to check in java files generated by
> >>> protobuf, because the .proto file is the "source", and the .java files
> >>> are generated. Git doesn't handle binary files particularly well, and
> >>> if the binary is modified a few times the git repo starts to become
> >>> bloated in size.
> >>>
> >>> Julian
> >>>
> >>>
> >>> On Sun, Jul 10, 2016 at 8:28 PM, Zhang, Edward (GDI Hadoop)
> >>>  wrote:
>  In 0.3 release, Hemanth uses a patch to work around this issue. Can we
> >>> use the same approach in 0.4 and in 0.5 we have decided to remove
> >>> dependency on tomcat.
> 
> 
>  Thanks
> 
>  Edward
> 
>  
>  From: Hao Chen 
>  Sent: Sunday, July 10, 2016 8:17:48 PM
>  To: dev@eagle.incubator.apache.org
>  Subject: Re: [Discuss] what will be the decent way to remove jars from
> >>> source code for releases
> 
>  Yes, the jars are added into the source package intentionally, which
> is
>  necessary for bootstrapping eagle service. So maybe it possible for us
> >>> the
>  keep the jars following apache way? Otherwise we may need some
> >> additional
>  work to refactoring our package method.
> 
>  - Hao
> 
>  On Mon, Jul 11, 2016 at 11:07 AM, Michael Wu 
> >> wrote:
> 
> > Hi guys,
> >
> > Further tested and verified, the 3 jar dependencies are NECESSARY for
> >>> the
> > eagle-service to start up. Without them, we can build the project but
> >>> when
> > we deploy it, eagle-service fails to start up complaining the lack of
> >>> the
> > dependencies. So, we cannot simply remove them before packaging the
> >>> source
> > tar ball.
> >
> > @PPMC, so far, we can tell that the 3 remaining jars are intended to
> >> be
> > there for the project's normal functionalities, they are important
> and
> > cannot be removed, can we just vote them as passed, please?
> >
> > Michael
> >
> > On Sat, Jul 9, 2016 at 3:46 PM, Michael Wu 
> >> wrote:
> >
> >> Hi dev group,
> >>
> >> As you may know, we encountered the issue of having