Re: Making managed schema unmutable correctly?

Solved it - had to make sure default requestHander was configured for spellcheck. -- View this message in context: http://lucene.472066.n3.nabble.com/Making-managed-schema-unmutable-correctly-tp4264051p4272235.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Making managed schema unmutable correctly?

From: "Boman [via Lucene]" <ml-node+s472066n4272073...@n3.nabble.com<mailto:ml-node+s472066n4272073...@n3.nabble.com>> Date: Thursday, April 21, 2016 at 9:52 PM To: Boman Irani <bir...@apttus.com<mailto:bir...@apttus.com>> Subject: Re: Making managed schema u

Re: Making managed schema unmutable correctly?

Thanks @Erick. You are right. That collection is not using a managed-schema. Works now! -- View this message in context: http://lucene.472066.n3.nabble.com/Making-managed-schema-unmutable-correctly-tp4264051p4272073.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Making managed schema unmutable correctly?

tus":0, > "QTime":2}, > "errors":[{"errorMessages":"schema is not editable"}]} > > Thanks. > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Making-managed-schema-unmutable-correctly-tp4264051p4271963.html > Sent from the Solr - User mailing list archive at Nabble.com.

Re: Making managed schema unmutable correctly?

rMessages":"schema is not editable"}]} Thanks. -- View this message in context: http://lucene.472066.n3.nabble.com/Making-managed-schema-unmutable-correctly-tp4264051p4271963.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Making managed schema unmutable correctly?

Thank you very much Erick, It does look like I was staring at the Reference Guide for too long and between the files and APIs and release notes, my mind just played tricks at 1am :-) Regards, Alex. Newsletter and resources for Solr beginners and intermediates: http://www.solr-start.com/

Re: Making managed schema unmutable correctly?

Thanks appreciate the feedback. On Wed, Mar 16, 2016 at 8:23 PM, Shawn Heisey wrote: > On 3/16/2016 7:51 PM, Jay Potharaju wrote: > > Does using schema API mean that no upconfig to zookeeper and no reloading > > of all the nodes in my solrcloud? In which scenario should I

Re: Making managed schema unmutable correctly?

I think you're mixing up schema and config? The message about not hand-modifying is for schema.xml (well, managed-schema). To lock it down you need to modify solrconfig.xml... There shouldn't need to be any need to unload, just reload? And I just skipped the e-mail so maybe I'm way off base.

Re: Making managed schema unmutable correctly?

On 3/16/2016 7:51 PM, Jay Potharaju wrote: > Does using schema API mean that no upconfig to zookeeper and no reloading > of all the nodes in my solrcloud? In which scenario should I not use schema > API, if any? The documentation says that a reload occurs automatically after the schema

Re: Making managed schema unmutable correctly?

s and I'm not worrying about elevation, synonyms, > etc. much yet. > > -Original Message- > From: Alexandre Rafalovitch [mailto:arafa...@gmail.com] > Sent: Wednesday, March 16, 2016 3:15 AM > To: solr-user <solr-user@lucene.apache.org> > Subject: Making managed schema u

RE: Making managed schema unmutable correctly?

<solr-user@lucene.apache.org> Subject: Making managed schema unmutable correctly? So, I am looking at the Solr 5.5 examples with their all-in by-default managed schemas. And I am scratching my head on the workflow users are expected to follow. One example is straight from documentation:

Re: Making managed schema unmutable correctly?

On 3/16/2016 1:14 AM, Alexandre Rafalovitch wrote: > So, I am looking at the Solr 5.5 examples with their all-in by-default > managed schemas. And I am scratching my head on the workflow users are > expected to follow. > > One example is straight from documentation: > "With the above

Re: Making managed schema unmutable correctly?

On Wed, Mar 16, 2016 at 11:10 PM, Erick Erickson wrote: > Personally I prefer to hand-edit the files. Me too, I hand edit managed-schema all the time. IMO, the warning is a bit overkill. -Yonik

Re: Making managed schema unmutable correctly?

Well, if using managed schema in SolrCloud, all the updates to the nodes is automatic so it's easier from that perspective. To me, the sweet spot for managed schema is that it lends itself to some kind of front end that allows you to deal with the schema visually, one can envision widgets,

RE: Making managed schema unmutable correctly?

feel like just now am I really upping my game; hopefully it continues. -Original Message- From: Alexandre Rafalovitch [mailto:arafa...@gmail.com] Sent: Wednesday, March 16, 2016 5:44 PM To: solr-user <solr-user@lucene.apache.org> Subject: Re: Making managed schema unmutable cor

Re: Making managed schema unmutable correctly?

Does using schema API mean that no upconfig to zookeeper and no reloading of all the nodes in my solrcloud? In which scenario should I not use schema API, if any? Thanks Jay On Wed, Mar 16, 2016 at 6:22 PM, Shawn Heisey wrote: > On 3/16/2016 1:14 AM, Alexandre Rafalovitch

Making managed schema unmutable correctly?

So, I am looking at the Solr 5.5 examples with their all-in by-default managed schemas. And I am scratching my head on the workflow users are expected to follow. One example is straight from documentation: "With the above configuration, you can use the Schema API to modify the schema as much as