[
https://issues.apache.org/jira/browse/SOLR-13381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17174336#comment-17174336
]
Cassandra Targett commented on SOLR-13381:
------------------------------------------
The exact strategies your addition mentions in passing are discussed in the
section on reindexing strategies,
https://lucene.apache.org/solr/guide/8_6/reindexing.html#reindexing-strategies,
in greater detail. My feeling is this note is repetition that doesn't add value.
I also don't like that it effectively becomes the 2nd sentence on the page, and
it's overly general. Reindexing doesn't always require removing all documents
first. Sometimes you _can_ just update the existing documents, but the page
says a couple times that dropping the index is the preferred approach. The only
thing I could think of adding, really, is to specifically add a sentence to the
section on reindexing strategies that repeats the point that if you change
field types, you must reindex *from scratch*.
The folks who read the page and didn't understand these from the section on
reindexing, could you perhaps share your thoughts on how we could have been
more clear? I'm just skeptical that this one sentence at the top of the page is
going to bring that point home if all the other discussion about it didn't.
> Unexpected docvalues type SORTED_NUMERIC Exception when grouping by a
> PointField facet
> --------------------------------------------------------------------------------------
>
> Key: SOLR-13381
> URL: https://issues.apache.org/jira/browse/SOLR-13381
> Project: Solr
> Issue Type: Bug
> Components: faceting
> Affects Versions: 7.0, 7.6, 7.7, 7.7.1
> Environment: solr, solrcloud
> Reporter: Zhu JiaJun
> Assignee: Erick Erickson
> Priority: Major
> Attachments: SOLR-13381.patch, SOLR-13381.patch
>
>
> Hey,
> I got an "Unexpected docvalues type SORTED_NUMERIC" exception when I perform
> group facet on an IntPointField. Debugging into the source code, the cause is
> that internally the docvalue type for PointField is "NUMERIC" (single value)
> or "SORTED_NUMERIC" (multi value), while the TermGroupFacetCollector class
> requires the facet field must have a "SORTED" or "SOTRTED_SET" docvalue type:
> [https://github.com/apache/lucene-solr/blob/2480b74887eff01f729d62a57b415d772f947c91/lucene/grouping/src/java/org/apache/lucene/search/grouping/TermGroupFacetCollector.java#L313]
>
> When I change schema for all int field to TrieIntField, the group facet then
> work. Since internally the docvalue type for TrieField is SORTED (single
> value) or SORTED_SET (multi value).
> Regarding that the "TrieField" is depreciated in Solr7, please help on this
> grouping facet issue for PointField. I also commented this issue in SOLR-7495.
>
> In addtional, all place of "${solr.tests.IntegerFieldType}" in the unit test
> files seems to be using the "TrieintField", if change to "IntPointField",
> some unit tests will fail, for example:
> [https://github.com/apache/lucene-solr/blob/3de0b3671998cc9bc723d10f1b31ce48cbd4fa64/solr/core/src/test/org/apache/solr/request/SimpleFacetsTest.java#L417]
--
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
