Hi Luke, I think this would be a very useful contribution, mainly since it removes one more constraint for the user to be cognizant of while using /export. I have found myself switching to cursorMark in cases where I needed to work with fields which are non-DV stored, which is a few more lines of boilerplate code, and so this would be a welcome enhancement.
Thanks, Rahul On Tue, Dec 2, 2025 at 9:52 AM Jason Gerlowski <[email protected]> wrote: > Hey Luke, > > I think that's worth contributing. Folks who come in planning to use > "/export" are likely to have DV's enabled most places, but I imagine > there's a lot of folks who only learn about "/export" after their data > is indexed and might benefit from "stored=true" being an option there. > > Do you have any sense for how using stored vs. DV fields impacts the > performance of /export? > > Best, > > Jason > > On Mon, Nov 17, 2025 at 11:02 AM Luke Kot-Zaniewski (BLOOMBERG/ 919 > 3RD A) <[email protected]> wrote: > > > > Hi All, > > > > I've come to enjoy Solr's streaming support with export writer very much, > > so when I ran into a case where I needed to extract non-dv stored fields > > I was motivated to equip ExportWriter with this power. I have a patch > that > > does this, or at least appears to do this. I would be happy to share but > > wanted to gauge interest and solicit any opinions on the mailing list > first. > > I realize DVs are usually better but this is in case you don't have DVs. > > > > Thanks, > > Luke > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
