[
https://issues.apache.org/jira/browse/SOLR-6311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14316751#comment-14316751
]
Timothy Potter commented on SOLR-6311:
--------------------------------------
I'm going with [~hossman]'s suggestion of using the LUCENE_MATCH_VERSION and am
targeting this fix for the 5.1 release. So my first inclination was to do:
{code}
if
(req.getCore().getSolrConfig().luceneMatchVersion.onOrAfter(Version.LUCENE_5_1_0))
{
...
{code}
But Version.LUCENE_5_1_0 is deprecated, so do I do this instead?
{code}
if (req.getCore().getSolrConfig().luceneMatchVersion.onOrAfter(Version.LATEST))
{
...
{code}
I guess it's the deprecated thing that's throwing me off.
> SearchHandler should use path when no qt or shard.qt parameter is specified
> ---------------------------------------------------------------------------
>
> Key: SOLR-6311
> URL: https://issues.apache.org/jira/browse/SOLR-6311
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.9
> Reporter: Steve Molloy
> Assignee: Timothy Potter
> Attachments: SOLR-6311.patch
>
>
> When performing distributed searches, you have to specify shards.qt unless
> you're on the default /select path for your handler. As this is configurable,
> even the default search handler could be on another path. The shard requests
> should thus default to the path if no shards.qt was specified.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
