Re: Managed Schema multiValued Predict Problem

Lova, When a search term is "foo*" or similar, you have a multivalue search. In schema.xml you have for a typical field, an index analysis chain and a query analysis chain. In the multivalue case, neither of these chains is followed. There is a wiki page which explains what chain gets followed,

Re: Managed Schema multiValued Predict Problem

Hello, I have this error org.apache.solr.common.SolrException: can not use FieldCache on multivalued field: post_title I can need specific field as multivalue, it's a bug in my app what I change in solrconfig.xml please? Thanks -- View this message in context: http://lucene.472066.n3.nabble.

Re: Managed schema used with Cloudera MapreduceIndexerTool and morphlines?

Hey Jay! All I can say is "good luck with that". I do know Morphlines uses EmbeddedSolrServer to do its work. So I don't really see a good way to pluck just what you'd need for schemaless. The MapReduceIndexerTool is carried right along with Solr though. IIRC the Morphlines stuff is mostly the ET

Re: Managed Schema multiValued Predict Problem

You are right, I mean schemaless mode. I saw that it's your answer ;) I've edited solrconfig.xml and fixed it. Thanks! On Mon, Mar 13, 2017 at 5:46 PM, Alexandre Rafalovitch wrote: > There is managed schema, which means it is editable via API, and there > is 'schemaless' mode that uses that to a

Re: Managed Schema multiValued Predict Problem

There is managed schema, which means it is editable via API, and there is 'schemaless' mode that uses that to auto-define the field based on the first occurance. 'schemaless' mode does not know if the field will be multi-valued the first time it sees content for that field. So, all the fields crea

Re: Managed Schema multiValued Predict Problem

OK, I found the answer here: http://stackoverflow.com/questions/38730035/solr-schemaless-mode-creating-fields-as-multivalued On Mon, Mar 13, 2017 at 5:15 PM, Furkan KAMACI wrote: > Hi, > > I generate dummy documents to test Solr 6.4.2. I create a field like that > at my test code: > >

Re: Managed schema vs schema.xml

I suggest we make additional comments on SOLR-10241. I created it as a result of this discussion and anyone who takes it on would benefit from the comments being made there. Anyone can make comments there, there's no special karma required although you do have to create a login. From the interest

Re: Managed schema vs schema.xml

Actually, the main cross-references are from the solrconfig.xml, and primarily from the Update Request Handler chain that creates the "schemaless" effect. Then, I think you also have highlighters, etc. I did that full analysis as a presentation at the last Solr Revolution: https://www.slideshare.

Re: Managed schema vs schema.xml

On 3/7/2017 1:32 PM, Phil Scadden wrote: I would have to say the "basic-config" seems distinctly more than basic. It is still a huge file. I thought perhaps I could delete every unused field type, but worried there were some "system" dependencies. This is definitely true. Solr example configs

Re: Managed schema vs schema.xml

Maybe this is expert stuff, but we keep our schema, solrconfig, and everything else checked into source control. I wrote a Python thingy to hit the cluster through the load balancer, get the zkHost string from status, upload the files to zookeeper (kazoo is a nice library), link the config, the

Re: Managed schema vs schema.xml

