A GUI is just one of the multiple interfaces through which a user may
interact with Solr. The API is more important.
We are starting to move Solr from a config file based system to an API
based system where all that you wish to change in a system is
accessible through the API (I am talking about
So it just occurred to me to ask why stop with renaming? We're going
around the loop again of wouldn't it be nice to edit the configs from
a GUI. Or a collections like API to manage configs on Zookeeper.
That got me to wondering if XML is really doing us any favors at this
point. NOTE: To even
bq. Then make it accept two names, and start shipping examples with the new
name. Old stuff works, new stuff makes sense.
That's not all that is involved. When there is so much pointing to
solrconfig.xml and you cannot find solrconfig.xml anymore there is added
confusion. Doesn't matter if we
coreconfig.xml has it's own problems in SolrCloud,
collectionconfig seems better. Except in that case
stand-alone Solr doesn't really use collections...
Siiggghhh.
On Wed, Jul 8, 2015 at 11:47 PM, Shawn Heisey apa...@elyograg.org wrote:
I had a thought, wondering if the idea is completely
On 7/9/2015 10:55 AM, Erick Erickson wrote:
coreconfig.xml has it's own problems in SolrCloud,
collectionconfig seems better. Except in that case
stand-alone Solr doesn't really use collections...
Siiggghhh.
I debated with myself on whether I even wanted to bring this up.
Ultimately I
I had a thought, wondering if the idea is completely insane.
The config file named solrconfig.xml suggests that it is a config file
for all of Solr, rather than configuring an individual index (core).
The radical idea that came out of this realization is to transition to
something like
It is the wrong name - mostly because it came from a single core solution.
We could change it, but you have to pretty carefully consider how heavily
it's embedded out there now.
- Mark
On Thu, Jul 9, 2015 at 1:20 PM Shawn Heisey apa...@elyograg.org wrote:
On 7/9/2015 10:55 AM, Erick Erickson
Then make it accept two names, and start shipping examples with the new
name. Old stuff works, new stuff makes sense.
Upayavira
On Thu, Jul 9, 2015, at 08:47 PM, Mark Miller wrote:
It is the wrong name - mostly because it came from a single core
solution. We could change it, but you have to
