Could you explain why the performance is an issue for points-based fields? I've
looked through the referenced issue (which is fixed in the version we are
running) but I'm missing the link between the two. Is there an issue to improve
this for points-based fields?
We're going to change the field type to a string, as our queries are always
looking for a specific value (and not intervals/ranges) and rerun our load test.
Kind Regards,
James Bodkin
On 11/06/2020, 14:49, "Erick Erickson" <erickerick...@gmail.com> wrote:
There’s a lot of confusion about using points-based fields for faceting,
see: https://issues.apache.org/jira/browse/SOLR-13227 for instance.
Two options you might try:
1> copyField to a string field and facet on that (won’t work, of course,
for any kind of interval/range facet)
2> use the deprecated Trie field instead. You could use the copyField to a
Trie field for this too.
Best,
Erick
