Re: [VOTE] Apache Flume 1.5.0 RC1

2014-05-19 Thread Hari Shreedharan
This vote is now closed. I will send out the results in a separate email. 

Thanks to all who voted! 


Thanks,
Hari


On Monday, May 19, 2014 at 2:11 PM, Hari Shreedharan wrote:

> +1.  
> 
> * Verified Signatures and Checksums
> * Compared LICENSE file against the libs directory in both profiles - all 
> binary jars are covered by the license.
> * Checked top-level files. 
> 
> 
> Thanks,
> Hari
> 
> 
> On Sunday, May 18, 2014 at 12:22 PM, Wolfgang Hoschek wrote:
> 
> > +1 Looks good to me!
> > 
> > Wolfgang Hoschek
> > 
> > On May 17, 2014, at 8:47 PM, Hari Shreedharan  > (mailto:hshreedha...@cloudera.com)> wrote:
> > 
> > > Flume PMC - Please vote!
> > > 
> > > 
> > > On Wed, May 14, 2014 at 12:31 AM, Arvind Prabhakar  > > (mailto:arv...@apache.org)>wrote:
> > > 
> > > > +1
> > > > 
> > > > * Verified signatures and checksums for both binary and source tarballs
> > > > * Rat check looks good on source tarball
> > > > * Nit: Notice file has dated header, needs to be updated but not a 
> > > > blocker
> > > > 
> > > > Regards,
> > > > Arvind Prabhakar
> > > > 
> > > > 
> > > > On Wed, May 7, 2014 at 3:28 PM, Hari Shreedharan
> > > > mailto:hshreedha...@cloudera.com)>wrote:
> > > > 
> > > > > This is a vote for the next release of Apache Flume, version 1.5.0. We
> > > > are
> > > > > voting on release candidate RC1.
> > > > > 
> > > > > It fixes the following issues:
> > > > > http://s.apache.org/4eQ
> > > > > 
> > > > > *** Please cast your vote within the next 72 hours ***
> > > > > 
> > > > > The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5,
> > > > > *.sha1) for the source and binary artifacts can be found here:
> > > > > https://people.apache.org/~hshreedharan/apache-flume-1.5.0-rc1/
> > > > > 
> > > > > Maven staging repo:
> > > > https://repository.apache.org/content/repositories/orgapacheflume-1001/
> > > > > 
> > > > > 
> > > > > The tag to be voted on:
> > > > https://git-wip-us.apache.org/repos/asf?p=flume.git;a=commit;h=8633220df808c4cd0c13d1cf0320454a94f1ea97
> > > > > 
> > > > > Flume's KEYS file containing PGP keys we use to sign the release:
> > > > > http://www.apache.org/dist/flume/KEYS
> > > > > 
> > > > > 
> > > > > Thanks,
> > > > > Hari
> > > > > 
> > > > 
> > > > 
> > > 
> > > 
> > 
> > 
> > 
> > 
> 
> 



Re: [VOTE] Apache Flume 1.5.0 RC1

2014-05-19 Thread Hari Shreedharan
+1.  

* Verified Signatures and Checksums
* Compared LICENSE file against the libs directory in both profiles - all 
binary jars are covered by the license.
* Checked top-level files. 


Thanks,
Hari


On Sunday, May 18, 2014 at 12:22 PM, Wolfgang Hoschek wrote:

