You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2026/01/31 19:52:00 UTC

[jira] [Commented] (SOLR-18071) Export Writer should optionally support stored-only fields

    [ https://issues.apache.org/jira/browse/SOLR-18071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18055676#comment-18055676 ] 

ASF subversion and git services commented on SOLR-18071:
--------------------------------------------------------

Commit 45adb11a9eaed2456244cd03d573d8daf10d92e1 in solr's branch refs/heads/main from Luke Kot-Zaniewski
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=45adb11a9ea ]

SOLR-18071: Support stored fields in ExportWriter (#4053)

 via a new includeStoredFields parameter

> Export Writer should optionally support stored-only fields
> ----------------------------------------------------------
>
>                 Key: SOLR-18071
>                 URL: https://issues.apache.org/jira/browse/SOLR-18071
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Luke Kot-Zaniewski
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 6h 20m
>  Remaining Estimate: 0h
>
> Add a new includeStoredFields parameter to the /export handler to retrieve stored-only fields (fields without DocValues) alongside DocValues-based fields. The /export handler currently only supports fields with DocValues enabled, as it uses a streaming/sorting approach that relies on DocValues for efficient iteration. However, there are valid use cases where users need to include stored-only fields in export results. For instance, when storing very large text fields, DocValues may not be an option.
> The enhancement should:
>  # Add a new parameter includeStoredFields. When enabled, it should allow stored-only fields to be included in export results
>  # When a stored-only field is explicitly requested in fl without includeStoredFields=true, the handler should return an error with a hint suggesting the parameter
>  # When using glob patterns (e.g., fl=*) includeStoredFields=false (explicitly or implicitly), stored-only fields should be silently skipped. With includeStoredFields=true, stored-only fields should be included



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org