In the reference guide, in the chapter named "The Well Configured Solr Instance", it says (I'm copying+pasting from the PDF version) : Switching from Managed Schema to Manually Edited schema.xml > If you have started Solr with managed schema enabled and you would like to > switch to manually editi

Re: Managed schema vs schema.xml

See SOLR-10241 I just opened for discussion. My first impulse (well actually second) is to _not_ encourage anyone to hand-edit managed schema, and especially not put that in the ref guide. But perhaps put the classic schema factory in a comment in basic_configs and direct people there (and maybe e

RE: Managed schema vs schema.xml

I would second that guide could be clearer on that. I read and reread several times trying to get my head around the schema.xml/managed-schema bit. I came away from first cursory reading with the idea that managed-schema was mostly for schema-less mode and only after some stuff ups and puzzling

Re: Managed schema vs schema.xml

On 7 March 2017 at 15:02, OTH wrote: > Specifically, that 'managed-schema' could indeed be modified by hand, or > even that what the HTTP API is doing is actually modifying this file. Thank you for the specific feedback. That is something we should fold into the Guide as you are not the only one

Re: Managed schema vs schema.xml

Hi, Thanks, I should've consulted this guide more thoroughly. I actually had encountered this section when reading the guide, but somehow forgot about it when asking this question. I think, it doesn't clarify some things very well, which could leave a beginner a bit confused. Specifically, that

Re: Managed schema vs schema.xml

Yes, it has been asked many times and has been answered both on the list and in the - awesome - Reference Guide. I'd recommend reading that and then coming back again with more specific question: https://cwiki.apache.org/confluence/display/solr/Overview+of+Documents%2C+Fields%2C+and+Schema+Design

Re: Managed schema vs schema.xml

Hi, Thanks, that sufficiently answers the question. It's especially good to know now that hand-editing is fine, as long as it's separated from API calls with restarts in between. Thanks On Tue, Mar 7, 2017 at 9:57 PM, Shawn Heisey wrote: > On 3/7/2017 9:41 AM, OTH wrote: > > I understand that

Re: Managed schema vs schema.xml

Hi OTH, I personally prefer to use the classic *schema.xml* file as I feel its better for core creation with the desired fields than dealing with api calls. You can use it specifying the schemaFactory class as ClassicIndexSchemaFactory as follows: Best regards, Ivan 2017-03-07 17:41 GMT+01:00

Re: Managed schema vs schema.xml

On 3/7/2017 9:41 AM, OTH wrote: > I understand that managed-schema is not supposed to be edited by hand but > only via the "API". All I understand about this "API" however, is that it > may be referring to the "Schema" page in the Solr browser-based Admin. > > However, in this "Schema" page, it pr

Re: Managed schema and schema.xml file

On 6/18/2015 8:10 AM, Steven White wrote: > In 5.1.0 (and maybe prior ver.?) when I enable managed schema per the > above, the existing schema.xml file is left as-is, a copy of it is created > as schema.xml.bak and a new one is created based on the name I gave it > "my-schema.xml". > > With 5.2.1

Re: Managed Schema

Thank you for the update! I will work with 4.8.1 for now - I'm able to use the schema API and waiting (about 2 seconds) between any updates. Looking forward to 4.10! Joe On Fri, Aug 15, 2014 at 7:15 PM, Erick Erickson wrote: > Ryan is talking of cutting the initial 4.10 in a week or so. As

Re: Managed Schema

Ryan is talking of cutting the initial 4.10 in a week or so. As Steve mentioned it may take some time to get it out the door, so let's call it a (very) tentative date of mid September. On Fri, Aug 15, 2014 at 9:16 AM, Steve Rowe wrote: > In the Lucene/Solr 4.X line, the average minor release int

Re: Managed Schema

In the Lucene/Solr 4.X line, the average minor release interval has been 10 weeks. 4.9 was released 7 weeks ago. It takes 2-3 weeks to go from starting the release process to producing and announcing a release, so I expect someone will volunteer to perform the 4.10 release within the next week

Re: Managed Schema

Thank you! Any ideas when 4.10 will be released? I tried sleeping when adding fields, and that improved things, but since I'm in schema-less mode, sometimes that doesn't work either. If I managed the schema all 'myself' using the schema API; would that work? On Fri, Aug 15, 2014 at 11:34 AM, St

Re: Managed Schema

Hi Joseph, SOLR-6137 fixed the NPE you encountered with 4.9, as well a couple other managed schema concurrency issues - it will be included in the next release of Solr: 4.10. Steve On Aug 15, 2014, at 11:00 AM, Joseph Obernberger wrote: > Hi