Hi guys 👋 We are using StarRocks heavily in production and one important thing for us is to be able to use it with Flink 2.3... There is this PR here github.com/StarRocks/starrocks-connector-for-apache-flink/pull/503 that is around since July. I have already reviewed the PR twice and I have also deployed and tested it in our testing enviroments with both Flink 1.20 and 2.3.. Can someone trigger the CI workflow and overall help us merge it please? Thanks in advance 🙏

Hi Giannis, Banmoy is the one reviewing your PR, you can pin him on GitHub.

Thanks Kate - we already did, and this is opened since July and something we really need to push for our production workloads 😅 We are happy to help address more issues in the connector, but we are missing privileges on the repo and its hard for us to push the features and fixes we need

I’ll check with Banmoy and see if he can prioritize it.

Hello 👋 I wanted to follow-up here and see if there is someone that can at least approve the workflow 😄 and help us understand what's the best way to push forward this job, as our new pipelines need the new connector and we are waiting on this.

+1 for merging this. We run StarRocks 4.0.12 in production with Flink 2.0.2. We want to replace several Routine Loads on one high-volume topic with a Flink sink. Without a Flink 2.x connector, our only option is a custom sink on a stream-load SDK built from source. An official release would let us use the supported connector instead.

yes, pretty disappointing experience tbh

@Anton Borisov @Giannis Polyzos @Tarundeep Singh Sorry for the bad experience. We’ve been busy with the Next Query. I’ll follow up on pending PRs and let you know the current progress. 🙏

@Kate Shao-Community Manager apologies if i end up being annoying, but any updates here? It’s literally a production blocker for us

@Giannis Polyzos @Anton Borisov Thanks for your patience, and sorry this has taken so long. I checked with our maintainers: Flink 2.x support is planned for the connector’s January release. The connector has its own release cycle, so it isn’t tied to a StarRocks version. I’ll keep this thread updated as the review moves forward. You can also reach the maintainer on GitHub.

@Kate Shao-Community Manager Thanks, Kate. What’s preventing even the CI workflows from being approved and run? Without that, we don’t even have basic validation feedback to work with.

@Anton Borisov Sorry for taking so long to get back to you on this PR. I’ve been tied up with other work. I’ll make it a priority over the next two weeks and give you my review feedback. In the meantime, I’ve approved the CI run.

@Luca Li there was a conflict in pom.xml, so CI didn’t run properly. Rebased, can you re-trigger, please?

done