> Pulsar SQL > objections It's not objections the blocker, but volunteers.
A comparable example is that Flink firstly tried to move out connectors in 2018 and finally made it happen in 2022 (specifically, Kafka connector _today_[1]). That indicates such initiatives require heavy development. For Pulsar SQL separation, there are two major works I don't find time to finish - 1. Factor out integration utils to shared libs and release them. Flink finally has flink-connector-shared-utils[2] and flink-test-utils-junit, flink-connector-test-utils, flink-architecture-tests-test, and so on. 2. Work out a solution to handle Docker image build and release after Pulsar SQL moved out. Best, tison. [1] https://lists.apache.org/thread/vt4746r8kbnmcq7llcsvyjk4gor7gops [2] https://github.com/apache/flink-connector-shared-utils/branches Lari Hotari <lhot...@apache.org> 于2023年6月28日周三 01:12写道： > I hope we could finally resume the work on PIP-62 and continue with > the plan that was set in April 2020. > You can find old discussion threads about PIP-62 with this query: > https://lists.apache.org/list?dev@pulsar.apache.org:lte=10y:PIP-62 > > There was a discussion in July 2022 about moving Pulsar SQL to a > separate repository. [1] > Could we finally make this happen? Any objections? > > -Lari > > [1] https://lists.apache.org/thread/mflm0pb5235jjk80vol0vs7v0hvowkq8 > > On Tue, Jun 27, 2023 at 1:35 PM Enrico Olivelli <eolive...@gmail.com> > wrote: > > > > Yes we can. > > > > It was a tentative goal of creating a new workflow to build releases, > > especially for the pulsar-all docker image, that depends both on > > pulsar main repo code and on Pulsar SQL, > > that we wanted to remove from the base repository. > > > > Enrico > > > > Il giorno mar 27 giu 2023 alle ore 08:27 Asaf Mesika > > <asaf.mes...@gmail.com> ha scritto: > > > > > > Seems quite neglected >