> +1 Looks good to me!
> 
> Wolfgang Hoschek
> 
> On May 17, 2014, at 8:47 PM, Hari Shreedharan  (mailto:hshreedha...@cloudera.com)> wrote:
> 
> > Flume PMC - Please vote!
> > 
> > 
> > On Wed, May 14, 2014 at 12:31 AM, Arvind Prabhakar  > (mailto:arv...@apache.org)>wrote:
> > 
> > > +1
> > > 
> > > * Verified signatures and checksums for both binary and source tarballs
> > > * Rat check looks good on source tarball
> > > * Nit: Notice file has dated header, needs to be updated but not a blocker
> > > 
> > > Regards,
> > > Arvind Prabhakar
> > > 
> > > 
> > > On Wed, May 7, 2014 at 3:28 PM, Hari Shreedharan
> > > mailto:hshreedha...@cloudera.com)>wrote:
> > > 
> > > > This is a vote for the next release of Apache Flume, version 1.5.0. We
> > > are
> > > > voting on release candidate RC1.
> > > > 
> > > > It fixes the following issues:
> > > > http://s.apache.org/4eQ
> > > > 
> > > > *** Please cast your vote within the next 72 hours ***
> > > > 
> > > > The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5,
> > > > *.sha1) for the source and binary artifacts can be found here:
> > > > https://people.apache.org/~hshreedharan/apache-flume-1.5.0-rc1/
> > > > 
> > > > Maven staging repo:
> > > https://repository.apache.org/content/repositories/orgapacheflume-1001/
> > > > 
> > > > 
> > > > The tag to be voted on:
> > > https://git-wip-us.apache.org/repos/asf?p=flume.git;a=commit;h=8633220df808c4cd0c13d1cf0320454a94f1ea97
> > > > 
> > > > Flume's KEYS file containing PGP keys we use to sign the release:
> > > > http://www.apache.org/dist/flume/KEYS
> > > > 
> > > > 
> > > > Thanks,
> > > > Hari
> > > > 
> > > 
> > > 
> > 
> > 
> 
> 
> 




Re: [VOTE] Apache Flume 1.5.0 RC1

2014-05-18 Thread Wolfgang Hoschek
+1 Looks good to me!

Wolfgang Hoschek

On May 17, 2014, at 8:47 PM, Hari Shreedharan  wrote:

> Flume PMC - Please vote!
> 
> 
> On Wed, May 14, 2014 at 12:31 AM, Arvind Prabhakar wrote:
> 
>> +1
>> 
>> * Verified signatures and checksums for both binary and source tarballs
>> * Rat check looks good on source tarball
>> * Nit: Notice file has dated header, needs to be updated but not a blocker
>> 
>> Regards,
>> Arvind Prabhakar
>> 
>> 
>> On Wed, May 7, 2014 at 3:28 PM, Hari Shreedharan
>> wrote:
>> 
>>> This is a vote for the next release of Apache Flume, version 1.5.0. We
>> are
>>> voting on release candidate RC1.
>>> 
>>> It fixes the following issues:
>>>  http://s.apache.org/4eQ
>>> 
>>> *** Please cast your vote within the next 72 hours ***
>>> 
>>> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5,
>>> *.sha1) for the source and binary artifacts can be found here:
>>>   https://people.apache.org/~hshreedharan/apache-flume-1.5.0-rc1/
>>> 
>>> Maven staging repo:
>>> 
>> https://repository.apache.org/content/repositories/orgapacheflume-1001/
>>> 
>>> 
>>> The tag to be voted on:
>>> 
>>> 
>>> 
>> https://git-wip-us.apache.org/repos/asf?p=flume.git;a=commit;h=8633220df808c4cd0c13d1cf0320454a94f1ea97
>>> 
>>> Flume's KEYS file containing PGP keys we use to sign the release:
>>>  http://www.apache.org/dist/flume/KEYS
>>> 
>>> 
>>> Thanks,
>>> Hari
>>> 
>> 



Re: [VOTE] Apache Flume 1.5.0 RC1

2014-05-17 Thread Hari Shreedharan
Flume PMC - Please vote!


On Wed, May 14, 2014 at 12:31 AM, Arvind Prabhakar wrote:

> +1
>
> * Verified signatures and checksums for both binary and source tarballs
> * Rat check looks good on source tarball
> * Nit: Notice file has dated header, needs to be updated but not a blocker
>
> Regards,
> Arvind Prabhakar
>
>
> On Wed, May 7, 2014 at 3:28 PM, Hari Shreedharan
> wrote:
>
> > This is a vote for the next release of Apache Flume, version 1.5.0. We
> are
> > voting on release candidate RC1.
> >
> > It fixes the following issues:
> >   http://s.apache.org/4eQ
> >
> > *** Please cast your vote within the next 72 hours ***
> >
> > The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5,
> > *.sha1) for the source and binary artifacts can be found here:
> >https://people.apache.org/~hshreedharan/apache-flume-1.5.0-rc1/
> >
> > Maven staging repo:
> >
> https://repository.apache.org/content/repositories/orgapacheflume-1001/
> >
> >
> > The tag to be voted on:
> >
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=flume.git;a=commit;h=8633220df808c4cd0c13d1cf0320454a94f1ea97
> >
> > Flume's KEYS file containing PGP keys we use to sign the release:
> >   http://www.apache.org/dist/flume/KEYS
> >
> >
> > Thanks,
> > Hari
> >
>


