Re: [VOTE] Release Apache Flume Spring Boot 2.0.0-rc2

+1 on the release I didn’t test it but it looks like Ralph and Donát did, so here is my +1 to unblock the release. Mike Sent from my iPhone > On Mar 30, 2023, at 9:45 PM, Ralph Goers wrote: > > Note that although this has 3 +1 votes it still needs one more +1 vote from > a PMC member.

Re: [ANNOUNCE] New Flume committer - Tristan Stevens

Congrats Tristan! Welcome aboard. Best, Mike On Mon, Jan 13, 2020 at 9:29 PM Bessenyei Balázs Donát wrote: > On behalf of the Apache Flume PMC, I am very pleased to welcome Tristan > Stevens > as a committer on the Apache Flume project. > > Tristan has been contributing to Flume over an

Re: Flume logo

Hi Daniel, I dug around a few years ago and unfortunately I could not find a vector version of the Flume logo. Out of the ones above, I like the current official logo the best. I admit there is room for improvement but a contract with a professional graphic designer (99 designs?) would likely be

Re: Better Marketing

one bug already in Log4j that was > causing a performance hit with Flume and have corrected that. > > Ralph > >> On Apr 28, 2019, at 11:42 AM, Mike Percy wrote: >> >> I’d certainly be in favor of updating the project description to be more >> general. That said, pa

Re: Better Marketing

I’d certainly be in favor of updating the project description to be more general. That said, part of Flume’s value proposition is integration with a bunch of components off the shelf and the main ones it ships are Hadoop ecosystem components, so we shouldn’t completely ignore that when

[ANNOUNCE] Change of Apache Flume PMC Chair

Dear Flume community, I have had the opportunity to serve as the Flume PMC Chair for the last year and some months, and for personal reasons have decided to step down at this time. I am very happy to announce that based on the PMC's recommendation, the Apache Foundation board has appointed

Re: [ANNOUNCE] New Flume PMC member - Ferenc Szabo

Congratulations Ferenc and welcome to the PMC! Thanks so much for all your diligence and for running the 1.9.0 release! Best regards, Mike On Wed, Jan 30, 2019 at 8:09 AM Denes Arvay wrote: > Hello Flume community, > > On behalf of the Apache Flume PMC I am pleased to announce that Ferenc >

Re: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org

>> I support the move and I think we should do it as soon as possible. >> If there is anything I can do to support, let me know. >> >> >> Donat >> >>> On Sat, Jan 5, 2019 at 12:26 AM Mike Percy wrote: >>> >>> Hi Ferenc, OK sounds good

Re: [ANNOUNCE] Apache Flume 1.9.0 released

Nice! Thanks Ferenc for managing this release! Regards, Mike > On Jan 8, 2019, at 6:34 AM, Ferenc Szabo wrote: > > The Apache Flume team is pleased to announce the release of Flume > version 1.9.0. > > Flume is a distributed, reliable, and available service for efficiently > collecting,

Re: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org

reate the JIRA > ticket. > > > Regards, > Ferenc > > > > > > On Thu, Jan 3, 2019 at 6:38 PM Mike Percy wrote: > > > Hi Flume devs, > > I propose we ask ASF Infra to move the Flume Git repo to GitBox as soon > as > > the release has been final

Re: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org

Hi Flume devs, I propose we ask ASF Infra to move the Flume Git repo to GitBox as soon as the release has been finalized / announced. Once they switch things over, we can update the web site / documentation to reflect that. Does anyone see any problems with this approach? Ferenc, when do you

Re: [VOTE] Release Apache Flume version 1.9.0 RC3

+1 on RC3 - Sigs and checksums match for source and binary artifacts - Source artifact matches git tag - LICENSE file looks good - README looks good - Source artifact builds and tests pass on Ubuntu bionic - Binary artifact runs on Ubuntu bionic with minimal configuration Thanks for

Re: [VOTE] Release Apache Flume version 1.9.0 RC2

