Isn't just reloading the core via Admin interface sufficient?
I though that all Solr driven changes are written out to managed-schema at
once, so as long as core is reloaded right after manual changes, it should
be OK.
Regards,
Alex
On 4 Jun 2016 10:12 am, "Erick Erickson" <erickerick...@gmail.com> wrote:
> Actually, I prefer to do it the other way:
>
> 1> shut down Solr
> 2> edit managed_schema
> 3> start Solr.
>
> that eliminates any possibility of inadvertently overwriting your
> changes by issuing a managed schema call.
>
> that's a nit though, either will work.
>
>
> FWIW,
> Erick
>
> On Fri, Jun 3, 2016 at 11:02 AM, Shawn Heisey <apa...@elyograg.org> wrote:
> > On 6/3/2016 9:22 AM, Jamal, Sarfaraz wrote:
> >> I would edit the managed-schema, make my changes, shutdown solr? And
> >> start it back up and verify it is still there?
> >
> > That's the sledgehammer approach. Simple and effective, but Solr does
> > go offline for a short time.
> >
> >> Or is there another way to reload the core/collection?
> >
> > For SolrCloud:
> >
> https://cwiki.apache.org/confluence/display/solr/Collections+API#CollectionsAPI-api2
> >
> > For non-cloud mode:
> >
> https://cwiki.apache.org/confluence/display/solr/CoreAdmin+API#CoreAdminAPI-RELOAD
> >
> > Thanks,
> > Shawn
> >
>
