You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kudu.apache.org by Grant Henke <gr...@apache.org> on 2019/09/18 18:58:19 UTC
Flume Integration Removal
Hi Kudu Developers,
Now that we have complete Java based testing utilities there is a less
reason to have all of the Kudu integrations the
Kudu repository. Instead they can be built and tested in the integration
repositories. The Apache NiFi and Apache Hive integrations
are a good example of this. We have also seen less development and usage of
the Apache Flume integration over time. Because of this, I would like to
propose removing the Flume integration from the Kudu project. And, if there
is interest, moving it to the Flume project going forward.
I had considered if we should deprecate the integration first, but I don't
think that is required given the already released versions will continue to
work with newer Kudu releases and if there is interest, the integration
will live on the the Flume repository.
What do you think? If folks agree, I am happy to follow through on the
removal process. If there is expressed interest, I am also happy to follow
through on contributing the integration to the Apache Flume project.
Thank you,
Grant
Re: Flume Integration Removal
Posted by Adar Lieber-Dembo <ad...@cloudera.com.INVALID>.
Thanks for following through with this. I +2'ed your removal patch.
Once merged let's make sure we announce the change in the 1.12.0 release notes.
On Wed, Nov 13, 2019 at 6:57 AM Grant Henke <gh...@cloudera.com.invalid> wrote:
>
> The patch for FLUME-3345 <https://issues.apache.org/jira/browse/FLUME-3345>
> was committed here:
> https://github.com/apache/flume/commit/9dafe98972a652aa1a202c6df9c08139d2bea592
>
> I rebased and updated the removal patch here:
> https://gerrit.cloudera.org/#/c/14255/
>
> On Wed, Sep 18, 2019 at 9:54 PM Grant Henke <gh...@cloudera.com> wrote:
>
> > I posted a patch to the Apache Flume project tracked here:
> > https://issues.apache.org/jira/browse/FLUME-3345
> >
> > On Wed, Sep 18, 2019 at 2:08 PM Grant Henke <gh...@cloudera.com> wrote:
> >
> >> I think we should contribute the integration to Apache Flume first
> >>
> >> before removing it from Kudu.
> >>
> >>
> >> I am okay with that. I will post a patch to the project and share it
> >> here.
> >>
> >> On Wed, Sep 18, 2019 at 2:05 PM Adar Lieber-Dembo
> >> <ad...@cloudera.com.invalid> wrote:
> >>
> >>> I agree with this (and with not needing explicit deprecation), though
> >>> I think we should contribute the integration to Apache Flume first
> >>> before removing it from Kudu.
> >>>
> >>> On Wed, Sep 18, 2019 at 11:58 AM Grant Henke <gr...@apache.org>
> >>> wrote:
> >>> >
> >>> > Hi Kudu Developers,
> >>> >
> >>> > Now that we have complete Java based testing utilities there is a less
> >>> > reason to have all of the Kudu integrations the
> >>> > Kudu repository. Instead they can be built and tested in the
> >>> integration
> >>> > repositories. The Apache NiFi and Apache Hive integrations
> >>> > are a good example of this. We have also seen less development and
> >>> usage of
> >>> > the Apache Flume integration over time. Because of this, I would like
> >>> to
> >>> > propose removing the Flume integration from the Kudu project. And, if
> >>> there
> >>> > is interest, moving it to the Flume project going forward.
> >>> >
> >>> > I had considered if we should deprecate the integration first, but I
> >>> don't
> >>> > think that is required given the already released versions will
> >>> continue to
> >>> > work with newer Kudu releases and if there is interest, the integration
> >>> > will live on the the Flume repository.
> >>> >
> >>> > What do you think? If folks agree, I am happy to follow through on the
> >>> > removal process. If there is expressed interest, I am also happy to
> >>> follow
> >>> > through on contributing the integration to the Apache Flume project.
> >>> >
> >>> > Thank you,
> >>> > Grant
> >>>
> >>
> >>
> >> --
> >> Grant Henke
> >> Software Engineer | Cloudera
> >> grant@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
> >>
> >
> >
> > --
> > Grant Henke
> > Software Engineer | Cloudera
> > grant@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
> >
>
>
> --
> Grant Henke
> Software Engineer | Cloudera
> grant@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
Re: Flume Integration Removal
Posted by Grant Henke <gh...@cloudera.com.INVALID>.
The patch for FLUME-3345 <https://issues.apache.org/jira/browse/FLUME-3345>
was committed here:
https://github.com/apache/flume/commit/9dafe98972a652aa1a202c6df9c08139d2bea592
I rebased and updated the removal patch here:
https://gerrit.cloudera.org/#/c/14255/
On Wed, Sep 18, 2019 at 9:54 PM Grant Henke <gh...@cloudera.com> wrote:
> I posted a patch to the Apache Flume project tracked here:
> https://issues.apache.org/jira/browse/FLUME-3345
>
> On Wed, Sep 18, 2019 at 2:08 PM Grant Henke <gh...@cloudera.com> wrote:
>
>> I think we should contribute the integration to Apache Flume first
>>
>> before removing it from Kudu.
>>
>>
>> I am okay with that. I will post a patch to the project and share it
>> here.
>>
>> On Wed, Sep 18, 2019 at 2:05 PM Adar Lieber-Dembo
>> <ad...@cloudera.com.invalid> wrote:
>>
>>> I agree with this (and with not needing explicit deprecation), though
>>> I think we should contribute the integration to Apache Flume first
>>> before removing it from Kudu.
>>>
>>> On Wed, Sep 18, 2019 at 11:58 AM Grant Henke <gr...@apache.org>
>>> wrote:
>>> >
>>> > Hi Kudu Developers,
>>> >
>>> > Now that we have complete Java based testing utilities there is a less
>>> > reason to have all of the Kudu integrations the
>>> > Kudu repository. Instead they can be built and tested in the
>>> integration
>>> > repositories. The Apache NiFi and Apache Hive integrations
>>> > are a good example of this. We have also seen less development and
>>> usage of
>>> > the Apache Flume integration over time. Because of this, I would like
>>> to
>>> > propose removing the Flume integration from the Kudu project. And, if
>>> there
>>> > is interest, moving it to the Flume project going forward.
>>> >
>>> > I had considered if we should deprecate the integration first, but I
>>> don't
>>> > think that is required given the already released versions will
>>> continue to
>>> > work with newer Kudu releases and if there is interest, the integration
>>> > will live on the the Flume repository.
>>> >
>>> > What do you think? If folks agree, I am happy to follow through on the
>>> > removal process. If there is expressed interest, I am also happy to
>>> follow
>>> > through on contributing the integration to the Apache Flume project.
>>> >
>>> > Thank you,
>>> > Grant
>>>
>>
>>
>> --
>> Grant Henke
>> Software Engineer | Cloudera
>> grant@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
>>
>
>
> --
> Grant Henke
> Software Engineer | Cloudera
> grant@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
>
--
Grant Henke
Software Engineer | Cloudera
grant@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
Re: Flume Integration Removal
Posted by Grant Henke <gh...@cloudera.com.INVALID>.
I posted a patch to the Apache Flume project tracked here:
https://issues.apache.org/jira/browse/FLUME-3345
On Wed, Sep 18, 2019 at 2:08 PM Grant Henke <gh...@cloudera.com> wrote:
> I think we should contribute the integration to Apache Flume first
>
> before removing it from Kudu.
>
>
> I am okay with that. I will post a patch to the project and share it
> here.
>
> On Wed, Sep 18, 2019 at 2:05 PM Adar Lieber-Dembo
> <ad...@cloudera.com.invalid> wrote:
>
>> I agree with this (and with not needing explicit deprecation), though
>> I think we should contribute the integration to Apache Flume first
>> before removing it from Kudu.
>>
>> On Wed, Sep 18, 2019 at 11:58 AM Grant Henke <gr...@apache.org>
>> wrote:
>> >
>> > Hi Kudu Developers,
>> >
>> > Now that we have complete Java based testing utilities there is a less
>> > reason to have all of the Kudu integrations the
>> > Kudu repository. Instead they can be built and tested in the integration
>> > repositories. The Apache NiFi and Apache Hive integrations
>> > are a good example of this. We have also seen less development and
>> usage of
>> > the Apache Flume integration over time. Because of this, I would like to
>> > propose removing the Flume integration from the Kudu project. And, if
>> there
>> > is interest, moving it to the Flume project going forward.
>> >
>> > I had considered if we should deprecate the integration first, but I
>> don't
>> > think that is required given the already released versions will
>> continue to
>> > work with newer Kudu releases and if there is interest, the integration
>> > will live on the the Flume repository.
>> >
>> > What do you think? If folks agree, I am happy to follow through on the
>> > removal process. If there is expressed interest, I am also happy to
>> follow
>> > through on contributing the integration to the Apache Flume project.
>> >
>> > Thank you,
>> > Grant
>>
>
>
> --
> Grant Henke
> Software Engineer | Cloudera
> grant@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
>
--
Grant Henke
Software Engineer | Cloudera
grant@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
Re: Flume Integration Removal
Posted by Grant Henke <gh...@cloudera.com.INVALID>.
>
> I think we should contribute the integration to Apache Flume first
before removing it from Kudu.
I am okay with that. I will post a patch to the project and share it here.
On Wed, Sep 18, 2019 at 2:05 PM Adar Lieber-Dembo <ad...@cloudera.com.invalid>
wrote:
> I agree with this (and with not needing explicit deprecation), though
> I think we should contribute the integration to Apache Flume first
> before removing it from Kudu.
>
> On Wed, Sep 18, 2019 at 11:58 AM Grant Henke <gr...@apache.org>
> wrote:
> >
> > Hi Kudu Developers,
> >
> > Now that we have complete Java based testing utilities there is a less
> > reason to have all of the Kudu integrations the
> > Kudu repository. Instead they can be built and tested in the integration
> > repositories. The Apache NiFi and Apache Hive integrations
> > are a good example of this. We have also seen less development and usage
> of
> > the Apache Flume integration over time. Because of this, I would like to
> > propose removing the Flume integration from the Kudu project. And, if
> there
> > is interest, moving it to the Flume project going forward.
> >
> > I had considered if we should deprecate the integration first, but I
> don't
> > think that is required given the already released versions will continue
> to
> > work with newer Kudu releases and if there is interest, the integration
> > will live on the the Flume repository.
> >
> > What do you think? If folks agree, I am happy to follow through on the
> > removal process. If there is expressed interest, I am also happy to
> follow
> > through on contributing the integration to the Apache Flume project.
> >
> > Thank you,
> > Grant
>
--
Grant Henke
Software Engineer | Cloudera
grant@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
Re: Flume Integration Removal
Posted by Adar Lieber-Dembo <ad...@cloudera.com.INVALID>.
I agree with this (and with not needing explicit deprecation), though
I think we should contribute the integration to Apache Flume first
before removing it from Kudu.
On Wed, Sep 18, 2019 at 11:58 AM Grant Henke <gr...@apache.org> wrote:
>
> Hi Kudu Developers,
>
> Now that we have complete Java based testing utilities there is a less
> reason to have all of the Kudu integrations the
> Kudu repository. Instead they can be built and tested in the integration
> repositories. The Apache NiFi and Apache Hive integrations
> are a good example of this. We have also seen less development and usage of
> the Apache Flume integration over time. Because of this, I would like to
> propose removing the Flume integration from the Kudu project. And, if there
> is interest, moving it to the Flume project going forward.
>
> I had considered if we should deprecate the integration first, but I don't
> think that is required given the already released versions will continue to
> work with newer Kudu releases and if there is interest, the integration
> will live on the the Flume repository.
>
> What do you think? If folks agree, I am happy to follow through on the
> removal process. If there is expressed interest, I am also happy to follow
> through on contributing the integration to the Apache Flume project.
>
> Thank you,
> Grant