[
https://issues.apache.org/jira/browse/SOLR-8362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16341721#comment-16341721
]
Hoss Man commented on SOLR-8362:
--------------------------------
FWIW, I've created 2 related issues that folks watching this Jira may want to
look at:
* SOLR-11916 - proposes (w/patch) a SortableTextField subclass that would
provide a straightforward way for people index & search analyzed test content
while still sorting on the original string (via docValues
* SOLR-11917 - a very broad scope "hypothetical roadmap" were i've posted a lot
of brain storming related to the improving the "ease of use" to some common
usescases i've seen in dealing with text fields & analyzers that typical
involves a lot of copyField work arrounds. A big part of that issue is
discussing how to tackle configurablilty in terms of supporting docValues on
TextField and what analysis should be used there.
> Add docValues support for TextField
> -----------------------------------
>
> Key: SOLR-8362
> URL: https://issues.apache.org/jira/browse/SOLR-8362
> Project: Solr
> Issue Type: Improvement
> Reporter: Hoss Man
> Priority: Major
>
> At the last lucene/solr revolution, Toke asked a question about why TextField
> doesn't support docValues. The short answer is because no one ever added it,
> but the longer answer was because we would have to think through carefully
> the _intent_ of supporting docValues for a "tokenized" field like TextField,
> and how to support various conflicting usecases where they could be handy.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
