Hi Yanquan, Yes, you are right about SQS - It is a MessageQueue. https://aws.amazon.com/sqs/features/
Thanks for reviewing the FLIP and valuable suggestions about adding observability. We have reviewed the above-mentioned Standardize Connector Metric FLIP [1] and added a section about it in the proposal document [2]. Please review and let us know your feedback on this. [1] https://cwiki.apache.org/confluence/display/FLINK/FLIP-33%3A+Standardize+Connector+Metrics [2] https://docs.google.com/document/d/1lreo27jNh0LkRs1Mj9B3wj3itrzMa38D4_XGryOIFks/edit#heading=h.oeqpkusea912 Thanks Saurabh & Abhi On Mon, Jul 22, 2024 at 8:53 AM Yanquan Lv <decq12y...@gmail.com> wrote: > Hi Dhingra, thanks for driving this. I am not very familiar with SQS, but > this should be some kind of message queue. So could we add metric of > currentFetchEventTimeLag > and currentEmitEventTimeLag from FLIP-33[1] in SQS source? and I want to > know what metrics do we provide in SQS source. > > [1] > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-33%3A+Standardize+Connector+Metrics > > Saurabh Singh <saurabhsingh9...@gmail.com> 于2024年7月20日周六 02:43写道： > > > Hi Fink Devs, > > > > Our team has been working on migrating various data pipelines to Flink to > > leverage the benefits of exactly-once processing, checkpointing, and > > stateful computing. We have several use cases built around the AWS SQS > > Service. For this migration, we have developed an SQS Source Connector, > > which enables us to run both stateless and stateful Flink-based jobs. > > > > We believe that this SQS Source Connector would be a valuable addition to > > the existing connector set. Therefore, we propose a FLIP to include it. > > > > For more information, please refer to the FLIP document. > > > > > > > https://docs.google.com/document/d/1lreo27jNh0LkRs1Mj9B3wj3itrzMa38D4_XGryOIFks/edit?usp=sharing > > > > Thanks > > Saurabh & Abhi > > >
