+1
We encountered the exact same issue today.
On Fri, Jul 13, 2018 at 10:51 PM Philip Doctor <philip.doc...@physiq.com>
wrote:
> Dear Flink Users,
> I noticed my sink's `invoke` method was deprecated, so I went to update
> it, I'm a little surprised by the new method signature, especially on
> Context (copy+pasted below for ease of discussion). Shouldn't Context be
> Context<IN> not Context<T> ? based on the docs? I'm having a hard time
> understanding what's getting sent to me here in Context. Anyone have any
> insights on why these might be different ?
>
>
> /** * Interface for implementing user defined sink functionality. * * @param
> <IN> Input type parameter. */@Publicpublic interface SinkFunction<IN> extends
> Function, Serializable {
>
>
> /**
>
> * Context that {@link SinkFunction SinkFunctions } can use for getting
> additional data about * an input record. * * <p>The context is only valid for
> the duration of a * {@link SinkFunction#invoke(Object, Context)} call. Do not
> store the context and use * afterwards! * * @param <T> The type of elements
> accepted by the sink. */@Public // Interface might be extended in the future
> with additional methods.interface Context<T> {
>
>
>
> org.apache.flink/flink-streaming-java_2.11/1.5.0/784a58515da2194a2e74666e8d53d50fac8c03/flink-streaming-java_2.11-1.5.0-sources.jar!/org/apache/flink/streaming/api/functions/sink/SinkFunction.java
>
--
*Ashwin Sinha *| Data Engineer
ashwin.si...@go-mmt.com <shivam.sha...@go-mmt.com> | 9452075361
<https://www.makemytrip.com/> <https://www.goibibo.com/>
<https://www.redbus.in/>
--
::DISCLAIMER::
----------------------------------------------------------------------------------------------------------------------------------------------------
This message is intended only for the use of the addressee and may
contain information that is privileged, confidential and exempt from
disclosure under applicable law. If the reader of this message is not the
intended recipient, or the employee or agent responsible for delivering the
message to the intended recipient, you are hereby notified that any
dissemination, distribution or copying of this communication is strictly
prohibited. If you have received this e-mail in error, please notify us
immediately by return e-mail and delete this e-mail and all attachments
from your system.
