[
https://issues.apache.org/jira/browse/SOLR-14692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168222#comment-17168222
]
Jason Gerlowski commented on SOLR-14692:
----------------------------------------
I've create an initial pass at this in the PR
[here|https://github.com/apache/lucene-solr/pull/1707]. I still need to work
through documentation, tests, and do a few sanity checks on the join queries
that are created as a result of this new "method" property. But the bones of
the implementation were pretty straightforward.
> JSON Facet "join" domain should take optional "method" property
> ---------------------------------------------------------------
>
> Key: SOLR-14692
> URL: https://issues.apache.org/jira/browse/SOLR-14692
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: faceting, JSON Request API
> Affects Versions: master (9.0), 8.6
> Reporter: Jason Gerlowski
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Solr offers several different join implementations which can be switched off
> providing the "method" local-param on JoinQuery's. Each of these
> implementations has different performance characteristics and can behave very
> differently depending on a user's data and use case.
> When joins are used internally as a part of JSON Faceting's "join"
> domain-transform though, users have no way to specify which implementation
> they would like to use. We should correct this by adding a "method" property
> to the join domain-transform. This will let user's choose the join that's
> most performant for their use case during JSON Facet requests.
--
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