Sorry for the delay in voting. -1 on RC2 because the source artifact should match the tag, but it has a .git folder in there: $ diff -r apache-flume-1.9.0-src src-tag Only in apache-flume-1.9.0-src: .git I am not sure why we don't just use the scripts designed to generate source artifacts

Re: [VOTE] Release Apache Flume version 1.9.0 RC1

Thanks Ferenc for putting this together! I agree with Denes that we should ensure the tag and source artifact match exactly. There shouldn't be any extra files if we use ./dev-support/generate-source-release.sh to generate the source release files because that script uses git archive to generate

Re: [DISCUSS] Flume 1.9 release proposal

Are you saying that because the customers are good > with the config change Flume 1.9 can go out with Log4j 2 or are you saying > you are good with updating the release notes to say it will happen in the > next release? > > Ralph > >> On Nov 29, 2018, at 10:53 PM, Mike Percy wro

Re: [DISCUSS] Flume 1.9 release proposal

>> Regarding move from Log4j1.x to 2, it’d be interesting to see what other >>>> Apache projects, such as Hadoop, Hive etc did around this (in fact, are >>>> they even at 2.x yet?). For me, if you need to change config, it’s not a >>>> minor release, it become

Re: [DISCUSS] Flume 1.9 release proposal

onát > wrote: > > > > I wonder, is there anything blocking us from releasing 2.0 next instead > of 1.x? > > > > > > Donat > > > > On Mon, Nov 26, 2018 at 6:27 PM Mike Percy wrote: > >> > >> If only the PMC would be affected by this dec

Re: [DISCUSS] Flume 1.9 release proposal

> >> As I said, I am fine with adding a notice to the release notes stating > > the > > >> logging will be changed in the next release regardless of its version > > >> number. This way the revert only needs to happen on the release branch >

Re: [DISCUSS] Flume 1.9 release proposal

really well. I’d like to commit > back some of the changes but the main one - Flume configuration - I really > don’t like and need to redo the whole thing. > > Ralph > > > On Nov 24, 2018, at 5:11 PM, Mike Percy wrote: > > > > I wasn't aware of this security issu

Re: [DISCUSS] Flume 1.9 release proposal

in a minor release, like a new and highly dangerous security bug. Without such a motivation, I don't see how this incompatible dependency change can be justified. Mike On Sat, Nov 24, 2018 at 3:20 PM Ralph Goers wrote: > > > On Nov 24, 2018, at 2:35 PM, Mike Percy wrote: > > > &g

Re: [DISCUSS] Flume 1.9 release proposal

Flume has long had a policy of backwards compatibility with its own configuration files and people expect things to "just work" when upgrading Flume. If log4j2 can't parse the log4j1 config file format then it's an incompatible upgrade and should not be done in a minor Flume release. If log4j2

Re: What do we do with Integrations with no maintainer?

I agree with the above... the JAR hell we are currently in seems mostly unresolvable and shedding dependencies seems like a reasonable choice regardless of whether we implement an isolated classloader or not. Mike On Mon, Nov 19, 2018 at 6:02 AM Ferenc Szabo wrote: > Hi all, > > I somewhat

Minor reface to the Apache Flume project web site

Hi all, I went to add the issues@ list to the mailing list page on http://flume.apache.org and remembered that I didn't care for some of the fonts and colors on the site theme, so I updated the CSS to be prettier while I was in there. Now it's more "nautical", in line with the color scheme of the

Re: Merge of patch in Flume-3021?

t; > Did you have a chance to look into this? > > thanks, > > Helmut > > > -----Original Message- > From: Mike Percy [mailto:mpe...@apache.org] > Sent: Montag, 26. März 2018 21:46 > To: dev@flume.apache.org > Subject: Re: Merge of patch in Flume-3021?

Re: Merge of patch in Flume-3021?

