Re: make junit tests passing again

ketWriter.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/

Re: Review Request 53056: FLUME-2945: Bump java target version to 1.8

version "1.8.0_91". All unit tests, except for the known flaky ones, successfully passed. Thanks, Lior Zeno

Re: Review Request 53056: FLUME-2945: Bump java target version to 1.8

"1.8.0_91". All unit tests, except for the known flaky ones, successfully passed. Thanks, Lior Zeno

Re: Migrate to Log4j 2

when it will be but hope we can speed up 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 <liorz...@gmail.com> wrote:

Re: Review Request 53056: FLUME-2945: Bump java target version to 1.8

t. 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/ > --- > > (Update

Re: Review Request 53056: FLUME-2945: Bump java target version to 1.8

the known flaky ones, successfully passed. Thanks, Lior Zeno

Re: Enabling Travis-CI on Flume

onfigure it to > do 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 Zeno &

Re: Enabling Travis-CI on Flume

ote for Jenkins with github PRs. > >> I just 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 je

Re: Review Request 53056: FLUME-2945: Bump java target version to 1.8

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

Re: Review Request 53056: FLUME-2945: Bump java target version to 1.8

flaky ones, successfully passed. Thanks, Lior Zeno

Review Request 53056: FLUME-2945: Bump java target version to 1.8

--- 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

Re: Migrate to Log4j 2

> Cheers, > Attila > > On Tuesday, 18 October 2016, Lior Zeno <liorz...@gmail.com> wrote: > > > Hi All, > > > > Log4j (v1) has been EOL'ed over a year now ( > > https://blogs.apache.org/foundation/entry/apache_ > logging_services_project_ > > an

Re: Moving Developer Section of cwiki to the git repository

+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 > >

Re: [ANNOUNCE] Apache Flume 1.7.0 released

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:

Migrate to Log4j 2

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

Re: Review Request 52955: FLUME-2698 - Upgrade Jetty Version

for 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

[jira] [Updated] (FLUME-2945) Bump java target version to 1.8

[ https://issues.apache.org/jira/browse/FLUME-2945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lior Zeno updated FLUME-2945: - Description: We should move to Java 8 as a minimum requirement. # Java 7 is EOL'ed http://www.oracle.com

[jira] [Updated] (FLUME-2945) Bump java target version to 1.8

[ https://issues.apache.org/jira/browse/FLUME-2945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lior Zeno updated FLUME-2945: - Attachment: FLUME-2945-0.patch > Bump java target version to

[jira] [Assigned] (FLUME-2945) Bump java target version to 1.8

[ https://issues.apache.org/jira/browse/FLUME-2945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lior Zeno reassigned FLUME-2945: Assignee: Lior Zeno > Bump java target version to

Re: Enabling Travis-CI on Flume

function can be achieved with 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 <liorz...@gmail.com> wrote: > > There are ways to do the

Re: Improving Flume distribution packaging

not sure it'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 <liorz...@gmail.com> wrote: > > > Hi All, > > > > Currently, we distribute Flume via a tarball. I

Improving Flume distribution packaging

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

Re: Enabling Travis-CI on Flume

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

Re: Flume bechmarks

; > How can I help with setting it up? > > On Oct 13, 2016 5:20 PM, "Lior Zeno" <liorz...@gmail.com> wrote: > > > Hi All, > > > > Monitoring Flume's performance over time is an important step in every > > production-level application. Benchmarking Flume

Re: Flume bechmarks

t;s...@cloudera.com> wrote: > 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,

Flume bechmarks

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

Re: [VOTE] Release Apache Flume version 1.7.0 RC2

+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

[jira] [Commented] (FLUME-3009) Update the website for 1.7 release

[ https://issues.apache.org/jira/browse/FLUME-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15572050#comment-15572050 ] Lior Zeno commented on FLUME-3009: -- We already have a ticket for this - FLUME-2932. > Upd

[jira] [Commented] (FLUME-2994) flume-taildir-source: support for windows

[ https://issues.apache.org/jira/browse/FLUME-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15549280#comment-15549280 ] Lior Zeno commented on FLUME-2994: -- I tested the patch on Windows 10 64bit and got a test failure: {code

Re: Review Request 52511: FLUME-3003: testSourceCounter in TestSyslogUdpSource is flaky

> 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 channel but

Re: [DISCUSS] Flume 1.7 release plan

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

Re: Review Request 52511: FLUME-3003: testSourceCounter in TestSyslogUdpSource is flaky

--- 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 On Oct

[jira] [Commented] (FLUME-3000) Update morphline solr sink to use solr-6

[ https://issues.apache.org/jira/browse/FLUME-3000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15544894#comment-15544894 ] Lior Zeno commented on FLUME-3000: -- This is a duplication of FLUME-2919, which is already scheduled

Re: Review Request 52279: FLUME-2917 Provide netcat UDP source as alternative to TCP

/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

Re: Review Request 51918: FLUME-2993: Support environment variables in configuration files

--- 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

Re: Review Request 52216: Patch for FLUME-2647

(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

[jira] [Commented] (FLUME-2811) Taildir source doesn't call stop() on graceful shutdown

[ https://issues.apache.org/jira/browse/FLUME-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15518721#comment-15518721 ] Lior Zeno commented on FLUME-2811: -- Thanks [~umesh9...@gmail.com], go ahead and assign this issue

Re: [ANNOUNCE] Two new Flume committers

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

[jira] [Commented] (FLUME-2977) fix compile warnings from SAXParser

[ https://issues.apache.org/jira/browse/FLUME-2977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15458409#comment-15458409 ] Lior Zeno commented on FLUME-2977: -- Looks like this issue is fixed by a recent pull request https

[jira] [Commented] (FLUME-2977) fix compile warnings from SAXParser

[ https://issues.apache.org/jira/browse/FLUME-2977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15438887#comment-15438887 ] Lior Zeno commented on FLUME-2977: -- +1. Thanks for the patch, these warning messages are really annoying

[jira] [Commented] (FLUME-2484) NullPointerException in Kafka Sink test

[ https://issues.apache.org/jira/browse/FLUME-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15430734#comment-15430734 ] Lior Zeno commented on FLUME-2484: -- Sure, go ahead. > NullPointerException in Kafka Sink t

Re: Review Request 50562: Patch for FLUME-2797 - SyslogTcpSource uses Deprecated Class + Deprecate Syslog Source

--- 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

[jira] [Commented] (FLUME-2959) Fix issues with flume-checkstyle module

[ https://issues.apache.org/jira/browse/FLUME-2959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15396261#comment-15396261 ] Lior Zeno commented on FLUME-2959: -- [~mpercy], thanks for committing this. Do you understand why

[jira] [Commented] (FLUME-2959) flume-checkstyle module should be consistent with flume-ng prefix convention

[ https://issues.apache.org/jira/browse/FLUME-2959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15395973#comment-15395973 ] Lior Zeno commented on FLUME-2959: -- {quote} I don't think the -ng stuff is really helpful and I don't

[jira] [Updated] (FLUME-2959) flume-checkstyle module should be consistent with flume-ng prefix convention

[ https://issues.apache.org/jira/browse/FLUME-2959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lior Zeno updated FLUME-2959: - Attachment: FLUME-2959-1.patch > flume-checkstyle module should be consistent with flume-ng pre

[jira] [Commented] (FLUME-2173) Exactly once semantics for Flume

[ https://issues.apache.org/jira/browse/FLUME-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15390755#comment-15390755 ] Lior Zeno commented on FLUME-2173: -- Kafka's offset management alone is not enough. Flume may fail between

[jira] [Updated] (FLUME-2959) flume-checkstyle module should be consistent with flume-ng prefix convention

[ https://issues.apache.org/jira/browse/FLUME-2959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lior Zeno updated FLUME-2959: - Description: In FLUME-2937 we added the flume-checkstyle module to Flume. There are three minor issues

[jira] [Updated] (FLUME-2959) flume-checkstyle module should be consistent with flume-ng prefix convention

[ https://issues.apache.org/jira/browse/FLUME-2959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lior Zeno updated FLUME-2959: - Description: In FLUME-2937 we added the flume-checkstyle module to Flume. There are two minor issues

[jira] [Created] (FLUME-2959) flume-checkstyle module should be consistent with flume-ng prefix convention

Lior Zeno created FLUME-2959: Summary: flume-checkstyle module should be consistent with flume-ng prefix convention Key: FLUME-2959 URL: https://issues.apache.org/jira/browse/FLUME-2959 Project: Flume

[jira] [Updated] (FLUME-2958) Add ignorePattern for TaildirSource

[ https://issues.apache.org/jira/browse/FLUME-2958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lior Zeno updated FLUME-2958: - Fix Version/s: v1.7.0 > Add ignorePattern for TaildirSou

[jira] [Updated] (FLUME-2890) Typo in Twitter source warning

[ https://issues.apache.org/jira/browse/FLUME-2890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lior Zeno updated FLUME-2890: - Fix Version/s: v1.7.0 LGTM +1. > Typo in Twitter source warn

[jira] [Resolved] (FLUME-2641) Drop Java 6 support post Flume 1.6

[ https://issues.apache.org/jira/browse/FLUME-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lior Zeno resolved FLUME-2641. -- Resolution: Implemented Implemented by FLUME-2935. > Drop Java 6 support post Flume

[jira] [Updated] (FLUME-2436) Make hadoop-2 the default build profile

[ https://issues.apache.org/jira/browse/FLUME-2436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lior Zeno updated FLUME-2436: - Fix Version/s: v1.8.0 > Make hadoop-2 the default build prof

[jira] [Updated] (FLUME-2437) S3 Source

[ https://issues.apache.org/jira/browse/FLUME-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lior Zeno updated FLUME-2437: - Fix Version/s: v2.0.0 > S3 Source > - > > Key: FLUME-2437 >

[jira] [Resolved] (FLUME-2399) Flume 1.5.0.1 release

[ https://issues.apache.org/jira/browse/FLUME-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lior Zeno resolved FLUME-2399. -- Resolution: Fixed > Flume 1.5.0.1 release > - > > Key

[jira] [Updated] (FLUME-2333) HTTP source handler doesn't allow for responses

[ https://issues.apache.org/jira/browse/FLUME-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lior Zeno updated FLUME-2333: - Fix Version/s: v1.8.0 > HTTP source handler doesn't allow for respon

[jira] [Resolved] (FLUME-2298) Replication Channel

[ https://issues.apache.org/jira/browse/FLUME-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lior Zeno resolved FLUME-2298. -- Resolution: Implemented Implemented (using Kafka) by FLUME-2500. > Replication Chan

[jira] [Updated] (FLUME-2173) Exactly once semantics for Flume

[ https://issues.apache.org/jira/browse/FLUME-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lior Zeno updated FLUME-2173: - Fix Version/s: v2.0.0 > Exactly once semantics for Fl

[jira] [Resolved] (FLUME-2101) Flume 1.4.0 Umbrella JIRA

[ https://issues.apache.org/jira/browse/FLUME-2101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lior Zeno resolved FLUME-2101. -- Resolution: Fixed > Flume 1.4.0 Umbrella JIRA > - > >

[jira] [Updated] (FLUME-2811) Taildir source doesn't call stop() on graceful shutdown

[ https://issues.apache.org/jira/browse/FLUME-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lior Zeno updated FLUME-2811: - Fix Version/s: v1.7.0 I'm scheduling this to 1.7.0, since it's the first release to include this source

[jira] [Resolved] (FLUME-2776) 1.6 Download link not actually Flume

[ https://issues.apache.org/jira/browse/FLUME-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lior Zeno resolved FLUME-2776. -- Resolution: Not A Problem > 1.6 Download link not actually Fl

[jira] [Resolved] (FLUME-710) ExecNIOSource blocks indefinitely if an exception is encountered

[ https://issues.apache.org/jira/browse/FLUME-710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lior Zeno resolved FLUME-710. - Resolution: Invalid ExecNIOSource was a part of Flume-OG and does not exist anymore. > ExecNIOSou

[jira] [Resolved] (FLUME-1687) ApacheSolrSink

[ https://issues.apache.org/jira/browse/FLUME-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lior Zeno resolved FLUME-1687. -- Resolution: Implemented Implemented by FLUME-2070. > ApacheSolrS

[jira] [Comment Edited] (FLUME-2001) TwitterSource - An EventDrivenSource for Streaming In Data from Twitter

[ https://issues.apache.org/jira/browse/FLUME-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15390621#comment-15390621 ] Lior Zeno edited comment on FLUME-2001 at 7/23/16 8:28 AM: --- Implemented by FLUME

[jira] [Resolved] (FLUME-2031) Removal of Unused Imports from Project

[ https://issues.apache.org/jira/browse/FLUME-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lior Zeno resolved FLUME-2031. -- Resolution: Not A Problem > Removal of Unused Imports from Proj

[jira] [Commented] (FLUME-2031) Removal of Unused Imports from Project

[ https://issues.apache.org/jira/browse/FLUME-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15390620#comment-15390620 ] Lior Zeno commented on FLUME-2031: -- +1. We will optimize imports when we commit changes to a file as part

[jira] [Commented] (FLUME-2876) ElasticSearchSink: indexnameBuilderContext.putAll bug fixes

[ https://issues.apache.org/jira/browse/FLUME-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15390616#comment-15390616 ] Lior Zeno commented on FLUME-2876: -- [~yh123555], thank you for the configuration example. Maybe I

[jira] [Commented] (FLUME-2717) Add commons-io dependency into hadoop-2 profile to enable Flume 1.5 to support Hadoop 2.7

[ https://issues.apache.org/jira/browse/FLUME-2717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15387374#comment-15387374 ] Lior Zeno commented on FLUME-2717: -- Are we planning to support hadoop-2.7.0? Currently hadoop2.version

[jira] [Commented] (FLUME-2514) Some TestFileChannelRestart tests are extremely slow

[ https://issues.apache.org/jira/browse/FLUME-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15387340#comment-15387340 ] Lior Zeno commented on FLUME-2514: -- [~mpercy], do you manually resolve issues after commit

[jira] [Updated] (FLUME-2919) Upgrade the Solr version to 6.0.1

[ https://issues.apache.org/jira/browse/FLUME-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lior Zeno updated FLUME-2919: - Fix Version/s: (was: v1.7.0) v1.8.0 > Upgrade the Solr version to 6.

[jira] [Commented] (FLUME-2797) SyslogTcpSource uses Deprecated Class + Deprecate Syslog Source

[ https://issues.apache.org/jira/browse/FLUME-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15387332#comment-15387332 ] Lior Zeno commented on FLUME-2797: -- +1 for Hari's suggestion. In our documentation we also mention

[jira] [Updated] (FLUME-2340) Refactor to make room for Morphlines Elasticsearch Sink

[ https://issues.apache.org/jira/browse/FLUME-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lior Zeno updated FLUME-2340: - Fix Version/s: (was: v1.8.0) v2.0.0 > Refactor to make room for Morphli

[jira] [Updated] (FLUME-2927) Update flume docs and release notes to 1.8-SNAPSHOT in trunk

[ https://issues.apache.org/jira/browse/FLUME-2927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lior Zeno updated FLUME-2927: - Description: Updated due to the new branching model as on the mailing list. Summary: Update flume

[jira] [Updated] (FLUME-2926) Update pom.xml version in trunk

[ https://issues.apache.org/jira/browse/FLUME-2926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lior Zeno updated FLUME-2926: - Summary: Update pom.xml version in trunk (was: Update pom.xml version in trunk and 1.8 branch) Updated

[jira] [Updated] (FLUME-2340) Refactor to make room for Morphlines Elasticsearch Sink

[ https://issues.apache.org/jira/browse/FLUME-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lior Zeno updated FLUME-2340: - Fix Version/s: (was: v1.7.0) v1.8.0 > Refactor to make room for Morphli

[jira] [Comment Edited] (FLUME-2340) Refactor to make room for Morphlines Elasticsearch Sink

[ https://issues.apache.org/jira/browse/FLUME-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15385518#comment-15385518 ] Lior Zeno edited comment on FLUME-2340 at 7/20/16 8:01 AM: --- Recent elasticsearch

[jira] [Commented] (FLUME-2340) Refactor to make room for Morphlines Elasticsearch Sink

[ https://issues.apache.org/jira/browse/FLUME-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15385518#comment-15385518 ] Lior Zeno commented on FLUME-2340: -- Recent elasticsearch versions require Guava 18.0. > Refac

[jira] [Comment Edited] (FLUME-2919) Upgrade the Solr version to 6.0.1

[ https://issues.apache.org/jira/browse/FLUME-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15385501#comment-15385501 ] Lior Zeno edited comment on FLUME-2919 at 7/20/16 7:59 AM: --- Yes, we a have

[jira] [Updated] (FLUME-2921) Support Elasticsearch 2.0+

[ https://issues.apache.org/jira/browse/FLUME-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lior Zeno updated FLUME-2921: - Fix Version/s: (was: v1.7.0) v1.8.0 > Support Elasticsearch

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

Lior Zeno created FLUME-2957: Summary: Remove Guava from our public API Key: FLUME-2957 URL: https://issues.apache.org/jira/browse/FLUME-2957 Project: Flume Issue Type: Task Affects Versions

[jira] [Commented] (FLUME-2921) Support Elasticsearch 2.0+

[ https://issues.apache.org/jira/browse/FLUME-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15385506#comment-15385506 ] Lior Zeno commented on FLUME-2921: -- It could work, but I highly discourage this solution. We don't want

[jira] [Commented] (FLUME-2919) Upgrade the Solr version to 6.0.1

[ https://issues.apache.org/jira/browse/FLUME-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15385501#comment-15385501 ] Lior Zeno commented on FLUME-2919: -- Yes, we a have a ticket for that FLUME-2945. > Upgrade the S

[jira] [Commented] (FLUME-2876) ElasticSearchSink: indexnameBuilderContext.putAll bug fixes

[ https://issues.apache.org/jira/browse/FLUME-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15385496#comment-15385496 ] Lior Zeno commented on FLUME-2876: -- Could you please add a test for this case? > ElasticSearchS

Re: branhes: flume-1.7 vs trunk

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 >

[jira] [Commented] (FLUME-2921) Support Elasticsearch 2.0+

[ https://issues.apache.org/jira/browse/FLUME-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15375442#comment-15375442 ] Lior Zeno commented on FLUME-2921: -- {quote} I don't think that is possible. The client JARs for those

[jira] [Commented] (FLUME-2921) Support Elasticsearch 2.0+

[ https://issues.apache.org/jira/browse/FLUME-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15374402#comment-15374402 ] Lior Zeno commented on FLUME-2921: -- I think we should avoid a custom classloader, and simply shade/remove

Re: Review Request 49458: FLUME-2921 Support Elasticsearch 2.0+

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.apache.flume

Re: Review Request 49458: FLUME-2921 Support Elasticsearch 2.0+

ps://reviews.apache.org/r/49458/#review141781 --- On July 9, 2016, 10:13 a.m., Lior Zeno wrote: > > --- > This is an automatically generated e-mail.

Re: Review Request 49458: FLUME-2921 Support Elasticsearch 2.0+

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

Re: Build failed in Jenkins: Flume-trunk-hbase-1 #177

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.maxDirect

Re: Build failed in Jenkins: Flume-trunk-hbase-1 #177

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

[jira] [Commented] (FLUME-2921) Support Elasticsearch 2.0+

[ https://issues.apache.org/jira/browse/FLUME-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15370147#comment-15370147 ] Lior Zeno commented on FLUME-2921: -- Flume ships all of its deps, that is true. Elasticsearch

Re: Unit tests

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" <liorz...@gmail.com> wrot

Re: Unit tests

Please see https://issues.apache.org/jira/browse/FLUME-2950. On Sun, Jul 10, 2016 at 11:38 AM, Mike Percy <mpe...@apache.org> wrote: > Gotcha. Thanks for paying attention to the Jenkins runs and bringing this > up. > > Sent from my iPhone > > > On Jul 9, 2016, at

[jira] [Updated] (FLUME-2950) ReliableSpoolingFileEventReader.rollCurrentFile is broken

[ https://issues.apache.org/jira/browse/FLUME-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lior Zeno updated FLUME-2950: - Attachment: FLUME-2950-0.patch > ReliableSpoolingFileEventReader.rollCurrentFile is bro

[jira] [Assigned] (FLUME-2950) ReliableSpoolingFileEventReader.rollCurrentFile is broken

[ https://issues.apache.org/jira/browse/FLUME-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lior Zeno reassigned FLUME-2950: Assignee: Lior Zeno > ReliableSpoolingFileEventReader.rollCurrentFile is bro

[jira] [Created] (FLUME-2950) ReliableSpoolingFileEventReader.rollCurrentFile is broken

Lior Zeno created FLUME-2950: Summary: ReliableSpoolingFileEventReader.rollCurrentFile is broken Key: FLUME-2950 URL: https://issues.apache.org/jira/browse/FLUME-2950 Project: Flume Issue Type

Re: Unit tests

Nope. The recent builds on Jenkins fail because of this test. On Jul 10, 2016 7:54 AM, "Mike Percy" <mpe...@apache.org> wrote: > Only on Windows? > > Sent from my iPhone > > > On Jul 9, 2016, at 9:14 PM, Lior Zeno <liorz...@gmail.co

Re: Unit tests

We have another one: org.apache.flume.client.avro.TestSpoolingFileLineReader.testDestinationExistsAndSameFileWindows It throws IllegalStateException. On Jul 9, 2016 13:19, "Lior Zeno" <liorz...@gmail.com> wrote: > I did, please see https://issues.apache.org/jira/browse/FLUME-29

[jira] [Updated] (FLUME-2949) Flume fails to build on Windows

[ https://issues.apache.org/jira/browse/FLUME-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lior Zeno updated FLUME-2949: - Description: Now that style violations fail Flume build process, Flume fails to build on Windows

  1   2   3   4   >