Yep!
From: Fabian Hueske mailto:fhue...@gmail.com>>
Date: Friday, October 14, 2016 at 11:00 AM
To: Shannon Carey mailto:sca...@expedia.com>>
Cc: "user@flink.apache.org<mailto:user@flink.apache.org>"
mailto:user@flink.apache.org>>
Subject: Re: [DISCUSS] Deprecat
Hi Shannon,
the plan is as follows:
We will keep the methods as they are for 1.2 but deprecate them and at the
same time we will add alternatives in an optional dependency.
In a later release, the deprecated methods will be removed and everybody
has to switch to the optional dependency.
Does tha
Speaking as a user, if you are suggesting that you will retain the
functionality but move the methods to an optional dependency, it makes sense to
me. We have used the Hadoop integration for AvroParquetInputFormat and
CqlBulkOutputFormat in Flink (although we won't be using CqlBulkOutputFormat
+1 for deprecating and the removing.
On Fri, 14 Oct 2016 at 11:38 Till Rohrmann wrote:
> Fabian's proposal sounds good to me. It would be a good first step towards
> removing our dependency on Hadoop.
>
> Thus, +1 for the changes.
>
> Cheers,
> Till
>
> On Fri, Oct 14, 2016 at 11:29 AM, Fabian H
Fabian's proposal sounds good to me. It would be a good first step towards
removing our dependency on Hadoop.
Thus, +1 for the changes.
Cheers,
Till
On Fri, Oct 14, 2016 at 11:29 AM, Fabian Hueske wrote:
> Hi everybody,
>
> I would like to propose to deprecate the utility methods to read data
