Thanks guys for the feedback.
@Yufei, what do you think about 0.10.0 release then ?
If we don't find a consensus on versioning, then, let's focus on the
1.0.0 release directly.
I would like to remind the purpose of the 0.10.0/1.0.0-preview release purpose:
- include binary distributions
- includ
Hi Eric
That's a good point. I think that it's something we can manage with
each tool in a separate folder/module. And, I'm sure we will find a
solution if/when the problem will occur :)
Regards
JB
On Mon, Mar 24, 2025 at 5:51 PM Eric Maynard wrote:
>
> +1 to what JB said.
>
> My concern with S
I pinged the responsible folks
On Tue, Mar 25, 2025 at 3:40 PM Dmitri Bourlatchkov
wrote:
> Thanks, Anna!
>
> I see that https://polaris.io redirects to https://polaris.apache.org/
> alright.
>
> However, http://polaris.io (no TLS) responds with a 500 error.
>
> It's a minor issue, but it would
I'm not convinced that keeping it in the main repo is necessary but I don't
think that's really
important at this time. I think it's simple enough to move the code out
later if we find that
we've run up against some other limitations of testing or releasing. So I'm
fine with beginning
in the main r
Hi Team,
Given that we are now introducing Spark Client, one thing we need to decide
is the release cycle for the Spark Plugin.
I propose to bundle the client release with Polaris main release like
Iceberg. In that way, users will be able to get the client support for new
APIs in the same release
Thanks, Anna!
I see that https://polaris.io redirects to https://polaris.apache.org/
alright.
However, http://polaris.io (no TLS) responds with a 500 error.
It's a minor issue, but it would be nice to fix it :)
Thanks,
Dmitri.
$ curl -v http://polaris.io/
* Trying 104.18.21.161:80...
*
Hi Team,
Along with the support of Generic Table, we are also introducing a Polaris
Spark client to interact with the new APIs.
To start the work, I propose to put the client in the Polaris main repo for
now. As we proceed, we can decide whether to move it to a different repo
depending on the com
In this case I think rather than a mistake, there could simply be some
ambiguity around what comments are considered blocking. For example, I'm
not sure if a comment prefixed "minor" should be considered blocking -- I
would say probably not, but someone else could interpret it differently.
To that
+1 (non-binding)
Best,
Rulin
+1
Best,
Yun
On Tue, Mar 25, 2025 at 9:22 AM Honah J. wrote:
> +1 (non-binding)
>
> Best,
> Honah (Jonas)
>
> On Tue, Mar 25, 2025 at 8:22 AM Yufei Gu wrote:
>
> > +1
> >
> > Yufei
> >
> >
> > On Tue, Mar 25, 2025 at 8:03 AM Prashant Singh
> > wrote:
> >
> > > +1 (non-binding)
> > >
> > > Bes
+1 (non-binding)
Best,
Honah (Jonas)
On Tue, Mar 25, 2025 at 8:22 AM Yufei Gu wrote:
> +1
>
> Yufei
>
>
> On Tue, Mar 25, 2025 at 8:03 AM Prashant Singh
> wrote:
>
> > +1 (non-binding)
> >
> > Best,
> > Prashant
> >
> > On Tue, Mar 25, 2025 at 7:01 AM Dmitri Bourlatchkov
> > wrote:
> >
> > >
+1
Yufei
On Tue, Mar 25, 2025 at 8:03 AM Prashant Singh
wrote:
> +1 (non-binding)
>
> Best,
> Prashant
>
> On Tue, Mar 25, 2025 at 7:01 AM Dmitri Bourlatchkov
> wrote:
>
> > +1 LGTM.
> >
> > Cheers,
> > Dmitri.
> >
> > On Tue, Mar 25, 2025 at 12:30 AM Dennis Huo wrote:
> >
> > > Hello all,
>
+1 (non-binding)
Best,
Prashant
On Tue, Mar 25, 2025 at 7:01 AM Dmitri Bourlatchkov
wrote:
> +1 LGTM.
>
> Cheers,
> Dmitri.
>
> On Tue, Mar 25, 2025 at 12:30 AM Dennis Huo wrote:
>
> > Hello all,
> >
> > We've had some productive discussion in various places on the mailing
> list,
> > in the g
+1
On Tue, Mar 25, 2025 at 4:07 AM Robert Stupp wrote:
> Hey Dennis,
>
> +1 on your proposal and thanks for especially marking it as
> "experimental, subject to change".
>
> On 25.03.25 05:28, Dennis Huo wrote:
> > Hello all,
> >
> > We've had some productive discussion in various places on the
Hey Dennis,
+1 on your proposal and thanks for especially marking it as
"experimental, subject to change".
On 25.03.25 05:28, Dennis Huo wrote:
Hello all,
We've had some productive discussion in various places on the mailing list,
in the github PR, and in the live community sync now about th
15 matches
Mail list logo