[
https://issues.apache.org/jira/browse/SOLR-7885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15045068#comment-15045068
]
Aaron LaBella commented on SOLR-7885:
-------------------------------------
Sure. Our DIH configuration files are stored, protected and maintained on a
*separate* HTTP server with an admin/editing interface. This allows us to give
users an actual front-end editor, make changes to the DIH, and have those
changes reloaded in SOLR automatically -- *without* having to explicitly reload
SOLR in any form (either at runtime or with a server restart).
I guess I didn't try reload-config because a.) I'm not really seeing any great
documentation on this feature and b.) I'm confused if it actually *persists* an
uploaded and/or reloaded configuration back to the local file system. If not,
then this is a problem because it means that if the SOLR server restarts it'll
re-load the old configurations.
I suppose you could argue this as a "back door" to SOLR, but, it's also
something that is disabled by default and users would have to consciously
enable using -Dsolr.allow.http.resourceloading, assuming they are willing to
accept the risk.
> Add support for loading HTTP resources
> --------------------------------------
>
> Key: SOLR-7885
> URL: https://issues.apache.org/jira/browse/SOLR-7885
> Project: Solr
> Issue Type: Improvement
> Components: contrib - DataImportHandler, SolrJ
> Affects Versions: 5.3
> Reporter: Aaron LaBella
> Attachments: SOLR-7885-1.patch, SOLR-7885-2.patch
>
>
> I have a need to be able to load data import handler configuration files from
> an HTTP server instead of the local file system. So, I modified
> {code}org.apache.solr.core.SolrResourceLoader{code} and some of the
> respective dataimport files in {code}org.apache.solr.handler.dataimport{code}
> to be able to support doing this.
> {code}solrconfig.xml{code} now has the option to define a parameter:
> *configRemote*, and if defined (and it's an HTTP(s) URL), it'll attempt to
> load the resource. If successfully, it'll also persist the resource to the
> local file system so that it is available on a solr server restart per chance
> that the remote resource is currently unavailable.
> Lastly, to be consistent with the pattern that already exists in
> SolrResourceLoader, this feature is *disabled* by default, and requires the
> setting of an additional JVM property:
> {code}-Dsolr.allow.http.resourceloading=true{code}.
> Please review and let me know if there is anything else that needs to be done
> in order for this patch to make the next release. As far as I can tell, it's
> fully tested and ready to go.
> Thanks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