[VOTE] Apache Flume 1.5.0 RC1

2014-05-15 Thread Hari Shreedharan
This is a vote for the next release of Apache Flume, version 1.5.0. We are
voting on release candidate RC1.

It fixes the following issues:
  http://s.apache.org/4eQ

*** Please cast your vote within the next 72 hours ***

The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5,
*.sha1) for the source and binary artifacts can be found here:
   https://people.apache.org/~hshreedharan/apache-flume-1.5.0-rc1/

Maven staging repo:
  https://repository.apache.org/content/repositories/orgapacheflume-1001/


The tag to be voted on:

https://git-wip-us.apache.org/repos/asf?p=flume.git;a=commit;h=8633220df808c4cd0c13d1cf0320454a94f1ea97

Flume's KEYS file containing PGP keys we use to sign the release:
  http://www.apache.org/dist/flume/KEYS


Thanks,
Hari


Re: [VOTE] Apache Flume 1.5.0 RC1

2014-05-14 Thread Arvind Prabhakar
+1

* Verified signatures and checksums for both binary and source tarballs
* Rat check looks good on source tarball
* Nit: Notice file has dated header, needs to be updated but not a blocker

Regards,
Arvind Prabhakar


On Wed, May 7, 2014 at 3:28 PM, Hari Shreedharan
wrote:

> This is a vote for the next release of Apache Flume, version 1.5.0. We are
> voting on release candidate RC1.
>
> It fixes the following issues:
>   http://s.apache.org/4eQ
>
> *** Please cast your vote within the next 72 hours ***
>
> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5,
> *.sha1) for the source and binary artifacts can be found here:
>https://people.apache.org/~hshreedharan/apache-flume-1.5.0-rc1/
>
> Maven staging repo:
>   https://repository.apache.org/content/repositories/orgapacheflume-1001/
>
>
> The tag to be voted on:
>
>
> https://git-wip-us.apache.org/repos/asf?p=flume.git;a=commit;h=8633220df808c4cd0c13d1cf0320454a94f1ea97
>
> Flume's KEYS file containing PGP keys we use to sign the release:
>   http://www.apache.org/dist/flume/KEYS
>
>
> Thanks,
> Hari
>


Re: [VOTE] Apache Flume 1.5.0 RC1

2014-05-13 Thread Hari Shreedharan
Looks like the ASF email issue caused the thread to be MIA for many. Hopefully 
this message will pop this thread back up.  


Thanks,
Hari


On Tuesday, May 13, 2014 at 11:20 AM, Roshan Naik wrote:

