[SOLR-5287] Allow at least solrconfig.xml and schema.xml to be edited via the admin screen

• Type: Improvement
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 4.5, 6.0
• Fix Version/s: 5.0, 6.0
• Component/s: Admin UI, Schema and Analysis
• Assignee: Erick Erickson
• Reporter: Erick Erickson
• Created: 28/Sep/13 13:30
• Updated: 16/Feb/17 15:55
• Resolved: 04/Apr/14 13:16

Description

A user asking a question on the Solr list got me to thinking about editing the main config files from the Solr admin screen. I chatted briefly with steffkes about the mechanics of this on the browser side, he doesn't see a problem on that end. His comment is there's no end point that'll write the file back.

Am I missing something here or is this actually not a hard problem? I see a couple of issues off the bat, neither of which seem troublesome.

1> file permissions. I'd imagine lots of installations will get file permission exceptions if Solr tries to write the file out. Well, do a chmod/chown.

2> screwing up the system maliciously or not. I don't think this is an issue, this would be part of the admin handler after all.

Does anyone have objections to the idea? And how does this fit into the work that [e-mail] has been doing?

I can imagine this extending to SolrCloud with a "push this to ZK" option or something like that, perhaps not in V1 unless it's easy.....

Of course any pointers gratefully received. Especially ones that start with "Don't waste your effort, it'll never work (or be accepted)"...

Because what scares me is this seems like such an easy thing to do that would be a significant ease-of-use improvement, so there has to be something I'm missing.

So if we go forward with this we'll make this the umbrella JIRA, the two immediate sub-JIRAs that spring to mind will be the UI work and the endpoints for the UI work to use.

I think there are only two end-points here
1> list all the files in the conf (or arbitrary from <solr_home>/collection) directory.
2> write this text to this file

Possibly later we could add "clone the configs from coreX to coreY".

BTW, I've assigned this to myself so I don't lose it, but if anyone wants to take it over it won't hurt my feelings a bit....

Issue Links

• blocks: SOLR-5446 Admin UI - Allow changing Schema and Config
• incorporates: SOLR-5433 Use the Schema REST api for editing the schema file
• incorporates: SOLR-5432 Allow simple editing for solrconfig.xml and schema.xml from the admin interface
• is blocked by: SOLR-5518 Move editing config files into a new handler
• is related to: SOLR-791 Allow to submit config and schema when creating a new core
• is related to: SOLR-5459 Try loading a temporary core when saving a file in the admin UI config editing mode
• relates to: SOLR-5523 Implement proper security when writing config files to Solr
• relates to: SOLR-5522 Pull modifying the Solr config documents out of Solr 4.x
• relates to: SOLR-6925 Back out changes having to do with SOLR-5287 (editing configs from admin UI)
• relates to: SOLR-791 Allow to submit config and schema when creating a new core
• relates to: SOLR-1523 Destructive Solr operations accept HTTP GET requests