[
https://issues.apache.org/jira/browse/SOLR-15274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17307243#comment-17307243
]
Chris M. Hostetter commented on SOLR-15274:
-------------------------------------------
bq. ...the file modification date is used to detect this... ...I'd prefer it be
done in a general way in either ConfigSetService or the SolrResourceLoader it
creates so that consumers (QEC) can be kept simple and free of implementation
details that are ConfigSetService specific...
+1
bq. I'd rather not add code to QEC to look in old places. If someone doesn't
read the release notes, they will find that QEC throws an error that it can't
find the config after which they'll find out, perhaps after reading the release
notes / ref guide then.
Except that it's suppose to be possible to use QEC w/o any elevate.xml at all
-- so there _shouldn't_ be an error if QEC can't find an elevate.xml in the
conf dir. Hence my suggestion that if we're breaking backcompat on the data
dir usage, we just include a cheap 2 line "if elevate.xml in data dir, log
error" check in the init() method to try and help ease frustration when QEC
seems to silently ignore their existing (datadir) elevate.xml on upgrade.
...except that (according SOLR-14970 that I just noticed) the ability to use
QEC w/o an elevate.xml has evidently been broken for a few releases ... so i
don't really know how much that matters.
> QueryElevationComponent: auto-load file changes; remove data dir support
> ------------------------------------------------------------------------
>
> Key: SOLR-15274
> URL: https://issues.apache.org/jira/browse/SOLR-15274
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SearchComponents - other
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> QueryElevationComponent can detect changes to its elevate.xml file and load
> it following a commit (new searcher). But this only works when the file is
> in the "data" dir, which is weird. I wish to +remove+ support for the data
> dir and add this auto-loading mechanism to standard conf/configSet location.
> Additionally, I wish to +remove+ QEC's support of the elevate.xml file to be
> "versioned" -- e.g. elevate.xml.001, elevate.xml.002.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
