Rachid is exactly right. There's a long story here, I had
the bright idea of editing the schema directly from the admin UI
and one of the folks who, you know, understands browsers
did the heavy lifting and then we were alerted to the fact that
this is a huge security issue (i.e. uploading arbit
On 7/27/2016 12:37 PM, Rachid Bouacheria wrote:
> I know that there still is the option to use schema.xml by using the
> ClassicIndexSchemaFactory but I am curious to hear from y'all that use
> managed schema how you are doing it and if there are any downside,
> gotchas, or if all is just much bett
Gratzi!
On Jul 28, 2016 9:14 PM, "Rachid Bouacheria" wrote:
> Jonn,
> I don't want to answer on Erick's behalf, but I am pretty sure there is no
> UI built in solr 6 that allows you to update the schema and somehow check
> it in VCS. I would guess that you could do this by exposing an MBean.
> A
Jonn,
I don't want to answer on Erick's behalf, but I am pretty sure there is no
UI built in solr 6 that allows you to update the schema and somehow check
it in VCS. I would guess that you could do this by exposing an MBean.
Anyway that's how I interpreted Erick's reply.
On Wed, Jul 27, 2016 at 6
Erick - the UI you mention -- something that exists or something that has
to be built? (I'm upgrading to version 6 as well and this question is one
I'll have to deal with...)
On Wed, Jul 27, 2016 at 5:31 PM, Rachid Bouacheria
wrote:
> Thank you very much Erick, I appreciate your feed back.
>
>
Thank you very much Erick, I appreciate your feed back.
On Wed, Jul 27, 2016 at 2:24 PM, Erick Erickson
wrote:
> Using classic schema is perfectly acceptable/reasonable, you can
> continue to do so freely (you'll have to change to
> ClassicSchemaFactory though).
>
> Also, you can freely edit man
Using classic schema is perfectly acceptable/reasonable, you can
continue to do so freely (you'll have to change to
ClassicSchemaFactory though).
Also, you can freely edit managed-schema just as you did schema.xml.
The "trick" here is that you have to take some care _not_ to issue
commands that mo
