Hello Matteo:

Considering that some users are still using the Go 1.15 version, in the
0.9.0 release, we still use the form of hard code and set the form of
pulsar-go-client to the version of 0.9.0. In order to ensure that the 0.9.0
release maintains backward compatibility, we may continue to do this for a
while. When we scrap Go 1.15, we will use the official Go embed to
dynamically configure pulsar Version information for -client-go.

--
Thanks
Xiaolong Ran

Matteo Merli <matteo.me...@gmail.com> 于2022年9月29日周四 11:33写道:

> +1
>
> It would be good to determine and document a compatibility policy to state
> which versions are going to be supported and for how long.
>
> On Wed, Sep 28, 2022 at 8:31 PM 沈家琦 <gleiphir2...@gmail.com> wrote:
>
> > +1
> > pulsar-go-client from Go 1.15 to Go 1.16
> >
> > Thanks
> >
> > r...@apache.org <ranxiaolong...@gmail.com> 于2022年9月29日周四 11:11写道:
> >
> > > Hello everyone:
> > >
> > > In the current version of pulsar-go-client, we do not support embedding
> > the
> > > version information of pulsar-go-client into
> > > Client Command to send to the Broker. Now the hard code is fixed to
> > 0.1.0.
> > > This makes it impossible for us to determine
> > > which version of pulsar-go-client the current user is using through the
> > > version information.
> > >
> > > To support this feature, the more clumsy method is described using
> > > https://github.com/apache/pulsar-client-go/pull/820.
> > > However, Go 1.16 officially supports the feature of embed (
> > > https://pkg.go.dev/embed), which supports reading the
> > > specified file directly, which seems to be a more elegant way, but this
> > > requires Go 1.16 version. Yes, the current minimum
> > > version supported by our pulsar-go-client is Go 1.15, which requires us
> > to
> > > change the minimum version of
> > > pulsar-go-client from Go 1.15 to Go 1.16.
> > >
> > > So here we start a discussion within the community to see if we can
> make
> > > this change.
> > >
> > > --
> > > Thanks
> > > Xiaolong Ran
> > >
> >
> --
> --
> Matteo Merli
> <matteo.me...@gmail.com>
>

Reply via email to