> Sound good. I have not tried building custom hbase against hadoop2. But i
> assume this has been tried out ? in which case +1 from me.
>  
> -roshan
>  
>  
> On Mon, May 12, 2014 at 11:19 PM, Hari Shreedharan <
> hshreedha...@cloudera.com (mailto:hshreedha...@cloudera.com)> wrote:
>  
> > The original email probably went missing due to the ASF email issue.
> >  
> > As far as the Hbase sink/asynchbase issue, did you build hbase .94.2
> > against Hadoop 2? Hbase did not realize artifacts built against Hadoop 2
> > before hbase .96. If you don't have hbase 94 built against Hadoop 2, mvn
> > will pull the one available on central which is built against Hadoop 1.
> >  
> > I don't think we need to build a new RC for the doc bug. I can deploy the
> > patches docs on the website without doing another RC.
> >  
> > Also, the copyright year is not a blocker - we have released 3 times after
> > 2012.
> >  
> > Hari
> >  
> > On Monday, May 12, 2014, Roshan Naik  > (mailto:ros...@hortonworks.com)> wrote:
> >  
> > > Sidenote: For some reason I didnt receive Hari's original email
> > announcing
> > > RC1.
> > >  
> > >  
> > >  
> > > Anyway here are my observations:
> > >  
> > > - verified checksums (src & bin) - Looks good
> > > - verified builds works ok for regular build and also
> > > with -Dhadoop.profile=2 option - Looks good
> > >  
> > > Unit Tests:
> > > - Manually brought up a sample Flume agent using the binary dist - Looks
> > > good
> > > - Ran a few unit tests (SpillChannel onwards) for hadoop1 profile. -
> > >  
> >  
> > Looks
> > > good.
> > > - Ran unit tests for hadoop2 profile - *Failures in TestAsyncHBaseSink &
> > > TestHBaseSink*. Rest ok. See details below.
> > >  
> > > - Documentation: - *Noticed a few issues*.
> > > + The date in the COPYRIGHT file is 2012 .. does this need to be
> > >  
> >  
> > 2014 ?
> > > + README file : Wonder if we should we also mention the
> > > '-Dhadoop.profile=2' altnerative option for building the distro here ?
> > > + Spillable Channel has a documentation bug in the last example. It
> > > omits setting one of the variables that is essential for that example.
> > > Fault is mine. Apologies. If we agree to fix this.. Let me know i can
> > > provide a patch (its trivial) just need to add
> > > "a1.channels.c1.overflowCapacity
> > > = 0" in this last example.
> > >  
> > > -roshan
> > >  
> > >  
> > > *Test Failures Details:*
> > > > mvn -Dhadoop.profile=2 test
> > >  
> > >  
> > > *Running org.apache.flume.sink.hbase.TestAsyncHBaseSink*
> > >  
> > > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.472 sec
> > > <<< FAILURE!
> > > org.apache.flume.sink.hbase.TestAsyncHBaseSink Time elapsed: 471 sec
> > >  
> >  
> > <<<
> > > ERROR!
> > > java.lang.NoSuchMethodError:
> > >  
> >  
> > org.apache.hadoop.hdfs.MiniDFSCluster.(ILorg/apache/hadoop/conf/Configuration;IZZZLorg/apache/hadoop/hdfs/server/common/HdfsConstants$StartupOption;[Ljava/lang/String;[Ljava/lang/String;[J)V
> > > at
> >  
> > org.apache.hadoop.hbase.HBaseTestingUtility.startMiniDFSCluster(HBaseTestingUtility.java:433)
> > > at
> >  
> > org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:601)
> > > at
> >  
> > org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:557)
> > > at
> >  
> > org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:526)
> > > at
> >  
> > org.apache.flume.sink.hbase.TestAsyncHBaseSink.setUp(TestAsyncHBaseSink.java:69)
> > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > > at
> > >  
> >  
> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> > > at
> >  
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> > > at java.lang.reflect.Method.invoke(Method.java:597)
> > > at
> > >  
> >  
> > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
> > > at
> >  
> > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> > > at
> >  
> > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
> > > at
> >  
> > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)
> > > at
> >  
> > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
> > > at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
> > > at
> > >  
> >  
> > org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
> > > at
> >  
> > org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
> > > at
> >  
> > org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
> > > at sun.reflect.NativeMethodAcc

Re: [VOTE] Apache Flume 1.5.0 RC1

2014-05-13 Thread Roshan Naik
Sound good. I have not tried building custom hbase against hadoop2. But i
assume this has been tried out ? in which case +1 from me.

-roshan


On Mon, May 12, 2014 at 11:19 PM, Hari Shreedharan <
hshreedha...@cloudera.com> wrote:

