[
https://issues.apache.org/jira/browse/SOLR-12249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16855936#comment-16855936
]
ASF subversion and git services commented on SOLR-12249:
--------------------------------------------------------
Commit 06257c5847f8a3493a9a93be6eebb058d20be06a in lucene-solr's branch
refs/heads/branch_8x from erick
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=06257c5 ]
SOLR-12249: Better error message when grouping on a tokenized (non
SortableText) field in SolrCloud
(cherry picked from commit 7fb5b7ed357b730c93ece574d1e977ecd1268533)
> Better error message when grouping on a tokenized (non SortableText) field in
> SolrCloud
> ---------------------------------------------------------------------------------------
>
> Key: SOLR-12249
> URL: https://issues.apache.org/jira/browse/SOLR-12249
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 6.6.2, 8.0
> Reporter: Erick Erickson
> Assignee: Erick Erickson
> Priority: Minor
> Attachments: SOLR-12249.patch
>
>
> I didn't test this with master. Under the covers in stand-alone mode, the
> "min" function is silently substituted for the grouping, but that's not true
> in SorlCloud mode. I broke this JIRA out separately to discuss whether it
> _ever_ makes sense to group by a tokenized text field.
> Grouping by the min value in a field is at least consistent, but on a text
> field I don't think it makes sense.
> I propose that we explicitly dis-allow this in both stand-alone and Cloud
> mode, especially now that there's the SortableTextField.
> Comments?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
