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

David Smiley commented on SOLR-8362:
------------------------------------

Hey [~hossman] I want to ensure you noticed [~mgibney]'s comment above since I 
think you've put tons of thought into this years ago -- SOLR-11917 and I think 
Michael has some similar ideas (poly field).

bq. Regarding the (minimal) Lucene changes: in order to support docValues on 
post-analysis terms, I know it would be possible to do post-analysis docValues 
entirely in Solr, by "pre-analyzing" in createFields(...), collecting tokens 
and buffering each into a separate *DocValuesField instance. But it seemed so 
straightforward (and general-purpose useful?) to do this in Lucene that I went 
that route initially. If there's interest in pursuing that approach, it could 
spin off into a separate Lucene issue.

Please do file a Lucene issue for that!  That reminds me of ideas I was kicking 
around when building the UnifiedHighlighter wherein I was considering 
alternatives to term vectors for getting the set of analyzed terms per 
document.  TVs probably make the most sense but it'd be cool to consider a 
DocValue based option.  Even better would be if the main term dictionary 
supported ordinals (e.g. BlockTreeOrdsPostingsFormat) and there could be a 
special DV impl that pointed back into a term dictionary instead of duplicating 
the same dictionary.  That would be a huge space savings.

> Add docValues support for TextField
> -----------------------------------
>
>                 Key: SOLR-8362
>                 URL: https://issues.apache.org/jira/browse/SOLR-8362
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Chris M. Hostetter
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org

Reply via email to