RE: Updating 3rd party dependencies

The Elasticsearch sink shouldn't be a problem. No one Is using that anyhow, since Flume is supporting version 0.9 of Elastic and Elastic is at version 7.0. best regards, Helmut -Original Message- From: Ferenc Szabo Sent: Montag, 6. Mai 2019 09:13 To: dev@flume.apache.org Subject:

What do we do with Integrations with no maintainer?

Hi all, What are we doing with integrations having no maintainer? An example is the morphline sink. It supports Solr 4.3 and Apache has already relased Solr 7.5.0. Kite SDK is at 1.1. Seems that no one is taking care of it. On the other site we are still "supporting" Elasticsearch 0.90.1,

RE: Merge of patch in Flume-3021?

Hi Mike, Did you have a chance to look at that? best regards, Helmut -Original Message- From: Wahrmann, Helmut Sent: Dienstag, 17. April 2018 18:53 To: 'dev@flume.apache.org' Subject: RE: Merge of patch in Flume-3021? Hi Mike, Did you have a chance to look into this? thanks

RE: Merge of patch in Flume-3021?

into it this week. Mike On Mon, Mar 19, 2018 at 2:41 AM, Wahrmann, Helmut <helmut.wahrm...@rsa.com> wrote: > Hi Mike, > > With the help of Ferenc, I got rid of the initial errors. > > Only one is remaining now: > > [INFO]

RE: Merge of patch in Flume-3021?

t; > from here you can fix the actual solr related test errors :) > > > > On Tue, Mar 6, 2018 at 11:56 AM, Wahrmann, Helmut > <helmut.wahrm...@rsa.com > > > wrote: > > > Hi Ferenc, > > > > Thanks for offering help. > > In agreement with Mike

RE: Merge of patch in Flume-3021?

of patch in Flume-3021? Hi Helmut, let me know what can I help You with. share your 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, > > I am

RE: Merge of patch in Flume-3021?

merge an upgrade patch, barring any serious concerns with the patch. Mike On Wed, Feb 14, 2018 at 1:47 AM, Wahrmann, Helmut <helmut.wahrm...@rsa.com> wrote: > Hi Mike, > > I won't have a problem upgrading the Solr sink to the latest version. > I am missing test environment h

RE: Merge of patch in Flume-3021?

tains > the same name in Solr7 and Solr4), which extends the SolrClient class. Hope this helps, Mike On Tue, Feb 13, 2018 at 4:41 AM, Wahrmann, Helmut <helmut.wahrm...@rsa.com> wrote: > Hi Mike, > > Thanks for the response. Would be cool if we get that sorted out. > > I've

RE: Store password for config safely?

exactly what you're looking for, but maybe he can chime in here. Mike On Mon, Feb 12, 2018 at 1:16 AM, Wahrmann, Helmut <helmut.wahrm...@rsa.com> wrote: > Hi, > > Do we have a way of storing a password safely, i.e. not in clear text? > When e.g. an Elasticsearch cluster is protected

RE: Merge of patch in Flume-3021?

dependency:tree. Regards, Mike On Mon, Feb 12, 2018 at 12:54 AM, Wahrmann, Helmut <helmut.wahrm...@rsa.com> wrote: > Hi, > > now that the blocker for FLUME-3021 is removed by committing > FLUME-2957, can we get the patch from 3021 merged to trunk? > > Thanks, > > Helmut >

Store password for config safely?

Hi, Do we have a way of storing a password safely, i.e. not in clear text? When e.g. an Elasticsearch cluster is protected by X-Pack Security, I need to specify a userid / password when connecting. The userid / password could be specified in the config, but then the password would be available

Merge of patch in Flume-3021?

Hi, now that the blocker for FLUME-3021 is removed by committing FLUME-2957, can we get the patch from 3021 merged to trunk? Thanks, Helmut

RE: Merging to trunk?

Mike Percy [mailto:mpe...@apache.org] Sent: Dienstag, 30. Jänner 2018 04:57 To: dev@flume.apache.org Subject: Re: Merging to trunk? On Mon, Jan 29, 2018 at 10:48 AM, Wahrmann, Helmut <helmut.wahrm...@rsa.com > wrote: > > I think it is not a problem to distribute the modules together if we >

RE: Merging to trunk?

her modules. > > 2018-01-27 6:14 GMT+08:00 Wahrmann, Helmut <helmut.wahrm...@rsa.com>: > > > fully agreed. > > But we shouldn't do that do support a 4 years old component. > > The goal should be to support the latest releases. > > It is ridiculous to release

Re: Merging to trunk?

nt pom and to not specify any versions in child poms. Then use the Maven enforcer plugin to make sure everything required has a declaration in the dependencyManagement section. Ralph > On Jan 26, 2018, at 8:28 AM, Wahrmann, Helmut <helmut.wahrm...@rsa.com> wrote: > > Hi Mike

RE: Merging to trunk?

flict here. I'm interested to hear your thoughts on this. Regards, Mike On Wed, Jan 24, 2018 at 7:57 AM, Wahrmann, Helmut <helmut.wahrm...@rsa.com> wrote: > Hi Mike, > > Thanks for the quick response. > > I fully agree that we need to take care about interop betw

RE: Merging to trunk?

some more on this thread. Mike On Tue, Jan 23, 2018 at 12:57 AM, Wahrmann, Helmut <helmut.wahrm...@rsa.com> wrote: > Hi, > > Who decides if/when a patch or pull request gets merged to trunk? > Reason I am asking is for the Elasticsearch support. The current code > in tr

Merging to trunk?

Hi, Who decides if/when a patch or pull request gets merged to trunk? Reason I am asking is for the Elasticsearch support. The current code in trunk does not work with ES > 2.x. Currently Elasticsearch is at 6.1. In FLUME-3021 we have several patches since March last year. I have a patched

RE: Working with Jira

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, Wahrmann, Helmut <helmut.wahrm...@rsa.

Working with Jira

Hi, In your developing guidelines you state, that if I would like to work on an issue I could assign it to myself: https://github.com/apache/flume/blob/trunk/CONTRIBUTING.md Well, I was able to create a Jira, but I am not able to assign it to myself. Seems I am missing authorization. Also,