[
https://issues.apache.org/jira/browse/SOLR-18071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luke Kot-Zaniewski updated SOLR-18071:
--------------------------------------
Description:
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
was:
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
> Export Writer should support for stored-only fields via parameter
> -----------------------------------------------------------------
>
> Key: SOLR-18071
> URL: https://issues.apache.org/jira/browse/SOLR-18071
> Project: Solr
> Issue Type: Improvement
> Reporter: Luke Kot-Zaniewski
> Priority: Major
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
