Hmm, it isn't mentioned in the release notes because it was
unintentional that it isn't wired up anymore, it just got lost in the
very large refactor required to support vsf. I opened
https://github.com/apache/druid/pull/18637 to wire the config back up.

On Wed, Oct 15, 2025 at 1:59 AM Frank Chen <[email protected]> wrote:
>
> I notice that the following PR removed the lazy loading feature(based on
> the druid.segmentCache.lazyLoadOnStart configuration),
> but its release note does not state this, nor does it remove this
> configuration from doc.
>
> Based on the description of this PR,  I think the virtual storage feature
> is different from lazy loading, and can't replace it.
> We need to discuss how to handle this incompatibility.
>
> https://github.com/apache/druid/pull/18176
>
>
> On Fri, Oct 10, 2025 at 8:10 AM Cece Mei <[email protected]> wrote:
>
> > Quick update, the branch cut for Druid 35 has been completed yesterday
> > (October 8th), a bit earlier than originally planned. Please merge
> > items on Druid
> > 35.0.0 milestone <https://github.com/apache/druid/milestone/63> by
> > Oct.14th
> > and I'll backport them to the release.
> >
> > Thanks,
> > Cece
> >
> > On Tue, Oct 7, 2025 at 5:40 PM Cece Mei <[email protected]> wrote:
> >
> > > Hello everyone,
> > >
> > > I'd like to inform you that we're preparing to release Druid 35 soon. I'm
> > > volunteering to be the release manager for this version. I plan to do a
> > > branch cut on October.14th (next Tuesday), Pacific Time. If you have any
> > > pending PRs that you'd like to include in this release, please:
> > >
> > >    - Tag the PR with Druid 35.0.0 milestone
> > >    <https://github.com/apache/druid/milestone/63> (
> > >    https://github.com/apache/druid/milestone/63)
> > >    - Reply to this thread with the PR link
> > >    - Prioritize getting them reviewed and merged before the branch cut
> > >    date (Oct.14th)
> > >
> > >
> > > Thanks,
> > > Cece
> > >
> >

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to