[
https://issues.apache.org/jira/browse/SOLR-7930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson updated SOLR-7930:
---------------------------------
Attachment: SOLR-7930.patch
OK, I'm trying to clear out some backlog and came back to this. I think the
right thing to do here is just comment out all of the entries in the
elevate.xml config files.
The trappy bit is that a user whose never even _heard_ of QEV changes the
<uniqueKey> to something like "long" and suddenly can't load the core or create
a collection. Because we've included an example elevations that are only
relevant to the sample techproducts docs.
If someone intentionally changes the QEV component then I think the stack trace
is sufficient since it makes sense in that context. And at least they're
working with QEV so have incentive to look.
I'll check this in tomorrow sometime unless there are objections.
> Comment out Query Elevation Component in solrconfig.xml distro
> --------------------------------------------------------------
>
> Key: SOLR-7930
> URL: https://issues.apache.org/jira/browse/SOLR-7930
> Project: Solr
> Issue Type: Bug
> Affects Versions: 5.3, 6.0
> Reporter: Erick Erickson
> Assignee: Erick Erickson
> Priority: Minor
> Attachments: SOLR-7930.patch
>
>
> What do people think about this? QEV, especially with the default example is
> trappy when someone defines the <uniqueKey> as something other than a string.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