[INFO] > > [INFO] BUILD FAILURE > > > The LuceneTestCase is extended by SolrTestCaseJ4. > No idea, what I could do against this. > > best regards, > > Helmut > > -Original Message- > From: Mike P

Re: Merge of patch in Flume-3021?

our current code on a github fork and describe the issue. I will > > see what can we do to solve it. > > > > > > On Tue, Mar 6, 2018 at 10:50 AM, Wahrmann, Helmut < > helmut.wahrm...@rsa.com > > > > > wrote: > > > > > Hi Mike, > > > >

Re: Merge of patch in Flume-3021?

get the credit. > > He'll do so after the Chinese New Year's Eve. > > > > I will then issue a Pull request for the new ES Rest client, which is > > dependent on the above work. > > > > best regards, > > Helmut > > > > -Original Message- > &

Re: Merge of patch in Flume-3021?

Chinese New Year's Eve. > > I will then issue a Pull request for the new ES Rest client, which is > dependent on the above work. > > best regards, > Helmut > > -Original Message- > From: Mike Percy [mailto:mpe...@apache.org] > Sent: Dienstag, 13. Februar 2018

Re: Store password for config safely?

I think Ferenc has been looking at something related to this, or perhaps is trying to get an existing patch merged (FLUME-2442 , PR 197 ). I haven't been following that work closely so I don't know if it's

Re: Merge of patch in Flume-3021?

Hi Helmut, I see that I neglected to follow up on the other thread on this topic after your reply about SolrServer missing from the solrj jar. Let me ask around w/ some folks I know that work on Solr and see if there is any way to retain the SolrServer for our tests after upgrading to the new

Re: Breaking changes in Flume - 2.0 release

going to +1 Denes' change @ https://github.com/apache/ flume/pull/195 Mike On Tue, Jan 30, 2018 at 2:32 PM, Mike Percy <mpe...@apache.org> wrote: > On Tue, Jan 30, 2018 at 11:20 AM, Hari Shreedharan < > hshreedha...@apache.org> wrote: > >> Agreed. Another chang

Re: Breaking changes in Flume - 2.0 release

On Tue, Jan 30, 2018 at 11:20 AM, Hari Shreedharan wrote: > Agreed. Another change we might want to consider is shading the > dependencies of individual modules and the framework itself. This will make > it easier to upgrade individual modules. > +1, I don't know to

Re: Merging to trunk?

On Mon, Jan 29, 2018 at 10:48 AM, Wahrmann, Helmut wrote: > > I think it is not a problem to distribute the modules together if we have > maintainers for them. > It doesn't make sense to release Flume 1.9 in 2018 with support for module > versions which were current in

Re: Breaking changes in Flume - 2.0 release

I think this change is important enough to warrant a breaking version bump. Virtually every project depends on Guava, and Flume should certainly shade/rename Guava for its internal use. I'd be on board with doing a Flume 2.0 to remove Guava from the public API. Mike On Mon, Jan 29, 2018 at 2:31

Re: Merging to trunk?

probably to set "optional" to true in the > > pom.xml. > > > Then we don't distribute those Jars in the flume lib and the users need > > to set their class path to point e.g. to Elasticsearch and then the > correct > > libs will be used. > > > I doubt that a Elasticsear

Re: Squash commits on trunk

remove spurious files > > 140ea5d FLUME-2050 Upgrade to Log4j 2 > > > > If there are no objections I'll force push this to the trunk. > > (Note: it might mess up the git-wip-us.apache.org -> github repo > mirroring, > > if that happens I'll get in touch with Ap

Re: Merging to trunk?

, which might cause problems to > other projects. > So I think it can be safely merged into trunk. > > best regards, > > Helmut > > > -Original Message- > From: Mike Percy [mailto:mpe...@apache.org] > Sent: Dienstag, 23. Jänner 2018 20:39 > To: dev@flume.a

Re: Merging to trunk?

Hi Helmut, Thank you for bringing this up on dev@ and thank you for the patch. I see there are other people people interested in this component upgrade as well. As you are probably aware, a Flume committer will need to approve the change before I gets merged to trunk. My primary concern w/

