退订
退订
退订
退订
退订
退订
退订
退订
sh_0...@126.com
退订
退订
退订
退订
退订
退订
退订
退订 获取 Outlook for iOS<https://aka.ms/o0ukef>
退订
退订
退订
退订
退订
退订
退订
退订
退订
退订
退订
退订 -- 发自新浪邮箱客户端
退订
您好： 退订！ 谢浩天
退订
退订
退订
退订
退订
退订
退订
退订
退订
退订
退订
退订
退订
退订
退订
退订
退订
退订
Re: 退订
Hi, Please send email to dev-unsubscr...@flink.apache.org <mailto:dev-unsubscr...@flink.apache.org> if you want to unsubscribe the mail from d...@flink.apache.org <mailto:d...@flink.apache.org> . Please send email to user-unsubscr...@flink.apache.org <mailto:user-unsubscr...@flink.apache.org> if you want to unsubscribe the mail from user@flink.apache.org <mailto:user@flink.apache.org> . Please send email to user-zh-unsubscr...@flink.apache.org <mailto:user-zh-unsubscr...@flink.apache.org> if you want to unsubscribe the mail from user...@flink.apache.org <mailto:user...@flink.apache.org> . You can refer[1] for more details. [1] https://flink.apache.org/community.html#mailing-lists <https://flink.apache.org/community.html#mailing-lists> Best, Leonard > 在 2021年8月31日，22:06，kindragos <6230...@163.com> 写道： > > 退订
Re: 退订
Hi, To unsubscribe emails from Flink dev mail list, send an email to dev-unsubscr...@flink.apache.org To unsubscribe emails from Flink user mail list, send an email to user-unsubscr...@flink.apache.org To unsubscribe emails from Flink user -zh mail list, send an email to user-zh-unsubscr...@flink.apache.org For more information, please go to [1]. [1] https://flink.apache.org/community.html#mailing-lists Best, JING ZHANG maozhaolin 于2021年9月26日周日 下午3:28写道： > 退订
unsubscribe (退订)
Hi, To unsubscribe emails from Flink dev mail list, send an email to dev-unsubscr...@flink.apache.org To unsubscribe emails from Flink user mail list, send an email to user-unsubscr...@flink.apache.org To unsubscribe emails from Flink user -zh mail list, send an email to user-zh-unsubscr...@flink.apache.org For more information, please go to [1]. [1] https://flink.apache.org/community.html#mailing-lists Best, Minglei | | 18717838093 | | 18717838...@126.com | 签名由网易邮箱大师定制
Re: 退订
退订请发送邮件到 user-zh-unsubscr...@flink.apache.org Best, Shammon On Thu, Feb 23, 2023 at 12:34 AM zhangjunjie wrote: > 退订 > > >
Re: 退订
Please refer to https://flink.apache.org/community/ and send the email to user-unsubscr...@flink.apache.org Best, Jane On Fri, Feb 24, 2023 at 3:17 PM zhangjunjie wrote: > 退订 > > >
Re: 退订
Please send an email to user-unsubscr...@flink.apache.org <mailto:user-unsubscr...@flink.apache.org> to unsubscribe > On Mar 3, 2023, at 8:42 AM, zhangjunjie wrote: > > 退订 > >
Re: 退订
Hi, you need send email to user-unsubscr...@flink.apache.org with any contents or subject [1] https://flink.apache.org/community.html#how-to-subscribe-to-a-mailing-list Best, Weihua On Fri, Mar 31, 2023 at 4:02 PM z wrote: > >
Re: 退订
Hi, you need send email to user-unsubscr...@flink.apache.org with any contents or subject [1] https://flink.apache.org/community.html#how-to-subscribe-to-a-mailing-list Best, Weihua > On Apr 3, 2023, at 11:15, 风 <919417...@qq.com> wrote: > > 退订
Re: 退订
退订请发送任意邮件到 user-unsubscr...@flink.apache.org，可以参考[1] [1] https://flink.apache.org/community.html#how-to-subscribe-to-a-mailing-list Best, Weihua On Mon, Apr 10, 2023 at 9:04 AM 柒朵 <1303809...@qq.com> wrote: > 退订 >
Re: 退订
退订请发送任意邮件到 user-unsubscr...@flink.apache.org，可以参考 https://flink.apache.org/community.html#how-to-subscribe-to-a-mailing-list Best, Hang 于2023年4月15日周六 11:57写道： > 退订 > > > > > -- > > 发自新浪邮箱客户端 <https://mail.sina.com.cn/client/mobile/index.php> >
Re: 退订
如果需要取消订阅 user@flink.apache.org 和 d...@flink.apache.org 邮件组，请发送任意内容的邮件到 user-unsubscr...@flink.apache.org 和 dev-unsubscr...@flink.apache.org ,参考[1] [1] https://flink.apache.org/zh/community/ On Fri, May 5, 2023 at 10:43 AM 谢浩天 wrote: > 您好： > 退订！ > > > 谢浩天 > >
Re: 退订
Please send email to user-unsubscr...@flink.apache.org if you want to unsubscribe the mail from user@flink.apache.org, and you can refer [1][2] for more details. [1] https://flink.apache.org/zh/community/#%e9%82%ae%e4%bb%b6%e5%88%97%e8%a1%a8 [2] https://flink.apache.org/community.html#mailing-lists Best, Ron 喻凯 于2023年8月30日周三 14:17写道： > >
Re: 退订
Hi Jintao, Please send an email to user-unsubscr...@flink.apache.org to unsubscribe the user mailing list. Jintao Ma 于2023年11月27日周一 09:24写道： > 退订 >
Re: 退订
Please send email to user-unsubscr...@flink.apache.org if you want to unsubscribe the mail from user@flink.apache.org, and you can refer [1][2] for more details. 请发送任意内容的邮件到 user-unsubscr...@flink.apache.org 地址来取消订阅来自 user@flink.apache.org 邮件组的邮件，你可以参考[1][2] 管理你的邮件订阅。 Best, Hang [1] https://flink.apache.org/zh/community/#%e9%82%ae%e4%bb%b6%e5%88%97%e8%a1%a8 [2] https://flink.apache.org/community.html#mailing-lists 唐大彪 于2023年12月18日周一 23:44写道： > 退订 >
Re: 退订
Please send email to user-unsubscr...@flink.apache.org and user-zh-unsubscr...@flink.apache.org if you want to unsubscribe the mail from user@flink.apache.org and user...@flink.apache.org, you can refer [1][2] for more details. Best, Junrui [1] https://flink.apache.org/zh/community/#%e9%82%ae%e4%bb%b6%e5%88%97%e8%a1%a8 [2] https://flink.apache.org/community.html#mailing-lists 李乐 于2024年1月19日周五 11:41写道： > 退订 >
RE: 退订
Please send email to user-unsubscr...@flink.apache.org if you want to unsubscribe the mail from user@flink.apache.org, and you can refer [1][2] for more details. 请发送任意内容的邮件到 user-unsubscr...@flink.apache.org 地址来取消订阅来自 user@flink.apache.org 邮件组的邮件，你可以参考[1][2] 管理你的邮件订阅。 Best, Jiabao [1] https://flink.apache.org/zh/community/#%e9%82%ae%e4%bb%b6%e5%88%97%e8%a1%a8 [2] https://flink.apache.org/community.html#mailing-lists On 2024/02/06 04:15:48 杨作青 wrote: > > >
Re: 退订/unsubscribe
退订请发送任意消息至user-unsubscr...@flink.apache.org In order to unsubscribe, please send an email to user-unsubscr...@flink.apache.org Thanks Best regards, Jing From: liangzai Date: Sun, Jun 19, 2022 at 4:37 AM Subject: Re: New KafkaSource API: Change in default behavior regarding starting offset To: bastien dine Cc: Martijn Visser , Jing Ge , user 请问这个邮件咋退订？ Replied Message >From bastien dine Date 06/15/2022 17:50 To Martijn Visser Cc Jing Ge , user Subject Re: New KafkaSource API : Change in default behavior regarding starting offset Hello Martijn, Thanks for the link to the release note, especially : "When resuming from the savepoint, please use setStartingOffsets(OffsetsInitializer.committedOffsets()) in the new KafkaSourceBuilder to transfer the offsets to the new source." So earliest is the new default We use for sure .committedOffsets - we have it by default in our custom KafkaSource builder to be sure we do not read all the previous data (earliest) What bother me is just this change in starting offset default behavior from FlinkKafkaConsumer to KafkaSource (this can lead to mistake) In fact it happens that we drop some of our kafka source state to read again from kafka committed offset, but maybe nodoby does that ^^ Anyway thanks for the focus on the release note ! Best Regards, -- Bastien DINE Data Architect / Software Engineer / Sysadmin bastiendine.io Le mer. 15 juin 2022 à 10:58, Martijn Visser a écrit : > Hi Bastien, > > When the FlinkKafkaConsumer was deprecated in 1.14.0, the release notes > included the instruction how to migrate from FlinkKafkaConsumer to > KafkaConsumer [1]. Looking at the Kafka documentation [2], there is a > section on how to upgrade to the latest connector version that I think is > outdated. I'm leaning towards copying the migration instructions to the > generic documentation. Do you think that would have sufficed? > > Best regards, > > Martijn > > [1] > https://nightlies.apache.org/flink/flink-docs-master/release-notes/flink-1.14/#deprecate-flinkkafkaconsumer > [2] > https://nightlies.apache.org/flink/flink-docs-master/docs/connectors/datastream/kafka/#upgrading-to-the-latest-connector-version > > Op wo 15 jun. 2022 om 09:22 schreef bastien dine : > >> Hello jing, >> >> This was the previous method in old Kafka consumer API, it has been >> removed in 1.15, so source code is not in master anymore, >> Yes I know for the new Offset initializer, committed offset + earliest as >> fallback can be used to have the same behavior as before >> I just wanted to know whether this is a changed behavior or I am missing >> something >> >> >> >> Bastien DINE >> Freelance >> Data Architect / Software Engineer / Sysadmin >> http://bastiendine.io >> >> >> >> Le mar. 14 juin 2022 à 23:08, Jing Ge a écrit : >> >>> Hi Bastien, >>> >>> Thanks for asking. I didn't find any call of setStartFromGroupOffsets() >>> within >>> Flink in the master branch. Could you please point out the code that >>> committed offset is used as default? >>> >>> W.r.t. the new KafkaSource, if OffsetsInitializer.committedOffsets() >>> is used, an exception will be thrown at runtime in case there is no >>> committed offset, which is useful if the user is intended to read from the >>> committed offset but something is wrong. It might feel weird if it is used >>> as default, because an exception will be thrown when users start new jobs >>> with default settings. >>> >>> Best regards, >>> Jing >>> >>> On Tue, Jun 14, 2022 at 4:15 PM bastien dine >>> wrote: >>> >>>> Hello everyone, >>>> >>>> Does someone know why the starting offset behaviour has changed in the >>>> new Kafka Source ? >>>> >>>> This is now from earliest (code in KafkaSourceBuilder), doc says : >>>> "If offsets initializer is not specified, OffsetsInitializer.earliest() >>>> will >>>> be used by default." from : >>>> https://nightlies.apache.org/flink/flink-docs-master/docs/connectors/datastream/kafka/#starting-offset >>>> >>>> Before in old FlinkKafkaConsumer it was from committed offset (i.e : >>>> setStartFromGroupOffsets() >>>> method) >>>> >>>> which match with this behaviour in new KafkaSource : : >>>> OffsetsInitializer.committedOffsets(OffsetResetStrategy.EARLIEST >>>> >>>> This change can lead to big troubles if user pay no attention to this >>>> point when migrating from old KafkaConsumer to new KafkaSource, >>>> >>>> Regards, >>>> Bastien >>>> >>>> -- >>>> >>>> Bastien DINE >>>> Data Architect / Software Engineer / Sysadmin >>>> bastiendine.io >>>> >>>
退订这个邮箱
RE: 退订这个邮箱
Please send email to user-unsubscr...@flink.apache.org if you want to unsubscribe the mail from user@flink.apache.org, and you can refer [1][2] for more details. 请发送任意内容的邮件到 user-unsubscr...@flink.apache.org 地址来取消订阅来自 user@flink.apache.org 邮件组的邮件，你可以参考[1][2] 管理你的邮件订阅。 Best, Jiabao [1] https://flink.apache.org/zh/community/#%e9%82%ae%e4%bb%b6%e5%88%97%e8%a1%a8 [2] https://flink.apache.org/community.html#mailing-lists
退订所有邮件列表
退订所有邮件列表- 原始邮件 -发件人：Teoh, Hong发送时间：2023-06-15 05:19:57收件人：Lu Niu抄送：d...@flink.apache.org;user主 题：Re: AsyncFunction vs Async SinkHi Lu,Thanks for your question. See below for my understanding.I would recommend using the Async Sink if you are writing to the external service as the final output of your job graph, and if you don’t have the ordered requirement that updates to the external system must be done before updates to some other external system within the same job graph. (More explained later).The abstraction of the Async Sink is a sink, meaning it is a terminal operator in the job graph. The abstraction is intended to simplify the writing of a sink - meaning the base implementation will handle batching, state management and rate limiting. You only need to provide the client and request structure to be used to interact with the external service. This makes writing and maintaining the sink easier (if you simply want to write to a destination with at least once processing). The AsyncFunction, as I understand it is more used for data enrichment, and is not a terminal operator in the job graph. This means the return value from the external service will continue to be passed on down the Flink Job graph. This is useful for data enrichment using the external service, or if we want to ensure the system being called in the AsyncFunction is updated BEFORE any data is written to the sinks further down the job graph.For example:Kinesis Source -> Map -> AsyncFunction (Updates DynamoDB) -> Kinesis SinkWe can be sure that the updates to DynamoDB for a particular record happens before the record is written to the Kinesis Sink.Hope the above clarifies your question!Regards,Hong On 14 Jun 2023, at 19:27, Lu Niu wrote: CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. Hi, Flink dev and usersIf I want to async write to an external service, which API shall I use, AsyncFunction or Async Sink?My understanding after checking the code are:Both APIs guarantee at least once write to external service. As both API internally stores in-flight requests in the checkpoint.Async Sink provides a batching request feature. This can be implemented with Map + AsyncFunction. Map function groups requests in batches and pass it to AsyncFunction.The batching implementation can refer to AbstractMapBundleOperator if don’t want to use state.Async Sink supports retry on failed requests. AsyncFunction also supports retry in latest flink version.Async Sink supports rate limiting, AsyncFunction doesn’t.AsyncFunction can be used to implement read-update-write. Async Sink cannot.BestLu
