[
https://issues.apache.org/jira/browse/SOLR-5287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13782355#comment-13782355
]
Jan Høydahl commented on SOLR-5287:
-----------------------------------
Yea, +1 to supporting the short-name in schema. It's more readable after all.
I played with a sample self-documentation format which could be used by GUI to
pull plugin documentation from server instead of hardcoding in HTML. Could also
use for generating this part of the documentation for the ref-guide and avoid
mismatch. And it would benefit Lucene and ES users as well as Solr users!
Example return string for {{synonymFilterFactory#getConfigSpec()}}
{code}
{ "key" : "synonym",
"name" : "Synonym filter",
"desc" : "Token filter which expands synonyms from a provided dictionary",
"see" :
"http://lucene.apache.org/core/4_4_0/analyzers-common/org/apache/lucene/analysis/synonym/SynonymFilter.html";,
"params" : [
{ "name" : "synonyms", "info" : "Name of synonym dictionary file",
"value" : "STRING" },
{ "name" : "format", "info" : "Specify format of the dictionary. May be
solr or snowball", "value" : [ "solr", "snowball" ]},
{ "name" : "ignoreCase", "info" : "Set to true for case insensitive",
"value" : "BOOLEAN" },
{ "name" : "expand", "info" : "If true, a synonym will be expanded to all
equivalent synonyms. If false, all equivalent synonyms will be reduced to the
first in the list", "value" : "BOOLEAN" },
{ "name" : "tokenizerFactory", "info" : "Which tokenizer to use when
parsing the dictionary. Use either shortname or class name", "value" :
"ref:TOKENIZERS"}
]
}
{code}
Well, guess we're way off-track here compared to original issue. Let's spin off
separate JIRAs for whatever we'd like to achieve :)
> Allow at least solrconfig.xml and schema.xml to be edited via the admin screen
> ------------------------------------------------------------------------------
>
> Key: SOLR-5287
> URL: https://issues.apache.org/jira/browse/SOLR-5287
> Project: Solr
> Issue Type: Improvement
> Components: Schema and Analysis, web gui
> Affects Versions: 4.5, 5.0
> Reporter: Erick Erickson
> Assignee: Erick Erickson
>
> 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 [[email protected]] 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....
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
