[
https://issues.apache.org/jira/browse/SOLR-8220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018760#comment-15018760
]
Keith Laban commented on SOLR-8220:
-----------------------------------
It looks like calling {{createFields}} instead actually creates both the fields
we need.
I was able to change decoration to something like this
{code}
SortedDocValues sdv = leafReader.getSortedDocValues(fieldName);
for(StorableField s: schemaField.getType().createFields(schemaField,
sdv.get(docid).utf8ToString(), 1.0f)) {
if(s != null) doc.add(s);
}
{code}
which makes the the SortedDocValueField get added to the document properly, but
when trying to write the string value later on it doesn't write anything
because the implementation in {{Field}} doesn't know how to write a
{{BytesRef}}. We can override this is in {{SortedDocValueField}} but all of
that stuff is in lucene code. It looks like {{StrField#createFields}} converts
the string value to a {{BytesRef}} for the constructors of the doc values
fields.
I'm still a bit confused how [SOLR-8276] works for you, i get a NPE when trying
pull back the non-indexed/non-stored field in the current impl.
> Read field from docValues for non stored fields
> -----------------------------------------------
>
> Key: SOLR-8220
> URL: https://issues.apache.org/jira/browse/SOLR-8220
> Project: Solr
> Issue Type: Improvement
> Reporter: Keith Laban
> Attachments: SOLR-8220-ishan.patch, SOLR-8220-ishan.patch,
> SOLR-8220-ishan.patch, SOLR-8220-ishan.patch, SOLR-8220.patch,
> SOLR-8220.patch, SOLR-8220.patch, SOLR-8220.patch, SOLR-8220.patch
>
>
> Many times a value will be both stored="true" and docValues="true" which
> requires redundant data to be stored on disk. Since reading from docValues is
> both efficient and a common practice (facets, analytics, streaming, etc),
> reading values from docValues when a stored version of the field does not
> exist would be a valuable disk usage optimization.
> The only caveat with this that I can see would be for multiValued fields as
> they would always be returned sorted in the docValues approach. I believe
> this is a fair compromise.
> I've done a rough implementation for this as a field transform, but I think
> it should live closer to where stored fields are loaded in the
> SolrIndexSearcher.
> Two open questions/observations:
> 1) There doesn't seem to be a standard way to read values for docValues,
> facets, analytics, streaming, etc, all seem to be doing their own ways,
> perhaps some of this logic should be centralized.
> 2) What will the API behavior be? (Below is my proposed implementation)
> Parameters for fl:
> - fl="docValueField"
> -- return field from docValue if the field is not stored and in docValues,
> if the field is stored return it from stored fields
> - fl="*"
> -- return only stored fields
> - fl="+"
> -- return stored fields and docValue fields
> 2a - would be easiest implementation and might be sufficient for a first
> pass. 2b - is current behavior
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
