[
https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14088253#comment-14088253
]
Mark Miller commented on SOLR-3619:
-----------------------------------
bq. I did it recently and didn't think it was bad at all.
Thanks for the input Cassandra!
{quote}
The biggest plus for me was that I didn't need to bother with ZK tools while in
SolrCloud mode to make some simple edits. How anyone uses those tools is really
beyond me - I have a huge hazy gap in my brain whenever I try to use them and I
fail miserably.
{quote}
That's still a huge issue with SolrCloud, but extends to solrconfig.xml as
well. We have an extra script that helps deal with that for Cloudera Search,
but it's still no fun.
bq. However, the Schema API is still a work-in-progress;
Okay, so sounds like that is the largest limiting part of this right now?
[~gchanan], you did a lot with the managed schema mode recently. What do you
think about it becoming the primary Solr 'mode' in it's current state?
> Rename 'example' dir to 'server' and pull examples into an 'examples'
> directory
> -------------------------------------------------------------------------------
>
> Key: SOLR-3619
> URL: https://issues.apache.org/jira/browse/SOLR-3619
> Project: Solr
> Issue Type: Improvement
> Reporter: Mark Miller
> Assignee: Timothy Potter
> Fix For: 4.9, 5.0
>
> Attachments: SOLR-3619.patch, SOLR-3619.patch, managed-schema,
> server-name-layout.png, solrconfig.xml
>
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