> The original email probably went missing due to the ASF email issue.
>
> As far as the Hbase sink/asynchbase issue, did you build hbase .94.2
> against Hadoop 2? Hbase did not realize artifacts built against Hadoop 2
> before hbase .96. If you don't have hbase 94 built against Hadoop 2, mvn
> will pull the one available on central which is built against Hadoop 1.
>
> I don't think we need to build a new RC for the doc bug. I can deploy the
> patches docs on the website without doing another RC.
>
> Also, the copyright year is not a blocker - we have released 3 times after
> 2012.
>
> Hari
>
> On Monday, May 12, 2014, Roshan Naik  wrote:
>
> > Sidenote: For some reason I didnt receive Hari's original email
> announcing
> > RC1.
> >
> >
> >
> > Anyway here are my observations:
> >
> > - verified checksums  (src & bin) - Looks good
> > - verified builds works ok for regular build and also
> > with -Dhadoop.profile=2 option - Looks good
> >
> > Unit Tests:
> > - Manually brought up a sample Flume agent using the binary dist - Looks
> > good
> > - Ran a few unit tests (SpillChannel onwards) for hadoop1 profile. -
> Looks
> > good.
> > - Ran unit tests for hadoop2 profile -  *Failures in TestAsyncHBaseSink &
> > TestHBaseSink*. Rest ok. See details below.
> >
> > - Documentation: - *Noticed a few issues*.
> > + The date in the COPYRIGHT file is 2012 .. does this need to be
> 2014 ?
> > + README file : Wonder if we should we also mention the
> > '-Dhadoop.profile=2' altnerative option for building the distro here ?
> > + Spillable Channel has a documentation bug in the last example. It
> > omits setting one of the variables that is essential for that example.
> > Fault is mine. Apologies. If we agree to fix this.. Let me know i can
> > provide a patch (its trivial) just need to add
> > "a1.channels.c1.overflowCapacity
> > = 0" in this last example.
> >
> > -roshan
> >
> >
> > *Test Failures Details:*
> > > mvn  -Dhadoop.profile=2   test
> >
> > *Running org.apache.flume.sink.hbase.TestAsyncHBaseSink*
> >
> > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.472 sec
> > <<< FAILURE!
> > org.apache.flume.sink.hbase.TestAsyncHBaseSink  Time elapsed: 471 sec
>  <<<
> > ERROR!
> > java.lang.NoSuchMethodError:
> >
> >
> org.apache.hadoop.hdfs.MiniDFSCluster.(ILorg/apache/hadoop/conf/Configuration;IZZZLorg/apache/hadoop/hdfs/server/common/HdfsConstants$StartupOption;[Ljava/lang/String;[Ljava/lang/String;[J)V
> > at
> >
> >
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniDFSCluster(HBaseTestingUtility.java:433)
> > at
> >
> >
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:601)
> > at
> >
> >
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:557)
> > at
> >
> >
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:526)
> > at
> >
> >
> org.apache.flume.sink.hbase.TestAsyncHBaseSink.setUp(TestAsyncHBaseSink.java:69)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> >
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> > at
> >
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> > at java.lang.reflect.Method.invoke(Method.java:597)
> > at
> >
> >
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
> > at
> >
> >
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> > at
> >
> >
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
> > at
> >
> >
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)
> > at
> >
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
> > at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
> > at
> >
> >
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
> > at
> >
> >
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
> > at
> >
> >
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> >
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> > at
> >
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> > at java.lang.reflect.Method.invoke(Method.java:597)
> > at
> >
> >
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> > at
> >
> >
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> > at
> >
> >
> org.apache.maven.surefire.boot

Re: [VOTE] Apache Flume 1.5.0 RC1

2014-05-13 Thread Ashish
+1

Ran the build + test, all good


On Sun, May 11, 2014 at 10:21 PM, Jarek Jarcec Cecho wrote:

> +1
>
> * Verified checksums and signature files
> * Verified that each jar in binary tarball is in the license
> * Notice have copyright from 2012, we should update it (not a blocker in
> my mind)
> * Checked top level files (NOTICE, ...)
> * Run tests
>
> Jarcec
>
> On Wed, May 07, 2014 at 03:28:36PM -0700, Hari Shreedharan wrote:
> > This is a vote for the next release of Apache Flume, version 1.5.0. We
> are
> > voting on release candidate RC1.
> >
> > It fixes the following issues:
> >   http://s.apache.org/4eQ
> >
> > *** Please cast your vote within the next 72 hours ***
> >
> > The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5,
> > *.sha1) for the source and binary artifacts can be found here:
> >https://people.apache.org/~hshreedharan/apache-flume-1.5.0-rc1/
> >
> > Maven staging repo:
> >
> https://repository.apache.org/content/repositories/orgapacheflume-1001/
> >
> >
> > The tag to be voted on:
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=flume.git;a=commit;h=8633220df808c4cd0c13d1cf0320454a94f1ea97
> >
> > Flume's KEYS file containing PGP keys we use to sign the release:
> >   http://www.apache.org/dist/flume/KEYS
> >
> >
> > Thanks,
> > Hari
>



