[
https://issues.apache.org/jira/browse/SOLR-10349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15938249#comment-15938249
]
Joel Bernstein commented on SOLR-10349:
---------------------------------------
Looks good, maybe just needs a distributed test?
I agree this makes sense in the default response. Do we think adding this new
field will cause problems with the client? Does this just add a field or has
the response structure changed?
> Add totalTermFreq support to TermsComponent
> -------------------------------------------
>
> Key: SOLR-10349
> URL: https://issues.apache.org/jira/browse/SOLR-10349
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Shai Erera
> Assignee: Shai Erera
> Priority: Minor
> Attachments: SOLR-10349.patch, SOLR-10349.patch
>
>
> See discussion here: http://markmail.org/message/gmpmege2jpfrsp75. Both
> {{docFreq}} and {{totalTermFreq}} are already available to the
> TermsComponent, it's just that doesn't add the ttf measure to the response.
> This issue adds a new {{terms.ttf}} parameter which if set to true results in
> the following output:
> {noformat}
> <lst name="terms">
> <lst name="standardfilt">
> <lst name="shark">
> <long name="docFreq">2</long>
> <long name="totalTermFreq">2</long>
> </lst>
> ...
> {noformat}
> The reason for the new parameter is to not break backward-compatibility,
> though I wish we could always return those two measures (it doesn't cost us
> anything, the two are already available to the code). Maybe we can break the
> response in {{master}} and add this parameter only to {{6x}} as deprecated? I
> am also fine if we leave it and handle it in a separate issue.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
