[
https://issues.apache.org/jira/browse/SOLR-13390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17040379#comment-17040379
]
Chris M. Hostetter commented on SOLR-13390:
-------------------------------------------
the main issue would be ensuring we don't break backcompat for people who
already have QEC configured -- even if they have it configured with a weird
name. (ie: it's not enough to say "don't register a QEC if a component with the
name 'elevate' already exists")
the second thing to consider is what kind of implicit configuration this new
implicit QEC instance should have? ... should it's "configured elevations" be
hardcoded with an "empty set" or should it be configured to look for a file
with a specific name (like "elevate.xml") that is happily ignores if it doesn't
exist but happily loads if it does?
> Provide Query Elevation Component by default
> --------------------------------------------
>
> Key: SOLR-13390
> URL: https://issues.apache.org/jira/browse/SOLR-13390
> Project: Solr
> Issue Type: Bug
> Reporter: Erik Hatcher
> Priority: Major
>
> Like other components, like highlighting and faceting, it'd be useful to have
> this work out of the box by just enabling it on the request. Currently the
> component needs to be added to `/select` and an empty elevate.xml file needs
> to be added to the config - a bit unnecessarily arduous.
> Let's add the component to `/select` and modify the component to be happy
> with or without an elevate.xml (since id's can be sent on the request to
> elevate, so fixed config isn't needed either).
--
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