-- 
thanks
ashish

Blog: http://www.ashishpaliwal.com/blog
My Photo Galleries: http://www.pbase.com/ashishpaliwal


Re: [VOTE] Apache Flume 1.5.0 RC1

2014-05-12 Thread Hari Shreedharan
The original email probably went missing due to the ASF email issue.

As far as the Hbase sink/asynchbase issue, did you build hbase .94.2
against Hadoop 2? Hbase did not realize artifacts built against Hadoop 2
before hbase .96. If you don't have hbase 94 built against Hadoop 2, mvn
will pull the one available on central which is built against Hadoop 1.

I don't think we need to build a new RC for the doc bug. I can deploy the
patches docs on the website without doing another RC.

Also, the copyright year is not a blocker - we have released 3 times after
2012.

Hari

On Monday, May 12, 2014, Roshan Naik  wrote:

> Sidenote: For some reason I didnt receive Hari's original email announcing
> RC1.
>
>
>
> Anyway here are my observations:
>
> - verified checksums  (src & bin) - Looks good
> - verified builds works ok for regular build and also
> with -Dhadoop.profile=2 option - Looks good
>
> Unit Tests:
> - Manually brought up a sample Flume agent using the binary dist - Looks
> good
> - Ran a few unit tests (SpillChannel onwards) for hadoop1 profile. - Looks
> good.
> - Ran unit tests for hadoop2 profile -  *Failures in TestAsyncHBaseSink &
> TestHBaseSink*. Rest ok. See details below.
>
> - Documentation: - *Noticed a few issues*.
> + The date in the COPYRIGHT file is 2012 .. does this need to be 2014 ?
> + README file : Wonder if we should we also mention the
> '-Dhadoop.profile=2' altnerative option for building the distro here ?
> + Spillable Channel has a documentation bug in the last example. It
> omits setting one of the variables that is essential for that example.
> Fault is mine. Apologies. If we agree to fix this.. Let me know i can
> provide a patch (its trivial) just need to add
> "a1.channels.c1.overflowCapacity
> = 0" in this last example.
>
> -roshan
>
>
> *Test Failures Details:*
> > mvn  -Dhadoop.profile=2   test
>
> *Running org.apache.flume.sink.hbase.TestAsyncHBaseSink*
>
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.472 sec
> <<< FAILURE!
> org.apache.flume.sink.hbase.TestAsyncHBaseSink  Time elapsed: 471 sec  <<<
> ERROR!
> java.lang.NoSuchMethodError:
>
> org.apache.hadoop.hdfs.MiniDFSCluster.(ILorg/apache/hadoop/conf/Configuration;IZZZLorg/apache/hadoop/hdfs/server/common/HdfsConstants$StartupOption;[Ljava/lang/String;[Ljava/lang/String;[J)V
> at
>
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniDFSCluster(HBaseTestingUtility.java:433)
> at
>
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:601)
> at
>
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:557)
> at
>
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:526)
> at
>
> org.apache.flume.sink.hbase.TestAsyncHBaseSink.setUp(TestAsyncHBaseSink.java:69)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
>
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
> at
>
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at
>
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
> at
>
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
> at
>
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
> at
>
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
> at
>
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
>
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at
>
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at
>
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at
>
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
>
> *Running org.apache.flume.sink.hbase.TestHBaseSink*
>
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.465 sec
> <<< FAILURE!
> org.apache.flume.sink.hbase.TestHBaseSink  Time elapsed: 464 sec  <<<
> ERROR!
> java.lang.NoSuchMethodError:
>
> org.apache.hadoop.hdfs.MiniDF

Re: [VOTE] Apache Flume 1.5.0 RC1

2014-05-12 Thread Roshan Naik
Sidenote: For some reason I didnt receive Hari's original email announcing
RC1.



