Hi Dennis,
Thanks for sharing this implementation plan. I left a couple of comments on
the doc.
I'm not sure I have a clear picture on what exactly you're planning to do,
but it looks like a reasonable approach to me overall.
I think refactoring AccessConfig to be a more prominent and self-suffi
Added.
Thanks,
Yong Zheng
On 2025/07/18 21:18:13 Dmitri Bourlatchkov wrote:
> Adding a helper Makefile, as Yong proposed, SGTM.
>
> It would be nice to have README notes to clarify its relationship to
> Gradle, though (also commented in GH).
>
> Thanks,
> Dmitri.
>
> On Fri, Jul 11, 2025 at 1:
Thanks for the feedback in the doc!
Yes, totally agree about refactoring to reduce the many conditional chains
and "instanceof" calls. This could be a good opportunity to aim for that
refactoring while adding these features.
On Fri, Jul 18, 2025 at 2:59 PM Dmitri Bourlatchkov
wrote:
> Hi Dennis
On Fri, Jul 18, 2025 at 1:39 PM yun zou wrote:
> The purpose of a nightly Helm Chart release is to *quickly* unblock users,
> as in this issue: https://github.com/apache/polaris/issues/2030.
>
> The release process for the nightly Helm Chart would follow the same
> approach
> as the current one—
The purpose of a nightly Helm Chart release is to *quickly* unblock users,
as in this issue: https://github.com/apache/polaris/issues/2030.
The release process for the nightly Helm Chart would follow the same
approach
as the current one—the main difference is that we’d need to publish it to
a
sep
Adding a helper Makefile, as Yong proposed, SGTM.
It would be nice to have README notes to clarify its relationship to
Gradle, though (also commented in GH).
Thanks,
Dmitri.
On Fri, Jul 11, 2025 at 1:27 AM Yong Zheng wrote:
> Right now, getting set up or performing routine builds often means j
This time frame looks good to me. It would be great to have the regular
cadence of monthly releases for our users (especially as so much is coming
in)!
Do we have an idea of what sort of enhancements would likely make it into
the release? I think MinIO Support would be 100% supported at that point
Hi Team,
I'd like to bring this thread back to the top. Aside from the long-term
plan to separate
the release, are we still considering a quick nightly release to unblock
users, or are
we ok to wait for the next scheduled release (seems the next scheduled
release is around Aug 20th) ?
Be
On Mon,
Howdy folks!
Thanks for joining the community meeting about the NoSQL presentation
yesterday. In this mail, I'd love to:
1. Detail the plan of moving forward with NoSQL
2. Gather more feedback on the work
*Moving Forward*
In terms of moving forward, I'll be opening up a serial series of PRs that
Hi Yun,
What do you mean by a "quick nightly release" for helm charts? How will it
work technically?
Thanks,
Dmitri.
On Fri, Jul 18, 2025 at 11:54 AM yun zou wrote:
> Hi Team,
>
> I'd like to bring this thread back to the top. Aside from the long-term
> plan to separate
> the release, are we s
A mid-August release sounds good to me.
I've added MinIO-related issues to the milestone:
* https://github.com/apache/polaris/issues/1901
* https://github.com/apache/polaris/issues/1530
Cheers,
Dmitri.
On Fri, Jul 18, 2025 at 1:07 AM Jean-Baptiste Onofré
wrote:
> Hi folks,
>
> I propose to ha
This is based on what was mentioned in the first email
> Meanwhile, we can start to release the nightly Helm Chart as a quick
> solution for any users trying the new release with JDBC backend. Thoughts
> and volunteers for this one?
I think the proposal is to do a non-formal release for Helm Char
Sorry, I'm still not clear on the technical details of nightly helm
releases. I imagine any official release will need a vote.
If the intent of nightly helm releases is to allow end users to use them in
their deployment environments (not just for testing), I do not think it
would be a good idea du
13 matches
Mail list logo