Re: [ANNOUNCE] New Flume PMC Chair

. Best regards, Mike On Thu, Jan 18, 2018 at 12:37 PM, Hari Shreedharan <hshreedha...@apache.org> wrote: > Hi all, > > It gives me immense happiness to announce that the Apache Software > Foundation Board has appointed Mike Percy as the new PMC chair of the > Apache Flume Project.

Re: Working with Jira

Hi Helmut, I think I just added you as a contributor in Flume which would allow you to assign yourself a JIRA. If it didn't work, send me your username in JIRA. Sending a GitHub pull request is the preferred method to contribute a patch these days. Best, Mike On Thu, Jan 18, 2018 at 5:55 AM,

Re: Squash commits on trunk

I agree squash-before-push is a good policy to maintain a readable commit history. I'd be +1 to doc this and squash the relevant commits. Mike On Wed, Jan 10, 2018 at 5:37 AM, Denes Arvay wrote: > Hi Hari, > > Thank you for your answer. > I think having one single commit

Re: Message Lists

t; Subject: Re: Message Lists > >> Date: December 11, 2017 at 1:41:11 PM MST > >> To: dev@flume.apache.org > >> Reply-To: dev@flume.apache.org > >> > >> +1. I agree, we should move the private messages out. > >> > >> On Sun, Dec

Re: Message Lists

ting infra to make the changes based on so little input. > > Ralph > >> On Dec 8, 2017, at 9:03 PM, Mike Percy <mpe...@apache.org> wrote: >> >> Sorry, I didn't see this message because of all the automated emails! >> >> +1 from me. >>

Re: Message Lists

Sorry, I didn't see this message because of all the automated emails! +1 from me. Mike On Sat, Nov 11, 2017 at 9:43 PM, Ralph Goers wrote: > Currently all the messages from Jenkins, Jira and GitHub land in this > mailing list. That makes this mailing list very

[ANNOUNCE] New Flume committers and PMC member

done! Best regards, Mike Percy on behalf of the Flume PMC

Re: [ANNOUNCE] Apache Flume 1.8.0 released

Congrats all! Nice work. Regards, Mike On Wed, Oct 4, 2017 at 9:57 AM, Denes Arvay wrote: > The Apache Flume team is pleased to announce the release of Flume > version 1.8.0. > > Flume is a distributed, reliable, and available service for efficiently > collecting,

Re: [VOTE] Release Apache Flume version 1.8.0 RC2

+1 (binding) I only checked the source artifact, I didn't check the binary convenience artifacts. - Checksums and sigs match - LICENSE file looks good - README file looks good - Files match git tag - Ran a full build and all tests passed Thanks for managing this release Denes, and to the others

Re: [VOTE] Release Apache Flume version 1.8.0 RC2

Sorry for not voting yet. I've just been slammed. I'll take a look at RC2 tomorrow. Mike On Mon, Sep 18, 2017 at 5:46 AM, Denes Arvay wrote: > Hi All, > > I'd like to encourage everybody to check the RC2 and provide feedback about > it. It's quite simple, just do the

Re: 1.8 RC1 failure - and how to fix it

Hi Denes, Shouldn't we use ./dev-support/generate-source-release.sh to generate the source release? That guarantees that the source release matches the git tag, and we don't have to worry about these kinds of weird problems. Mike On Thu, Sep 14, 2017 at 3:28 PM, Denes Arvay

Re: [DISCUSS] Flume 1.8 release proposal

I added the additional versions earlier today but neglected to notify the list until just now. :) +1 on the plan. Thanks for keeping us updated and continuing to drive this release, Denes! Mike On Tue, Sep 12, 2017 at 3:04 AM, Denes Arvay wrote: > Hi Donat, > > Thanks for

Re: [DISCUSS] Flume 1.8 release proposal

