Hi All,
I would like to make code contributions to the project, however I'm not
sure how.
I have sent a PR (FLUME-2726) on github a few days ago, but never got a
reply.
Please let me know how to properly get started.
Thanks
well:
> https://cwiki.apache.org/confluence/display/FLUME/How+to+Contribute
>
> HTH.
>
>
>
> On Wed, May 11, 2016 at 8:48 AM, Lior Zeno wrote:
> > Hi All,
> >
> > I would like to make code contributions to the project, however I'm not
> > s
I'm a newbie here, but I am eager to contribute.
Hi guys,
I think we should work together towards a new release. It has been a year
since the last release, and there are many new features that were added in
this year.
What do you think?
Lior
Anybody?
On Thu, Jun 9, 2016 at 7:24 PM, Lior Zeno wrote:
> Hi guys,
>
> I think we should work together towards a new release. It has been a year
> since the last release, and there are many new features that were added in
> this year.
> What do you think?
>
> Lior
>
Hi guys, there are many JIRA issues that are still open but are not
relevant anymore. We also have lots of unresolved issues with a submitted
patch linked to them, that we should review and commit or reject. We should
definitely reorganize our issues and discard old/irrelevant issues and
commit/rej
Hi guys, we should make the reviewing process easier and more focused on
correctness rather than style issues. I suggest enforcing our code style (
https://cwiki.apache.org/confluence/display/FLUME/Code+Formatting) at
compile time using the maven checkstyle plugin (
https://maven.apache.org/plugins
t 8:10 PM, Hari Shreedharan
wrote:
> Sound good to me. If we have a volunteer to run the release I will gladly
> help out.
> On Sat, Jun 11, 2016 at 6:54 AM Lior Zeno wrote:
>
> > Anybody?
> >
> > On Thu, Jun 9, 2016 at 7:24 PM, Lior Zeno wrote:
> >
> &g
like to help out managing Jira's but never heard back from the
> community about the graph sink that I've been working on. Does it make
> sense to do a google hangout to discuss roadmap/upcoming features?
>
> Sent from my iPhone
>
> > On Jun 11, 2016, at 10:19 AM, Lior
ps to get to a more vibrant community
and move this plugin along? I am in the initial dev and design stage for
the plugin.
Sent from my iPhone
> On Jun 12, 2016, at 2:03 AM, Lior Zeno wrote:
>
> This is absolutely true. The availability of the project's committers is
> very low
a year.
> > > > Actually I never even got to patch submit page, I just wanted
> feedback
> > > from
> > > > the community around interest for a graph sink to write or read from
> > > > neo4j/orientdb, I've started dev efforts but am worried
Thanks. I'll review this and share my comments later on today.
On Jun 13, 2016 2:30 AM, "Saikat Kanjilal" wrote:
> Motivation/Design: The graph/sink source plugin will be used to
> custom transformations to connected data and dynamically apply these
> transformations to send data to any sync, an
I'm not sure that I follow here. Can you please give a detailed use-case?
On Mon, Jun 13, 2016 at 7:20 AM, Lior Zeno wrote:
> Thanks. I'll review this and share my comments later on today.
> On Jun 13, 2016 2:30 AM, "Saikat Kanjilal" wrote:
>
>> Motivation/D
tabase
>
> Sent from my iPhone
>
> > On Jun 13, 2016, at 10:55 AM, Lior Zeno wrote:
> >
> > I'm not sure that I follow here. Can you please give a detailed use-case?
> >
> >> On Mon, Jun 13, 2016 at 7:20 AM, Lior Zeno wrote:
> >>
> >> Than
g data that is
> heterogeneous and transform that data before dumping it into the graph db.
>
> Sent from my iPhone
>
> > On Jun 13, 2016, at 11:09 AM, Lior Zeno wrote:
> >
> > I got this part. How events are linked together? Do you expect an
> adjacency
> > list incorpor
We can use the same style Kafka is using:
https://github.com/apache/kafka/blob/trunk/checkstyle/checkstyle.xml
On Mon, Jun 13, 2016 at 10:14 PM, Hari Shreedharan
wrote:
> I agree. Checkstyle is pretty useful - we should add it.
>
> On Sat, Jun 11, 2016 at 7:50 AM Lior Zeno wrote:
>
en got to patch submit page, I just wanted
>> feedback
>> > > from
>> > > > the community around interest for a graph sink to write or read from
>> > > > neo4j/orientdb, I've started dev efforts but am worried that no one
>> has
>>
issues we need to figure out before we can proceed:
> > > (a) Who can commit to the repo?
> > > (b) Who has JIRA permissions?
> > >
> > > Hari, I'll be happy to run this release, if that's fine by everyone.
> > >
> > > On Mon, Jun 1
een updates.
> On Mon, Jun 13, 2016 at 9:29 PM Saikat Kanjilal
> wrote:
>
> > Works for me, let me know how I can get involved/help.
> >
> > Sent from my iPhone
> >
> > > On Jun 13, 2016, at 9:24 PM, Lior Zeno wrote:
> > >
> > > Saikat, I s
In addition, I opened an umbrella issue for this release:
https://issues.apache.org/jira/browse/FLUME-2674
On Thu, Jun 16, 2016 at 9:35 PM, Lior Zeno wrote:
> Hi guys,
>
> We still have the following issues to resolve in order to release:
>
> https://issues.apache.org/jira/browse
Flume uses Kafka 0.9.0.1 client, it should work with 0.10 brokers.
http://kafka.apache.org/documentation.html#upgrade
On Jun 19, 2016 2:32 AM, "Joseph Aliase (JIRA)" wrote:
>
> [
> https://issues.apache.org/jira/browse/FLUME-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpa
%20%3D%20v1.7.0
>
> It looks like some of these have patches and some don't. For the ones that
> have patches, I'll try to take a look at a couple of them, unfortunately
> not all because I'm really tight on time these days.
>
> Mike
>
> On Thu, Jun 16, 2016 at 11:4
a responsibility of the graph db not flume, flume is responsible
> > > for delivering the events and has no understanding of connectivity of
> the
> > > data. The goal in using flume is to connect incoming data that is
> > > heterogeneous and transform that data before dum
; > > > wrote:
> > > >
> > > > > That's a responsibility of the graph db not flume, flume is
> responsible
> > > > > for delivering the events and has no understanding of connectivity
> of
> > > the
> &
oritize the
> JIRA and it doesn't seem like a blocker, just remove fixVersion.
>
> Mike
>
> On Mon, Jun 20, 2016 at 11:43 AM, Lior Zeno wrote:
>
> > Thanks Mike!
> >
> > BTW, what should we do with unresolved issues with fixVersion in
> unreleased
> &
Hi guys,
I know that there are a few tests that are problematic, i.e. may fail
arbitrarily. Please reply here with all tests that are known to be flaky. I
will create a jira issue for fixing that. Obviously, we won't fix all tests
in the project at this moment, but we can definitely fix that in the
MAVEN_OPTS.
On Wed, Jun 22, 2016 at 9:25 AM, Mike Percy wrote:
> The kafka source tests are extremely flaky. I haven't investigated it.
>
> Mike
>
> On Tue, Jun 21, 2016 at 9:23 PM, Lior Zeno wrote:
>
> > Hi guys,
> > I know that there are a few tests
+1.
We had a thread about it here:
http://mail-archives.apache.org/mod_mbox/flume-dev/201606.mbox/raw/%3CCAA6RhS9%2BzsJ8GNom3FSjB7MN_Zb2aWfOSXxh_RC-MuvhAfQC7g%40mail.gmail.com%3E/1
In addition, I created a jira issue for that. I hope we can add this to
1.8.0: https://issues.apache.org/jira/browse/F
Hi guys,
We have two unreleased versions 0.9.5 and 1.4.1 mentioned in jira. These
versions were never released, as far as I'm aware of. I made sure that
there aren't unresolved issues with fix version equals {0.9.5, 1.4.1}.
Therefore, we can archive/delete these from jira.
This is a simple, cosme
> On Sat, Jun 25, 2016 at 1:19 AM, Lior Zeno wrote:
>
> > Hi guys,
> >
> > We have two unreleased versions 0.9.5 and 1.4.1 mentioned in jira. These
> > versions were never released, as far as I'm aware of. I made sure that
> > there aren't unresolv
I'm not sure that we should integrate that so close to the release, since
it won't only affect next commits, but it would require modifications to
our current code that violates the style. Usually this requires a great
deal of changes to many files in the project. I suggest fixing this issue
in 1.8
ou know of any large patches that you think would have major conflicts?
> Maybe we should try to merge those first.
>
> Mike
>
> On Tue, Jun 28, 2016 at 12:34 PM, Lior Zeno wrote:
>
> > I'm not sure that we should integrate that so close to the release, since
> > it
hat is weakened. That one is super
> strict (and a bit annoying).
>
> I'll try to submit a patch for this in the next couple of days.
>
> Mike
>
> On Tue, Jun 28, 2016 at 12:54 PM, Lior Zeno wrote:
>
> > FLUME-2706, FLUME-2919 and FLUME-2921 are the largest pending
vial (more than 3 LOC) and are not overriding a method in a
base class or interface. Is it a problem too? Do we have too many non
documented public methods?
On Wed, Jun 29, 2016 at 1:47 AM, Mike Percy wrote:
> On Tue, Jun 28, 2016 at 1:46 PM, Lior Zeno wrote:
>
> > A few suggestions if
ssions.
>
> Still, let me address these comments inline...
>
> On Wed, Jun 29, 2016 at 11:26 AM, Lior Zeno wrote:
>
>> It's absolutely fine to have two passes for this.
>>
>> Still, a few notes:
>> 1. Why do we need static star imports?
>>
>
> They
Hi Mike, for some reason your commit is not available on github. Are you
aware of that?
On Thu, Jun 30, 2016 at 7:37 AM, Lior Zeno wrote:
> Thank you for this contribution, it is greatly appreciated!
>
> I'll create a new issue for a second pass, scheduled to 1.8.0.
> On Jun
and see if GItHub picks it
> > up. If that doesn't work, I'll file an INFRA ticket.
> >
> > Mike
> >
> > On Thu, Jun 30, 2016 at 10:00 AM, Lior Zeno wrote:
> >
> >> Hi Mike, for some reason your commit is not available on github. Are you
> &g
/TimeBasedIndexNameBuilderTest.java
678342a
pom.xml 694c073
Diff: https://reviews.apache.org/r/49458/diff/
Testing
---
I made sure that all unit tests (due to guava upgrade) pass successfully. The
known flaky tests may not pass, though.
Thanks,
Lior Zeno
a newer diff due to the latest
commits.
- Lior
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/49458/#review140215
----
/r/49458/diff/
Testing
---
I made sure that all unit tests (due to guava upgrade) pass successfully. The
known flaky tests may not pass, though.
Thanks,
Lior Zeno
/
Testing
---
I made sure that all unit tests (due to guava upgrade) pass successfully. The
known flaky tests may not pass, though.
Thanks,
Lior Zeno
a lot of other components so this huge version jump scares
> > me.
>
> Lior Zeno wrote:
> The minimum Guava version requires is 18.0, due to
> MoreExecutors.directExecutor. In the next elasticsearch release, Guava won't
> be a dependency anymore.
> Also, I wi
/
Testing
---
I made sure that all unit tests (due to guava upgrade) pass successfully. The
known flaky tests may not pass, though.
Thanks,
Lior Zeno
atch, thanks.
> On July 1, 2016, 3:39 p.m., Attila Simon wrote:
> > pom.xml, lines 874-879
> > <https://reviews.apache.org/r/49458/diff/3/?file=1434943#file1434943line874>
> >
> > is this change related to elastic search?
Same as above.
On July 1, 2016, 3:3
00791e4
pom.xml 85c0dc8
Diff: https://reviews.apache.org/r/49458/diff/
Testing
---
I made sure that all unit tests (due to guava upgrade) pass successfully. The
known flaky tests may not pass, though.
Thanks,
Lior Zeno
791e4
pom.xml 85c0dc8
Diff: https://reviews.apache.org/r/49458/diff/
Testing (updated)
---
I made sure that all unit tests (due to guava upgrade) pass successfully. The
known flaky tests may not pass, though.
In addition, I tested the sink against a local elasticsearch instance.
Thanks,
Lior Zeno
ed e-mail. To reply, visit:
https://reviews.apache.org/r/49458/#review140734
---
On July 2, 2016, 8:04 a.m., Lior Zeno wrote:
>
> ---
> This is an automatically generated e-ma
acc06
pom.xml b50693e
Diff: https://reviews.apache.org/r/49458/diff/
Testing
---
I made sure that all unit tests (due to guava upgrade) pass successfully. The
known flaky tests may not pass, though.
In addition, I tested the sink against a local elasticsearch instance.
Thanks,
Lior Zeno
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/49458/#review141333
---
On July 9, 2016, 10:13 a.m., Lior Zeno wrote:
>
> ---
I did, please see https://issues.apache.org/jira/browse/FLUME-2936.
On Sat, Jul 9, 2016 at 12:28 PM, Mike Percy wrote:
> Hi Lior,
>
> On Thu, Jun 23, 2016 at 8:58 AM, Lior Zeno wrote:
> >
> > 1. KafkaSource hangs in doStart at line 413:
> >it = consumer.poll(10
k and HDFSEventSink are used
> > in the same Flume agent, there must be a single version of the Guava JAR
> > loaded, and those two projects must both work with it.
>
> Lior Zeno wrote:
> This module shades Elasticsearch's Guava, but a better solution would be
>
We have another one:
org.apache.flume.client.avro.TestSpoolingFileLineReader.testDestinationExistsAndSameFileWindows
It throws IllegalStateException.
On Jul 9, 2016 13:19, "Lior Zeno" wrote:
> I did, please see https://issues.apache.org/jira/browse/FLUME-2936.
>
> On Sat, Jul
Nope. The recent builds on Jenkins fail because of this test.
On Jul 10, 2016 7:54 AM, "Mike Percy" wrote:
> Only on Windows?
>
> Sent from my iPhone
>
> > On Jul 9, 2016, at 9:14 PM, Lior Zeno wrote:
Please see https://issues.apache.org/jira/browse/FLUME-2950.
On Sun, Jul 10, 2016 at 11:38 AM, Mike Percy wrote:
> Gotcha. Thanks for paying attention to the Jenkins runs and bringing this
> up.
>
> Sent from my iPhone
>
> > On Jul 9, 2016, at 10:43 PM, Lior Zeno wro
Hi Mike, thank you for your help here.
After looking at the log of our last build, I think that Jenkins is not
started correctly with the right jvm parameters. I think it should match
our recommendation for MAVEN_OPTS.
On Jul 10, 2016 8:08 PM, "Lior Zeno" wrote:
> Ple
It's weird, not sure why the test was killed. Maybe the output file has a
few more hints.
Could you please upload the output file? I can't access it since it
requires a Jenkins user.
On Jul 12, 2016 00:51, "Mike Percy" wrote:
TestFileChannel was killed for some reason on this run.
>From https:/
t instanceof Long) {
> return (Long)result;
> }
> } catch (Exception e) {
> LOG.info("Unable to get maxDirectMemory from VM: " +
> e.getClass().getSimpleName() + ": " + e.getMessage());
> }
> // default according to VM.maxDirectMemory()
>
ally generated e-mail. To reply, visit:
https://reviews.apache.org/r/49458/#review141780
---
On July 9, 2016, 10:13 a.m., Lior Zeno wrote:
>
> ---
> This is an au
:
https://reviews.apache.org/r/49458/#review141781
---
On July 9, 2016, 10:13 a.m., Lior Zeno wrote:
>
> ---
> This is an automatically generated e-
> >
> > We would need to release Flume 2.0 to do this.
>
> Lior Zeno wrote:
> Guava is shaded, it's problematic to expose a shaded jar in the API.
I must add that I think it's a bad practice to expose a foreign namespace in
our API. Either org.apac
Many projects follow this branching model:
http://nvie.com/posts/a-successful-git-branching-model/
In my experience, it is working pretty well.
On Jul 13, 2016 23:20, "Hari Shreedharan" wrote:
> +1. Let's get rid of the 2 branch policy. I think we can now technically
> force-push to all branches,
That's very weird, it uses a custom port that is very unlikely to be used
by other programs.
What do we know about isolation? Can you tell what other jobs were running
in parallel to this build?
Or maybe it collides with another test we have?
On Jul 14, 2016 1:25 AM, "Mike Percy" wrote:
Caused b
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50562/#review146088
---
Ship it!
Ship It!
- Lior Zeno
On Aug. 18, 2016, 1:44 p.m
Congratulations Bessenyei and Jeff. Keep up your great work!
On Sep 20, 2016 01:43, "Mike Percy" wrote:
> Hi Apache Flume community,
>
> I am very happy to announce that the Flume PMC has voted to add Bessenyei
> Balázs Donát and Jeff Holoman as committers in recognition of their
> contributions
(line 656)
<https://reviews.apache.org/r/52216/#comment218205>
same here
- Lior Zeno
On Sept. 24, 2016, 12:23 p.m., Umesh Chaudhary wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> http
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/51918/#review150300
---
LGTM, should we enable this by default?
- Lior Zeno
On Sept
/NetcatUdpSource.java (line
67)
<https://reviews.apache.org/r/52279/#comment219490>
nit: s/NetcatHander/NetcatHandler
- Lior Zeno
On Oct. 3, 2016, 5:51 p.m., Tristan Stevens wrote:
>
> ---
> This is an automatically generated e
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/52511/#review151322
---
Shouldn't you simply call source.close()?
- Lior Zeno
O
I would love to see FLUME-2994 getting into the release (low-hanging fruit).
On Tue, Oct 4, 2016 at 6:01 PM, Balazs Donat Bessenyei
wrote:
> As there have been no objections, I am going to proceed with the plan
> I have outlined in my original mail.
>
> I will try to work a little more on some f
> On Oct. 4, 2016, noon, Lior Zeno wrote:
> > Shouldn't you simply call source.close()?
>
> Denes Arvay wrote:
> Thanks for the suggestion, it'd be a cleaner solution for sure but I
> tried it and unfortunately doesn't work. It might flush the netty
+1, tested simple scenarios on Windows 10 and Ubuntu 16.04.
On Thu, Oct 13, 2016 at 5:53 PM, Balazs Donat Bessenyei wrote:
> Hi All,
>
> +1 for the RC2
>
> * md5s, sha1s match
> * signatures are correct
> * mvn clean install -DskipTests runs successfully in the src ; RAT passes
> * binary works
Hi All,
Monitoring Flume's performance over time is an important step in every
production-level application. Benchmarking Flume on a nightly basis has
the following advantages:
* Better understanding of Flume's bottlenecks.
* Allow users to compare the performance of different solutions, such as
:
> Good idea! What would be required to set up something similar for Flume?
> ie initial time cost for setting up the infrastructure and periodic time
> cost to add new use-cases.
>
> Cheers,
> Attila
>
>
>
> On Thu, Oct 13, 2016 at 5:19 PM, Lior Zeno wrote:
>
>
up?
>
> On Oct 13, 2016 5:20 PM, "Lior Zeno" wrote:
>
> > Hi All,
> >
> > Monitoring Flume's performance over time is an important step in every
> > production-level application. Benchmarking Flume on a nightly basis has
> > the follow
Jenkins can do PRs as well. If we can upgrade Jenkins to 2.0, we will be
able to define the build step via Jenkinsfile which becomes very similar to
Travis.
Is there any reason to prefer Travis over Jenkins in our case?
On Thu, Oct 13, 2016 at 7:01 PM, Balazs Donat Bessenyei wrote:
> Hi All,
>
>
Hi All,
Currently, we distribute Flume via a tarball. I think we should improve and
also publish deb and rpm packages that allow running Flume as a service.
More over, container technology, such as Docker, has become increasingly
popular in last few years. Publishing an official Docker image will
#x27;s worth the effort since Flume depends on
> so many other projects like Hadoop, HBase, etc
>
> Mike
>
> On Fri, Oct 14, 2016 at 9:36 AM, Lior Zeno wrote:
>
> > Hi All,
> >
> > Currently, we distribute Flume via a tarball. I think we should improve
probably configurable to achieve similar function. However,
> I have no idea how to do such. (And could not find an example when I
> did a quick search.)
>
> Are there any disadvantages of enabling Travis on Flume?
>
>
> Thank you,
>
> Donat
>
> On Thu, Oct 13, 201
ith Jenkins and it's easy
> (+quick) to set up, I'm totally happy with that.
>
> What do we have to do to enable Jenkins builds on PR-s?
>
> On Fri, Oct 14, 2016 at 2:05 PM, Lior Zeno wrote:
> > There are ways to do the same with Jenkins, for instance, see this SO
>
You can add testShutdown(org.apache.flume.source.TestExecSource) to the
list.
java.lang.IllegalStateException: Command [ps -ef] exited with 143
at org.apache.flume.source.TestExecSource.exec(TestExecSource.java:460)
at
org.apache.flume.source.TestExecSource.testShutdown(TestExecSource.java:406)
at
bumping java version to 8. Will your patch change
much if we upgrade to the latest Jetty version?
- Lior Zeno
On Oct. 17, 2016, 7:29 p.m., Tristan Stevens wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit
Hi All,
Log4j (v1) has been EOL'ed over a year now (
https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces)
and is no longer officially supported.
I propose we migrate to Log4j 2. We can begin with using the Log4j 1.x
bridge, and then incrementally move the whole cod
Congratulations everyone! A big thank you for all of those who made this
possible.
Donat, if you could please tag the final release in the repo that would be
great. Also, mark the version as released on Jira.
On Tue, Oct 18, 2016 at 3:32 PM, Balazs Donat Bessenyei wrote:
> And thank you, Mike P
+1 for moving the whole site as well. I wish we could improve our frontend
to become a bit more appealing.
On Thu, Oct 20, 2016 at 11:53 AM, Attila Simon wrote:
> +1
> Essentially moving whole site (all web content) to scm would help
> contribution.
>
> Cheers,
> Attila
>
> On Tuesday, 18 Octobe
>
> On Tuesday, 18 October 2016, Lior Zeno wrote:
>
> > Hi All,
> >
> > Log4j (v1) has been EOL'ed over a year now (
> > https://blogs.apache.org/foundation/entry/apache_
> logging_services_project_
> > announces)
> > and is no longer officially supp
sting
---
The attached patch was tested on Ubuntu 16.04 with openjdk version "1.8.0_91".
All unit tests, except for the known flaky ones, successfully passed.
Thanks,
Lior Zeno
The attached patch was tested on Ubuntu 16.04 with openjdk version "1.8.0_91".
All unit tests, except for the known flaky ones, successfully passed.
Thanks,
Lior Zeno
nown flaky ones, successfully passed.
Thanks,
Lior Zeno
sit:
https://reviews.apache.org/r/53056/#review153413
---
On Oct. 20, 2016, 4:50 p.m., Lior Zeno wrote:
>
> ---
> This is an automatically generated e-mail. To re
st checked Mesos and the PRs are checked by Travis, or at least they
> >> experienced with it, there's a short discussion regarding to Travis at
> >> https://github.com/apache/mesos/pull/165
> >>
> >> As for the jenkins pull request job I'd be hap
the same thing, then great, let's switch when it's ready.
>
> Note that only ASF committers have access to Jenkins so non-committers will
> need to work with a committer to get it done if they want to help.
>
> Mike
>
> On Fri, Oct 21, 2016 at 3:46 PM, Lior
t for the known flaky ones, successfully passed.
Thanks,
Lior Zeno
On Oct. 21, 2016, 3:56 p.m., Lior Zeno wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/53056/
> ---
>
> (U
the
> release cycles).
>
> Cheers,
> Attila
>
>
> *Attila Simon*
> Software Engineer
> Email: s...@cloudera.com
>
> [image: Cloudera Inc.]
>
> On Thu, Oct 20, 2016 at 12:11 PM, Lior Zeno wrote:
>
>> Sure.
>>
>> First, the Log4jAppender will be depr
rsion "1.8.0_91".
All unit tests, except for the known flaky ones, successfully passed.
Thanks,
Lior Zeno
enjdk version "1.8.0_91".
All unit tests, except for the known flaky ones, successfully passed.
Thanks,
Lior Zeno
etWriter.testFileSuffixNotGiven (bessbd
> is already addressing this with https://issues.apache.
> org/jira/browse/FLUME-3002)
> org.apache.flume.source.TestExecSource.testMonitoredCounterGroup (mpercy
> is
> already addressing this with https://github.com/apache/flume/pull/72)
>
> Cheers,
>
[
https://issues.apache.org/jira/browse/FLUME-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lior Zeno updated FLUME-2726:
-
Attachment: FLUME-2726-0.patch
> Remove * imports from Kafka Chan
[
https://issues.apache.org/jira/browse/FLUME-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lior Zeno updated FLUME-2797:
-
Attachment: FLUME-2797-0.patch
> SyslogTcpSource uses Deprecated Class + Deprecate Syslog Sou
Lior Zeno created FLUME-2921:
Summary: Support Elasticsearch 2.0+
Key: FLUME-2921
URL: https://issues.apache.org/jira/browse/FLUME-2921
Project: Flume
Issue Type: Improvement
1 - 100 of 366 matches
Mail list logo
