On Fri, Jun 21, 2013 at 2:59 PM, Edward Sargisson wrote:
> 1. The patch to build with elasticsearch 0.90.1 is in FLUME-2049 and the
> review is here: https://reviews.apache.org/r/11581/
> I think we really need that one in Flume because otherwise anybody who
> wants to use Flume with anything oth
Hi all,
I thought I'd give an update from the ElasticSearchSink perspective. I know
that we're very keen to see a 1.4 release and will test RCs, etc. when they
come out when priorities allow.
1. The patch to build with elasticsearch 0.90.1 is in FLUME-2049 and the
review is here: https://reviews.a
Hi Roshan,
I'm OK with that if no one else has any concerns.
I'll start a separate thread with a scoping discussion.
Thanks,
Mike
On Thu, Jun 6, 2013 at 11:29 AM, Roshan Naik wrote:
> shall i go ahead and file a jira on dropping the Recoverable Memory Channel
> from 1.4 ?
>
>
> On Wed, May 2
shall i go ahead and file a jira on dropping the Recoverable Memory Channel
from 1.4 ?
On Wed, May 29, 2013 at 3:36 PM, Roshan Naik wrote:
> Perhaps this is a good point to consider dropping the Recoverable Memory
> Channel from 1.4 ... since it has been deprecated.
>
>
> On Wed, May 29, 2013
Perhaps this is a good point to consider dropping the Recoverable Memory
Channel from 1.4 ... since it has been deprecated.
On Wed, May 29, 2013 at 8:49 AM, Ralph Goers wrote:
> I don't consider this a showstopper, but it should be a learning
> experience. First, Flume should probably release m
I don't consider this a showstopper, but it should be a learning experience.
First, Flume should probably release more often. Second, where possible
deprecate stuff in one release and delete it in the next.
Ralph
On May 28, 2013, at 6:47 AM, Mike Percy wrote:
> Hmm, I wish we had agreed on th
Hmm, I wish we had agreed on the use of those APIs outside the project up
front. The interfaces log4j2 used to embed Flume were not designed to be
public. Now that we have a stable API, hopefully log4j2 can have another
release soon which takes advantage of the embedded agent APIs.
AFAICT it's not
The one concern I have is that when adding support for embedded agents some
classes were removed. This means if users of Log4j 2 try to use 1.4 they will
have problems until it is modified to use Flume 1.4. It would have been nice
to have had at least one release where both were present.
Ralph
+1 for Flume 1.4
+1 for Mike being RM.
On Wed, May 22, 2013 at 1:25 PM, Roshan Naik wrote:
> +1 for both (non binding)
>
>
> On Wed, May 22, 2013 at 10:41 AM, Mubarak Seyed wrote:
>
> > +1 for Flume 1.4
> > +1 for Mike being RM
> >
> >
> > -Mubarak
> >
> > On May 22, 2013, at 9:51 AM, Venkates
+1 for both (non binding)
On Wed, May 22, 2013 at 10:41 AM, Mubarak Seyed wrote:
> +1 for Flume 1.4
> +1 for Mike being RM
>
>
> -Mubarak
>
> On May 22, 2013, at 9:51 AM, Venkatesh S R wrote:
>
> > +1 for both! Thanks Mike!
> >
> > Best,
> > Venkatesh
> >
> >
> > On Wed, May 22, 2013 at 9:41 A
+1 for Flume 1.4
+1 for Mike being RM
-Mubarak
On May 22, 2013, at 9:51 AM, Venkatesh S R wrote:
> +1 for both! Thanks Mike!
>
> Best,
> Venkatesh
>
>
> On Wed, May 22, 2013 at 9:41 AM, Will McQueen wrote:
>
>> +1 for Flume 1.4
>> +1 for Mike being RM.
>>
>> On May 22, 2013, at 9:28 AM,
+1 for both! Thanks Mike!
Best,
Venkatesh
On Wed, May 22, 2013 at 9:41 AM, Will McQueen wrote:
> +1 for Flume 1.4
> +1 for Mike being RM.
>
> On May 22, 2013, at 9:28 AM, Edward Sargisson wrote:
>
> > Hi All,
> > +1/+1 for 1.4 and Mike.
> >
> >
> > I'm very keen to have a 1.4 for the environm
+1 for Flume 1.4
+1 for Mike being RM.
On May 22, 2013, at 9:28 AM, Edward Sargisson wrote:
> Hi All,
> +1/+1 for 1.4 and Mike.
>
>
> I'm very keen to have a 1.4 for the environments I manage. There's a lot of
> stuff I'm keen on in there.
>
> On my pre-1.4 list:
> 1. compile with elasticsea
Hi All,
+1/+1 for 1.4 and Mike.
I'm very keen to have a 1.4 for the environments I manage. There's a lot of
stuff I'm keen on in there.
On my pre-1.4 list:
1. compile with elasticsearch 0.90
2. figure out file channel state issue which is stopping Flume logging via
itself.
1. Currently we compi
+1 (non-binding) for both!
Thanks for the effort, Mike!
On May 22, 2013, at 10:09 AM, Jarek Jarcec Cecho wrote:
> +1 for releasing Flume 1.4
> +1 for Mike being the RM for this release
>
> Jarcec
>
> On Wed, May 22, 2013 at 01:02:06AM -0700, Arvind Prabhakar wrote:
>> Thanks for taking this i
+1 for releasing Flume 1.4
+1 for Mike being the RM for this release
Jarcec
On Wed, May 22, 2013 at 01:02:06AM -0700, Arvind Prabhakar wrote:
> Thanks for taking this initiative Mike!
>
> +1 for 1.4 and Mike as RM.
>
> Regards,
> Arvind Prabhakar
>
> On Wed, May 22, 2013 at 12:45 AM, Hari Shre
Thanks for taking this initiative Mike!
+1 for 1.4 and Mike as RM.
Regards,
Arvind Prabhakar
On Wed, May 22, 2013 at 12:45 AM, Hari Shreedharan <
hshreedha...@cloudera.com> wrote:
> +1 for Flume 1.4
> +1 for Mike being RM.
>
>
> Cheers,
> Hari
>
>
> On Wednesday, May 22, 2013 at 12:33 AM, Mike
+1 for Flume 1.4
+1 for Mike being RM.
Cheers,
Hari
On Wednesday, May 22, 2013 at 12:33 AM, Mike Percy wrote:
> Hi folks,
> We have had over 100 commits since 1.3.1, and a bunch of new features and
> improvements including a Thrift source, much improved ElasticSearch sink,
> support for a new
Hi folks,
We have had over 100 commits since 1.3.1, and a bunch of new features and
improvements including a Thrift source, much improved ElasticSearch sink,
support for a new plugins directory and layout, compression support in the
avro sink/source, improved checkpointing in the file channel and m
19 matches
Mail list logo