Hi Denes, +1 from me for releasing a Flume 1.8.0 and for you taking on the RM role for Flume 1.8.0. The timeline for a first RC seems fine. It sounds like you will have some help, which is good. Let me know if you need anything from me. Regards, Mike On Mon, Sep 4, 2017 at 1:21 AM, Denes Arvay

[jira] [Commented] (FLUME-3115) Upgrade netty library dependency

[ https://issues.apache.org/jira/browse/FLUME-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075293#comment-16075293 ] Mike Percy commented on FLUME-3115: --- The CVE says versions of Netty prior to 3.9.2 are vulnerable

Re: Update 3rd party dependencies

Hi Attila, Thanks for sending this. I have a few thoughts / questions on this: 1) You didn't include the analysis of A,G,S, etc. for the listed dependencies in your email. 2) If there are security vulnerabilities reported that could affect Flume then we should upgrade those dependencies where

[jira] [Commented] (FLUME-2957) Remove Guava from our public API

[ https://issues.apache.org/jira/browse/FLUME-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075107#comment-16075107 ] Mike Percy commented on FLUME-2957: --- I agree that we should simply expose a Map instead of the Guava

[ANNOUNCE] New Flume committer - Denes Arvay

On behalf of the Apache Flume PMC, I am very pleased to welcome Denes Arvay as a committer on the Apache Flume project. Denes has put a lot of effort into improving the stability of Flume, most recently focusing on identifying and fixing serious and hard-to-diagnose issues including several bugs

[jira] [Resolved] (FLUME-3092) Extend the FileChannel's monitoring metrics

[ https://issues.apache.org/jira/browse/FLUME-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Percy resolved FLUME-3092. --- Resolution: Fixed Fix Version/s: 1.8.0 > Extend the FileChannel's monitoring metr

[jira] [Resolved] (FLUME-3085) HDFS Sink can skip flushing some BucketWriters, might lead to data loss

[ https://issues.apache.org/jira/browse/FLUME-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Percy resolved FLUME-3085. --- Resolution: Fixed Pushed to trunk. > HDFS Sink can skip flushing some BucketWriters, might l

[jira] [Updated] (FLUME-3085) HDFS Sink can skip flushing some BucketWriters, might lead to data loss

[ https://issues.apache.org/jira/browse/FLUME-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Percy updated FLUME-3085: -- Fix Version/s: 1.8.0 > HDFS Sink can skip flushing some BucketWriters, might lead to data l

[jira] [Updated] (FLUME-2293) Isolate Flume agent plugins to their own classloader

[ https://issues.apache.org/jira/browse/FLUME-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Percy updated FLUME-2293: -- Affects Version/s: (was: 1.7.0) v1.7.0 > Isolate Flume agent plug

[jira] [Updated] (FLUME-2293) Isolate Flume agent plugins to their own classloader

[ https://issues.apache.org/jira/browse/FLUME-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Percy updated FLUME-2293: -- Component/s: Technical Debt > Isolate Flume agent plugins to their own classloa

[jira] [Updated] (FLUME-2293) Isolate Flume agent plugins to their own classloader

[ https://issues.apache.org/jira/browse/FLUME-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Percy updated FLUME-2293: -- Affects Version/s: 1.7.0 > Isolate Flume agent plugins to their own classloa

Re: [ANNOUNCE] Bessenyei Balázs Donát joining the Flume PMC

> On Mar 11, 2017, at 12:57 AM, Mike Percy <mpe...@apache.org> wrote: > > Donat was also instrumental to the latest release by acting as the release > manager for Flume 1.6.0. Oops, I meant Flume 1.7.0 :) Mike

[ANNOUNCE] Bessenyei Balázs Donát joining the Flume PMC

Hi Flume community, Today I'm very happy to announce that the PMC has voted to add Bessenyei Balázs Donát (Donat) as a PMC member on the Apache Flume project! Donat joined the Flume project as a committer back in September and since that time has taken on the work of doing many code reviews and

Re: Travis-CI build hung

t; something > > On Feb 24, 2017 3:32 PM, "Mike Percy" <mpe...@apache.org> wrote: > > > The Travis pre-commit build request for PR #109 seems hung: > > https://travis-ci.org/apache/flume/builds/204857948 > > > > Does anybody know if I need to have some

Travis-CI build hung

The Travis pre-commit build request for PR #109 seems hung: https://travis-ci.org/apache/flume/builds/204857948 Does anybody know if I need to have some special permissions to cancel that request and resubmit? Thanks, Mike

[jira] [Assigned] (FLUME-3056) TestApplication hangs indefinitely

[ https://issues.apache.org/jira/browse/FLUME-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Percy reassigned FLUME-3056: - Assignee: Andras Beni > TestApplication hangs indefinit

[jira] [Commented] (FLUME-3055) Taildir source FD leaks when the matched files is renamed or rotated to other dir

[ https://issues.apache.org/jira/browse/FLUME-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15873870#comment-15873870 ] Mike Percy commented on FLUME-3055: --- Thanks [~huLiu] for confirming! > Taildir source FD leaks w

Re: REST API Proposal

Thanks for sending this out, Tristan. Sorry for my late response. I added a couple of comments to the doc. One missing piece is how do the configuration changes get persisted (or do they?) Due to other commitments it would be difficult for me to help out very much. However, it may be possible for

[jira] [Commented] (FLUME-3055) Taildir source FD leaks when the matched files is renamed or rotated to other dir

[ https://issues.apache.org/jira/browse/FLUME-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870983#comment-15870983 ] Mike Percy commented on FLUME-3055: --- Hi [~huLiu], is this a real bug? Did you work around the problem

[jira] [Resolved] (FLUME-2427) java.lang.NoSuchMethodException and warning on HDFS (S3) sink

[ https://issues.apache.org/jira/browse/FLUME-2427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Percy resolved FLUME-2427. --- Resolution: Fixed Fix Version/s: v1.8.0 > java.lang.NoSuchMethodException and warning on H

[jira] [Assigned] (FLUME-2427) java.lang.NoSuchMethodException and warning on HDFS (S3) sink

[ https://issues.apache.org/jira/browse/FLUME-2427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Percy reassigned FLUME-2427: - Assignee: Mike Percy > java.lang.NoSuchMethodException and warning on HDFS (S3) s

[jira] [Assigned] (FLUME-2427) java.lang.NoSuchMethodException and warning on HDFS (S3) sink

[ https://issues.apache.org/jira/browse/FLUME-2427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Percy reassigned FLUME-2427: - Assignee: Ping Wang (was: Mike Percy) > java.lang.NoSuchMethodException and warning on HDFS

[jira] [Commented] (FLUME-2427) java.lang.NoSuchMethodException and warning on HDFS (S3) sink

[ https://issues.apache.org/jira/browse/FLUME-2427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870967#comment-15870967 ] Mike Percy commented on FLUME-2427: --- +1 on [~wpwang]'s patch, I am also going to lower this to info

[jira] [Commented] (FLUME-3042) use ganglia to monitoring flume KafkaChannel error

[ https://issues.apache.org/jira/browse/FLUME-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870956#comment-15870956 ] Mike Percy commented on FLUME-3042: --- Please report this to the Ganglia project... with an example

[jira] [Resolved] (FLUME-3049) Wrapping the exception into SecurityException in UGIExecutor.execute hides the original one

[ https://issues.apache.org/jira/browse/FLUME-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Percy resolved FLUME-3049. --- Resolution: Fixed Fix Version/s: v1.8.0 Pushed to trunk. Thanks for the patch, Denes

Re: Moving Developer Section of cwiki to the git repository

, Balazs Donat Bessenyei <bes...@cloudera.com > wrote: > Thank you. > > Wouldn't committing (and PRing) them one-by-one pollute the git log and > mailing lists too much? > > On Oct 24, 2016 5:26 PM, "Mike Percy" <mpe...@apache.org> wrote: > > > Feel fre

Re: Moving Developer Section of cwiki to the git repository

> flume/pull/77 > > I'm planning to add more e-mail templates to the HowToRelease.md and > commit all docs in a single commit, but reviews and comments are > welcome in the meanwhile. > > > Thank you, > > Donat > > On Fri, Oct 21, 2016 at 6:07 PM, Mike Per

Re: jira reference is missing from git commit messages

Hi Attila, On Fri, Oct 21, 2016 at 7:51 PM, Attila Simon wrote: > I have no strong opinion on whether we should have a jira or not (thus > the proposal of FLUME-PR70). I just "I found this habit very useful". > It seems kind of obtrusive to me to require committers to use

Re: Enabling Travis-CI on Flume

sorry if my former post delivered the > wrong message. > > On Fri, Oct 21, 2016 at 6:29 PM, Mike Percy <mpe...@apache.org> wrote: > > > Personally I prefer Jenkins over TravisCI for various reasons however if > > Donat is willing to do the work of adding pre-commit c

Re: Moving Developer Section of cwiki to the git repository

Thanks, Donat. +1 on moving the docs. Regarding the web site source code, it can reside in svn or git however it should continue using the standard ASF site infrastructure [1] for hosting content which consists only of static rendered HTML content. Our options for pushing that rendered HTML are

Re: Enabling Travis-CI on Flume

Personally I prefer Jenkins over TravisCI for various reasons however if Donat is willing to do the work of adding pre-commit checks on PRs via Travis then I say let him do it, in the Apache spirit of "let they that do the work make the decisions". If someone actually spends the time to set up

Re: jira reference is missing from git commit messages

Hi Attila, Thanks for raising this concern of yours. Please see inline. On Fri, Oct 21, 2016 at 12:17 PM, Attila Simon wrote: > The how to contribute page asks to have a jira first for each change. I > guess with allowing pull requests we have to update the how to contribute

Re: [ANNOUNCE] Apache Flume 1.7.0 released

Thank you for all your hard work RMing this release Donat and getting it to the finish line. It was my pleasure to help out! Best, Mike On Tue, Oct 18, 2016 at 1:32 PM, Balazs Donat Bessenyei <bes...@cloudera.com > wrote: > And thank you, Mike Percy for the mentoring and tremendou

Re: [ANNOUNCE] Apache Flume 1.7.0 released

Woot! Congrats everyone! Thanks Donat for working so hard to get this version of Flume out the door! Best, Mike On Tue, Oct 18, 2016 at 10:09 AM, Bessenyei Balázs Donát wrote: > The Apache Flume team is pleased to announce the release of Flume > version 1.7.0. > > Flume is

Re: [RESULT] Flume 1.7.0 release vote

, 2016 at 2:20 PM, Balazs Donat Bessenyei <bes...@cloudera.com > wrote: > Thank you for the help, Mike! > > On Mon, Oct 17, 2016 at 1:53 PM, Mike Percy <mpe...@apache.org> wrote: > > Thanks for running the vote, Donat! > > > > I will help to deploy the staged

Re: [RESULT] Flume 1.7.0 release vote

/thread.html/ > 3cf114125dbea6e662b69d1312c34184690af327900e8dcccea5edde@% > 3Cdev.flume.apache.org%3E > > The vote has received 3 binding +1 votes from the following PMC members: > Mike Percy > Hari Shreedharan > Brock Noland > > Four non-binding +1 votes were received from:

Re: Improving Flume distribution packaging

l in the future. > > On Fri, Oct 14, 2016 at 11:30 AM, Mike Percy <mpe...@apache.org > <javascript:;>> wrote: > > > Currently rpms are handled by downstream projects like Apache BigTop as > > well as commercial distributions. So in my view it's a duplicat

Re: Improving Flume distribution packaging

Currently rpms are handled by downstream projects like Apache BigTop as well as commercial distributions. So in my view it's a duplication of efforts there, particularly since BigTop and distributions based on it also harmonize dependencies to a certain extent and we mark many of our dependencies

Re: [VOTE] Release Apache Flume version 1.7.0 RC2

+1 (binding) There are some flaky tests which are listed below but I don't think they are release blockers. I performed the following checks: Binary convenience artifact: * Signature and checksums match * LICENSE, NOTICE, and README.md files in the binary convenience artifact look accurate and

Re: [VOTE] Release Apache Flume version 1.7.0 RC1

ache/flume/pull/68 > Regarding to the jackson-core|mapper-asl: it only has versions up to > 1.9.13 as of now. Thus specifying the 1. in the license is confusing > for me. "-asl" is already in the name and that is the important > information. > > Cheers, > Attila >

Re: [VOTE] Release Apache Flume version 1.7.0 RC1

On Wed, Oct 12, 2016 at 5:07 PM, Attila Simon wrote: > Additional libraries shipped but not mentioned in the licence file: > hamcrest-core (BSD License), junit (BSD License), xz ( > http://git.tukaani.org/?p=xz.git;a=blob;f=COPYING), > Regarding xz it looks like while the

Re: [VOTE] Release Apache Flume version 1.7.0 RC1

-1 for RC1 I've found a few problems with RC1: 1. As mentioned by Donat, the signed source artifact was corrupted somehow, I am guessing the maven assembly plugin had some problem at build / deploy time 2. I locally built a source tarball from the RC1 tag and compared the file contents with the

Re: Review Request 52627: FLUME-2971. Document secure Kafka Sink/Source/Channel setup

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/52627/#review152037 --- Ship it! Ship It! - Mike Percy On Oct. 10, 2016, 11:04 a.m

[jira] [Resolved] (FLUME-2999) Kafka channel and sink should enable statically assigned partition per event via header

[ https://issues.apache.org/jira/browse/FLUME-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Percy resolved FLUME-2999. --- Resolution: Fixed Fix Version/s: v1.7.0 Pushed to trunk. Thanks for the patch Tristan

[jira] [Commented] (FLUME-2999) Kafka channel and sink should enable statically assigned partition per event via header

[ https://issues.apache.org/jira/browse/FLUME-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15563027#comment-15563027 ] Mike Percy commented on FLUME-2999: --- +1. I am about to commit the latest rev from FLUME-2999. > Ka

Re: Review Request 52598: FLUME-2999 - Kafka channel and sink should enable statically assigned partition per event via header

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/52598/#review152027 --- Ship it! Ship It! - Mike Percy On Oct. 10, 2016, 1:53 a.m

[jira] [Updated] (FLUME-2911) Add includePattern option in SpoolDirectorySource configuration

[ https://issues.apache.org/jira/browse/FLUME-2911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Percy updated FLUME-2911: -- Affects Version/s: (was: notrack) > Add includePattern option in SpoolDirectorySource configurat

Re: Review Request 52627: FLUME-2971. Document secure Kafka Sink/Source/Channel setup

this. - Mike Percy On Oct. 7, 2016, 6:27 a.m., Attila Simon wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache

Re: Review Request 52627: FLUME-2971. Document secure Kafka Sink/Source/Channel setup

to documentation or provide a reference to where we can find more relevant information? flume-ng-doc/sphinx/FlumeUserGuide.rst (line 3203) <https://reviews.apache.org/r/52627/#comment220665> nit: please add spaces around the equals signs for consistency, here and elsewhere - Mike Pe

[jira] [Updated] (FLUME-2911) Add includePattern option in SpoolDirectorySource configuration

[ https://issues.apache.org/jira/browse/FLUME-2911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Percy updated FLUME-2911: -- Assignee: Andrea Rota > Add includePattern option in SpoolDirectorySource configurat

  1   2   3   4   5   6   7   8   9   10   >