Anyway here are my observations:

- verified checksums  (src & bin) - Looks good
- verified builds works ok for regular build and also
with -Dhadoop.profile=2 option - Looks good

Unit Tests:
- Manually brought up a sample Flume agent using the binary dist - Looks
good
- Ran a few unit tests (SpillChannel onwards) for hadoop1 profile. - Looks
good.
- Ran unit tests for hadoop2 profile -  *Failures in TestAsyncHBaseSink &
TestHBaseSink*. Rest ok. See details below.

- Documentation: - *Noticed a few issues*.
+ The date in the COPYRIGHT file is 2012 .. does this need to be 2014 ?
+ README file : Wonder if we should we also mention the
'-Dhadoop.profile=2' altnerative option for building the distro here ?
+ Spillable Channel has a documentation bug in the last example. It
omits setting one of the variables that is essential for that example.
Fault is mine. Apologies. If we agree to fix this.. Let me know i can
provide a patch (its trivial) just need to add "a1.channels.c1.overflowCapacity
= 0" in this last example.

-roshan


*Test Failures Details:*
> mvn  -Dhadoop.profile=2   test

*Running org.apache.flume.sink.hbase.TestAsyncHBaseSink*

Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.472 sec
<<< FAILURE!
org.apache.flume.sink.hbase.TestAsyncHBaseSink  Time elapsed: 471 sec  <<<
ERROR!
java.lang.NoSuchMethodError:
org.apache.hadoop.hdfs.MiniDFSCluster.(ILorg/apache/hadoop/conf/Configuration;IZZZLorg/apache/hadoop/hdfs/server/common/HdfsConstants$StartupOption;[Ljava/lang/String;[Ljava/lang/String;[J)V
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniDFSCluster(HBaseTestingUtility.java:433)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:601)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:557)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:526)
at
org.apache.flume.sink.hbase.TestAsyncHBaseSink.setUp(TestAsyncHBaseSink.java:69)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)

*Running org.apache.flume.sink.hbase.TestHBaseSink*

Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.465 sec
<<< FAILURE!
org.apache.flume.sink.hbase.TestHBaseSink  Time elapsed: 464 sec  <<< ERROR!
java.lang.NoSuchMethodError:
org.apache.hadoop.hdfs.MiniDFSCluster.(ILorg/apache/hadoop/conf/Configuration;IZZZLorg/apache/hadoop/hdfs/server/common/HdfsConstants$StartupOption;[Ljava/lang/String;[Ljava/lang/String;[J)V
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniDFSCluster(HBaseTestingUtility.java:433)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:601)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:557)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:526)
at
org.apache.flume.sink.hbase.TestHBaseSink.setUpOnce(TestHBaseSink.java:81)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at

Re: [VOTE] Apache Flume 1.5.0 RC1

2014-05-11 Thread Jarek Jarcec Cecho
+1

* Verified checksums and signature files
* Verified that each jar in binary tarball is in the license
* Notice have copyright from 2012, we should update it (not a blocker in my 
mind)
* Checked top level files (NOTICE, ...)
* Run tests

Jarcec

On Wed, May 07, 2014 at 03:28:36PM -0700, Hari Shreedharan wrote:
> This is a vote for the next release of Apache Flume, version 1.5.0. We are
> voting on release candidate RC1.
> 
> It fixes the following issues:
>   http://s.apache.org/4eQ
> 
> *** Please cast your vote within the next 72 hours ***
> 
> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5,
> *.sha1) for the source and binary artifacts can be found here:
>https://people.apache.org/~hshreedharan/apache-flume-1.5.0-rc1/
> 
> Maven staging repo:
>   https://repository.apache.org/content/repositories/orgapacheflume-1001/
> 
> 
> The tag to be voted on:
> 
> https://git-wip-us.apache.org/repos/asf?p=flume.git;a=commit;h=8633220df808c4cd0c13d1cf0320454a94f1ea97
> 
> Flume's KEYS file containing PGP keys we use to sign the release:
>   http://www.apache.org/dist/flume/KEYS
> 
> 
> Thanks,
> Hari


signature.asc
Description: Digital signature