RE: Schema API specifying different analysers for query and index

It worked! Thanks Mr. Rafalovitch. I just removed “type”: “query”.. keys from the json, and used indexAnalyzer and queryAnalyzer in place of analyzer json node. Sent from Mail for Windows 10 From: Alexandre Rafalovitch Sent: 03 March 2021 01:19 To: solr-user Subject: Re: Schema API specifying

Re: Schema API specifying different analysers for query and index

RefGuide gives this for Adding, I would hope the Replace would be similar: curl -X POST -H 'Content-type:application/json' --data-binary '{ "add-field-type":{ "name":"myNewTextField", "class":"solr.TextField", "indexAnalyzer":{ "tokenizer":{ "class":"solr.PathHi

Re: Schema Browser API

The Luke request handler may do what you are asking for already? This is coming directly from Lucene and doesn't rely on what Solr has in the schema information. /admin/luke https://lucene.apache.org/solr/guide/7_7/implicit-requesthandlers.html https://cwiki.apache.org/confluence/display/SOLR/Luk

Re: Schema configuration field defaults

Sure. In both cases define a fieldType with those attributes set however you want. Any field that is defined with that fieldType will have the defaults you specify unless overridden on the field definition itself. Best, Erick > On Feb 25, 2019, at 9:08 AM, Dionte Smith wrote: > > Hi, > > I h

Re: Schema Change for Solr 7.4

Aliases are like pointers to collections that can be used in-place anywhere you'd use the collection name. See https://lucene.apache.org/solr/guide/7_4/collections-api.html#createalias -- Jan Høydahl, search solution arc

Re: Schema Change for Solr 7.4

Hi Shawn, thanks for this response. We are probably going to take your suggested approach: 1. Upload a new configset to ZooKeeper. 2. Create a new collection using the new configset. 3. Index data into the new collection. 4. Set up an alias with the original collection name, pointing at the ne

Re: Schema Change for Solr 7.4

On 8/3/2018 9:09 AM, Joe Lerner wrote: > We recently set up Solr 7.4 in Production. There are 2 Solr nodes, with 3 > zookeepers. We need to make a schema change. What I want to do is simply > push the updated schema to Solr, and then re-index all the content to pick > up the change. But I am being

Re: Schema Change for Solr 7.4

For an in-place migration: 1. Add new fields to the schema. 2. Reindex to populate those fields. 3. Change queries to use those fields and stop using old fields. 4. Stop sending data to old fields, reindex. 5. Remove old fields from the schema. wunder Walter Underwood wun...@wunderwood.org http:/

Re: Schema Change for Solr 7.4

Joe, On 8/3/18 11:44 AM, Joe Lerner wrote: > OK--yes, I can see how that would work. But it would require some quick > infrastructure flexibility that, at least to this point, we don't really > have. The only thing that needs swapping is the URL that your application uses to connect to Solr, so y

Re: Schema Change for Solr 7.4

OK--yes, I can see how that would work. But it would require some quick infrastructure flexibility that, at least to this point, we don't really have. Joe -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Schema Change for Solr 7.4

Joe, On 8/3/18 11:09 AM, Joe Lerner wrote: > We recently set up Solr 7.4 in Production. There are 2 Solr nodes, with 3 > zookeepers. We need to make a schema change. What I want to do is simply > push the updated schema to Solr, and then re-index all the content to pick > up the change. But I am b

Re: schema-api: modifying schema in xml format

Hi Steve, it is reasonable that schema api understand the commands only JSON. Great that you'll update the ref guide. Thanks for taking care of it. Nice of you :-) Cheers, Arturas On Wed, Apr 18, 2018 at 3:27 PM, Steve Rowe wrote: > Hi Arturas, > > The Schema API only understands commands in

Re: schema-api: modifying schema in xml format

Hi Arturas, The Schema API only understands commands in JSON. I looked through the ref guide page, and I’m surprised that this isn’t stated directly; I’ll try to fix that. -- Steve www.lucidworks.com > On Apr 18, 2018, at 4:12 AM, Arturas Mazeika wrote: > > Hi solr-users, > > is it possibl

Re: Schema update/Reload during Live traffic

On 3/23/2018 10:32 PM, Susheel Kumar wrote: I did schema update to Solr cloud of Source CDCR cluster and same on target. After Collection Reload, noticed "error opening searcher" / IndexWriter closed etc. on leader node while all replica's went into recovery mode. Later after restarting Solr on

Re: Schema API: Modify Unique Key

as unique key (uniqueness is OK) and do this kind of update. Regards,Nabil.  De : Shawn Heisey À : solr-user@lucene.apache.org Envoyé le : Lundi 27 mars 2017 17h00 Objet : Re: Schema API: Modify Unique Key On 3/27/2017 7:05 AM, nabil Kouici wrote: > We're going to use Sol

Re: Schema API: Modify Unique Key

On 3/27/2017 7:05 AM, nabil Kouici wrote: > We're going to use Solr in our organization (under test) and we want > to set the primary key through schema API, which is not allowed today. > Is this function planned to be implemented in Solr? If yes, do you > have any idea in which version? Steve Ro

Re: Schema API: Modify Unique Key

Hi Nabil, There is an open JIRA issue to implement this functionality, but I haven’t had a chance to work on it recently: . Consequently, I’m not sure which release will have it. Patches welcome! -- Steve www.lucidworks.com > On Mar 27, 2017,

Re: Schema Changes

Hi Ethan, If the new fields are something that the old documents are also supposed to contain, you would need to reindex. e.g. in case you add a new copy field or a new field in general that your raw document contains, you would need to reindex. If the new field would only be something that exists

Re: Schema API

Looks like I ran into the same as was discussed here: http://grokbase.com/t/lucene/solr-user/15c4nr1j48/solrcloud-1-server-1-configset-multiple-collections-multiple-schemas Would be nice if that would be changed in the future as it would make these setups much easier. On 29/04/16 20:07, Hendrik H

Re: Schema/Index design for disparate data sources (Federated / Google like search)

Thanks, Jack for various points. A question when you have hundreds of fields from different sources and you also have lot of copy fields instructions for facets, sort or catch all etc. you suffer some performance hit during ingestion as many of the copy instructions would just be executing but doin

Re: Schema/Index design for disparate data sources (Federated / Google like search)

Step one is to refine and more clearly state the requirements. Sure, sometimes (most of the time?) the end user really doesn't know exactly what they expect or want other than "Gee, I want to search for everything, isn't that obvious??!!", but that simply means that an analyst is needed to interven

Re: Schema API, change the defaultoperator

On 12/11/2015 8:02 AM, Yago Riveiro wrote: > I uploaded a schema.xml manualy with the defaultoperator configuration and > it's working. > > My problem is that my legacy application is huge and I can't go to all places > to add the q.op parameter. > > The solrconfig.xml option should be an optio

Re: Schema API, change the defaultoperator

I uploaded a schema.xml manualy with the defaultoperator configuration and it's working. My problem is that my legacy application is huge and I can't go to all places to add the q.op parameter. The solrconfig.xml option should be an option. The q.op param defined in request handlers work

Re: Schema API, change the defaultoperator

On 12/11/2015 4:23 AM, Yago Riveiro wrote: > How can I change the defaultoperator parameter through the schema API? The default operator and default field settings in the schema have been deprecated for quite some time, so I would imagine that you can't change them with the schema API -- they shou

Re: schema fileds and Typefield in solr-5.3.1

I fixe the prb using requestHandler dataimoprt: tika-data-config.xml I configure the tika-data-config.xml according to my needs to get the right value : now dont need indexing from Commandline using sim

Re: schema fileds and Typefield in solr-5.3.1

thank you , that's why I choose to add the exact value using solarium PHP Client, but the time out stop indexing after 30seconde: $dir = new Folder($dossier); $files = $dir->find('.*\.*'); foreach ($files as $file) { $file = new File($dir->pwd() . DS . $file); $query = $client->createExtract(

Re: schema fileds and Typefield in solr-5.3.1

Kostali - See if the "Introspect rich document parsing and extraction” section of http://lucidworks.com/blog/2015/08/04/solr-5-new-binpost-utility/ helps*. You’ll be able to see the output of /update/extract (aka Tika) and adjust your mappings and configurations accordingly. * And apologies t

Re: schema fileds and Typefield in solr-5.3.1

thank you Erick, i follow you advice and take a look to config apache tika, I have modifie my request handler /update/extract: last_modified ignored_ true links ignored_ D:\solr\solr-5.3.1\server\solr\tika-data-config.xml and config tika : data

Re: schema fileds and Typefield in solr-5.3.1

Have you looked at Solr Cell? See: https://cwiki.apache.org/confluence/display/solr/Uploading+Data+with+Solr+Cell+using+Apache+Tika When working with things like MS word, there are a couple of things to be aware of: 1> there has to be a mapping between the meta-data (last_edited, author, whatever)

Re: schema modification issue

Hi Steve, Thanks for paying attention to this. Here is the JIRA issue I reported: https://issues.apache.org/jira/browse/SOLR-7536. Sorry for any inconvenience caused by my unfamiliarness with JIRA. 2015-05-12 0:22 GMT+08:00 Steve Rowe : > Hi, > > Thanks for reporting, I’m working a test to repr

Re: schema modification issue

Hi, Thanks for reporting, I’m working a test to reproduce. Can you please create a Solr JIRA issue for this?: https://issues.apache.org/jira/browse/SOLR/ Thanks, Steve > On May 7, 2015, at 5:40 AM, User Zolr wrote: > > Hi there, > > I have come accross a problem that when using managed

Re: Schema API: add-field-type

Hi Steve, responses inline below: > On Apr 29, 2015, at 6:50 PM, Steven White wrote: > > Hi Everyone, > > When I pass the following: > http://localhost:8983/solr/db/schema/fieldtypes?wt=xml > > I see this (as one example): > > >date >solr.TrieDateField >0 >0 > > las

Re: Schema Parsing Failed: unknown field 'id' [Zookeeper, SolrCloud]

: out how to remove the configs from zookeeper through the cloud scripts, so I : just manually removed the files in the zookeeper data directory. https://cwiki.apache.org/confluence/display/solr/Using+ZooKeeper+to+Manage+Configuration+Files https://cwiki.apache.org/confluence/display/solr/Command

Re: Schema Parsing Failed: unknown field 'id' [Zookeeper, SolrCloud]

Thanks for the suggestions. I actually had both problems. I couldn't figure out how to remove the configs from zookeeper through the cloud scripts, so I just manually removed the files in the zookeeper data directory. -- View this message in context: http://lucene.472066.n3.nabble.com/Schema-Pa

Re: Schema Parsing Failed: unknown field 'id' [Zookeeper, SolrCloud]

One other possibility in addition to Hoss' comments. Did you load a version of your configs to ZooKeeper sometime that didn't have these fields? I don't quite know where the schema and solrconfig files came from, but the fact that they're on a local disk says nothing about what's in ZooKeeper. When

Re: Schema Parsing Failed: unknown field 'id' [Zookeeper, SolrCloud]

: Thanks. There is definitely a in each of the schemas. : : I am using 4.7.2. if this conig is working for you when you don't use zookeeper/hdfs then you must be using a newer version of Solr when you test w/ zk/hdfs 4.8.0 is when the and section tags were deprecated. in 4.7.x and earlier

Re: Schema Parsing Failed: unknown field 'id' [Zookeeper, SolrCloud]

Thanks. There is definitely a in each of the schemas. I am using 4.7.2. Here is one of the *schema.xml* (the others are similar): id

Re: Schema Parsing Failed: unknown field 'id' [Zookeeper, SolrCloud]

: There is nothing wrong with the declaration of the 'id' field, and I have it : working fine when it's not using SolrCloud/HDFS. One odd thing is the part ...I can't explain that, but as far as this... : that says "Schema file is solr//schema.xml", because there is no : schema file there. I hav

Re: Schema API synchronization question

The release vote has passed, the release packages are spreading out to the mirrors, and the announcement should appear in the next 12-24 hours. Steve www.lucidworks.com On Sep 2, 2014, at 11:56 PM, Matthias Broecheler wrote: > Yes, that is what we are seeing. Thanks for pointing me to the righ

Re: Schema API synchronization question

Yes, that is what we are seeing. Thanks for pointing me to the right issues to track. Where can I find out when 4.10 final is going to be released? Thanks, Matthias On Sat, Aug 30, 2014 at 9:26 PM, Erick Erickson wrote: > There have been some recent improvements in that area, what version of S

Re: Schema API synchronization question

There have been some recent improvements in that area, what version of Solr are you running? Is there any chance you could try with 4.10 when the final version is released? Or perhaps checkout/build the 4.10 release candidate? See, for instance, https://issues.apache.org/jira/browse/SOLR-6137 Sti

Re: Schema Updates and Core Reload with SolrCloud

Thanks for your validation Shawn. Marc 2014-08-27 15:18 GMT-04:00 Shawn Heisey : > On 8/27/2014 1:03 PM, Marc Campeau wrote: > > Well I got my answer by trying it. I issued the Collections API reload > > action on one of the shards (Shard4 to be exact, not the leader) and I > got > > this back

Re: Schema Updates and Core Reload with SolrCloud

On 8/27/2014 1:03 PM, Marc Campeau wrote: > Well I got my answer by trying it. I issued the Collections API reload > action on one of the shards (Shard4 to be exact, not the leader) and I got > this back as output. So the action triggers a reload of all shards > composing the Collection. The Colle

Re: Schema Updates and Core Reload with SolrCloud

Well I got my answer by trying it. I issued the Collections API reload action on one of the shards (Shard4 to be exact, not the leader) and I got this back as output. So the action triggers a reload of all shards composing the Collection. 0 11957 0 4585 0 2839 0 2655 0 7705

Re: Schema Updates and Core Reload with SolrCloud

This past thread from June might hold the answer to my question. Posting this here for other folks that might stumble upon this question. -- Forwarded message -- From: Shawn Heisey Date: 2014-06-28 1:36 GMT-04:00 Subject: Re: Some questions about Solrcloud To: solr-user@lucene.apa

Re: [Schema API] EmbeddedSolrServer Test

Thank you Chris, Exactly as you suggested I was looking into related classes to that one. Playing with : @BeforeClass > public static void init() throws Exception { > final SortedMap extraServlets = new > TreeMap(); > final ServletHolder solrRestApi = new ServletHolder("SolrRestApi", >

Re: [Schema API] EmbeddedSolrServer Test

EmbeddedSolrServer is really just for dealing with embedded SolrCore objects. It doesn't have ay of the other HTTP related plumbing assocaited with it -- which is why it can't be used for replication and/or cloud features, let alone the RESTLet based endpoints. if you want to write a test tha

Re: schema / config file names

Chris, We have actually done that. Our requirement was basically have a single installation of Solr to assume different roles and each role had its own changes for optimisation done on solrconfig.xml and schema.xml When we start a role we basically adapt to file role_solrconfig.xml and role_sch

Re: schema / config file names

ged. Thanks. From: Chris Hostetter To: solr-user@lucene.apache.org, Date: 07/02/2014 10:22 PM Subject:Re: schema / config file names : Is it required for the schema.xml and solrconfig.xml to have those exact : filenames? It's an extremelely good idea ...

Re: schema / config file names

: Is it required for the schema.xml and solrconfig.xml to have those exact : filenames? It's an extremelely good idea ... but strictly speaking no... https://cwiki.apache.org/confluence/display/solr/CoreAdminHandler+Parameters+and+Usage#CoreAdminHandlerParametersandUsage-CREATE This smells lik

Re: Schema

On Aug 22, 2013, at 19:53 , Kamaljeet Kaur wrote: > On Thu, Aug 22, 2013 at 10:56 PM, SolrLover [via Lucene] > wrote: >> >> Now use DIH to get the data from MYSQL database in to SOLR.. >> >> http://wiki.apache.org/solr/DataImportHandler > > > These are for versions 1.3, 1.4, 3.6 or 4.0. > Why

Re: Schema

Verisons mentioned in the wiki only tell you that these features are available from that version of Solr. This will not be applicable in your case as you are using the latest version. So everything you find in the wiki would be available in 4.4 Solr -- View this message in context: http://lucen

Re: Schema

On Thu, Aug 22, 2013 at 10:56 PM, SolrLover [via Lucene] wrote: > > Now use DIH to get the data from MYSQL database in to SOLR.. > > http://wiki.apache.org/solr/DataImportHandler These are for versions 1.3, 1.4, 3.6 or 4.0. Why versions are mentioned there? Don't they work on solr 4.4.0? -- K

Re: Schema

Now use DIH to get the data from MYSQL database in to SOLR.. http://wiki.apache.org/solr/DataImportHandler You need to define the field mapping (between my sql and SOLR document) in data-config.xml. -- View this message in context: http://lucene.472066.n3.nabble.com/Schema-tp4086136p4086140.h

Re: Schema Lint

Funny, you should ask. Here are the relevant suggestions from the Solr Usability contest that is going right now: *) https://solrstart.uservoice.com/forums/216001-usability-contest/suggestions/4249791-solr-lint-a-tool-to-check-solr-configuration-and *) https://solrstart.uservoice.com/forums/216001-

Re: Schema Lint

On Aug 6, 2013, at 9:55 AM, Steven Bower wrote: > Is there an easy way in code / command line to lint a solr config (or even > just a solr schema)? No, there's not. I would love there to be one, especially for the DIH. -- Andy Lester => a...@petdance.com => www.petdance.com => AIM:petdance

Re: Schema design for parent child field

from my experience deeply nested scopes is for SOLR-3076 almost only. On Sat, Jun 29, 2013 at 1:08 PM, Sperrink wrote: > Good day, > I'm seeking some guidance on how best to represent the following data > within > a solr schema. > I have a list of subjects which are detailed to n levels. > Each

Re: Schema design for parent child field

Both dynamic fields and multivalued fields are powerful Solr features that can be used to great effect, but only is used in moderation - a relatively small number of discrete values (e.g., a few dozens of strings.) Anything more complex and you are asking for trouble and creating a pseudo-schema

Re: Schema Change: Int -> String (i am the original poster, new email address)

Right, a search for "442" would not match "1442". -- Jack Krupansky -Original Message- From: z z Sent: Friday, June 07, 2013 2:18 AM To: solr-user@lucene.apache.org Subject: Re: Schema Change: Int -> String (i am the original poster, new email address) Mayb

Re: Schema Change: Int -> String (i am the original poster, new email address)

Maybe if I were to say that the column "user_id" will become "user_ids" that would clarify things? user_id:2002+AND+created:[${**from}+TO+${until}]+data:"more" becomes user_id*s*:2002+AND+created:[${**from}+TO+${until}]+data:"more" where I want 2002 to be an exact positive match on one of the u

Re: Schema Change: Int -> String (i am the original poster, new email address)

nts and your data model, > including a clarification about user id vs. "a string of concatenated user > id values", I can't answer your question definitively, other than "Maybe, > depending on what you really mean by user id." > > > -- Jack Krupansky > >

Re: Schema Change: Int -> String (i am the original poster, new email address)

ion definitively, other than "Maybe, depending on what you really mean by user id." -- Jack Krupansky -Original Message- From: z z Sent: Friday, June 07, 2013 12:11 AM To: solr-user@lucene.apache.org Subject: Re: Schema Change: Int -> String (i am the original poster, new

Re: Schema Change: Int -> String (i am the original poster, new email address)

The unique key is an auto-incremented int in the db. Sorry for having given the impression that user_id is the unique key per document. This is a table of events that are happening as users interact with our system. It just so happens that we were inserting individual records for each user before

Re: Schema Change: Int -> String (i am the original poster, new email address)

2013 11:48 PM To: solr-user@lucene.apache.org Subject: Re: Schema Change: Int -> String (i am the original poster, new email address) I want to query against one user_id in the string. eg user_id:2002+AND+created:[${from}+TO+${until}]+data:"more" So all of the records with a 2002 in us

Re: Schema Change: Int -> String (i am the original poster, new email address)

eg user_id:2002+AND+created:[${from}+TO+${until}]+data:"more" Expected results: return row "XYZ" but ignore this row: column1: "data here" column2: "more data here" ... user_id: "45 15001 45664" > *Row X* > > column1: "data here" > column2: "more data here" > ... > user_id: 2002 > > *Row Y*

Re: Schema Change: Int -> String (i am the original poster, new email address)

-Original Message- From: z z Sent: Thursday, June 06, 2013 11:31 PM To: solr-user@lucene.apache.org Subject: Re: Schema Change: Int -> String (i am the original poster, new email address) 3. Too hard to say from the way you have described it. Show us some sample input. Jack, Here you

Re: Schema Change: Int -> String (i am the original poster, new email address)

I want to query against one user_id in the string. eg user_id:2002+AND+created:[${from}+TO+${until}]+data:"more" So all of the records with a 2002 in user_id need to be returned and only those records. If this can only be guaranteed by having user_id be an integer, then that is fine, but I woul

Re: Schema Change: Int -> String (i am the original poster, new email address)

3. Too hard to say from the way you have described it. Show us some sample input. Jack, Here you go. *Row X* column1: "data here" column2: "more data here" ... user_id: 2002 *Row Y* column1: "data here" column2: "more data here" ... user_id: 45 *Row Z* column1: "data here" column2: "more data

Re: Schema Change: Int -> String

1. Generally, any schema change requires a full reindex. Sure, a lot of times you can squeak by, but with Solr and Lucene there are no guarantees. If it works for you, great. If not, don't complain - just reindex. And even if it does work for the current release, there is no guarantee that a si

Re: Schema Change: Int -> String

On 6/5/2013 11:25 PM, TwoFirst TwoLast wrote: > 1) If I change one field's type in my schema, will that cause problems with > the index or searching? My data is pulled in chunks off of a mysql server > so one field in the currently indexed data is simply an "int" type field in > solr. I would lik

Re: Schema/config changes and re-indexing in a SolrCloud setup

On Feb 7, 2013, at 5:23 PM, Steffen Elberg Godskesen wrote: > Re (1): Am I right in thinking that a given update is sent to every replica > of the shard to which it belongs for analysis and indexing? And that there is > no immediate way to separate indexing from queries within a collection?

Re: Schema Field Names i18n

Will a field have different names in different languages? There is no facility for 'aliases' for field name. Erick is right, this sounds like you need query and update components to implement this. Also, you might try using URL-encoding for the field names. This would save my sanity. On 01/10/

Re: Schema Field Names i18n

There's no really easy way that I know of. I've seen several approaches used though 1> do it in the UI. This assumes that your users aren't typing in raw queries, they're picking field names from a drop-down or similar. Then the UI maps the chosen fields into what the schema defines. 2> Do it in

Re: Re: Schema model to store additional field metadata

: So, let's assume you want to provide links to the images. : Having a field (multiValued?) with index="false" and stored="true" : would allow you to store all the img urls in a single field. : : All that said, now it's up to your application layer that : constructs the pages for presentation to

Re: Re: Schema model to store additional field metadata

You might be confusing indexing and storing. When you specify index="true" in your field definition, the input is tokenized, transformed, etc and the results of this (see the admin/analysis) page is what is searched. But when you specify stored="true", a literal, verbatim copy of the text is put i

Re: Re: Schema model to store additional field metadata

> Why would you store the actual images in SOLR? No, the images are files on the filesystem. Only the path to the image should be stored in Solr. > And you are most likely looking at dynamic fields as the solution > > 1) Define *_Path, *_Size, *_Alt as a dynamic field with appropriate types > 2

Re: Schema model to store additional field metadata

Why would you store the actual images in SOLR? There is no way to really search the bytes of image, is there? What you probably want to do is extract all searchable metadata out of that image, name, alt, EXIF, etc. And you are most likely looking at dynamic fields as the solution 1) Define *_Path

Re: Schema / Config Error?

.6 > schema/config for any differences. > > -- Jack Krupansky > > -Original Message- From: Erick Erickson > Sent: Wednesday, June 06, 2012 6:57 AM > To: solr-user@lucene.apache.org > Subject: Re: Schema / Config Error? > > That implies one of two things: &

Re: Schema / Config Error?

e.apache.org Subject: Re: Schema / Config Error? That implies one of two things: 1> you changed solr.xml. I'd go back to the original and re-edit anything you've changed 2> you somehow got a corrupted download. Try blowing your installation away and getting a new copy Because it wor

Re: Schema / Config Error?

Make sure your port is 8983 or 8080. On Wed, Jun 6, 2012 at 4:27 PM, Erick Erickson wrote: > That implies one of two things: > 1> you changed solr.xml. I'd go back to the original and re-edit > anything you've changed > 2> you somehow got a corrupted download. Try blowing your installation > away

Re: Schema / Config Error?

That implies one of two things: 1> you changed solr.xml. I'd go back to the original and re-edit anything you've changed 2> you somehow got a corrupted download. Try blowing your installation away and getting a new copy Because it works perfectly for me. Best Erick On Wed, Jun 6, 2012 at 4:14 AM

Re: Schema / Config Error?

Hi :) Looks like you forgot to paste your schema.xml and the error in your e-mail : o Gary Le 06/06/2012 10:14, Spadez a écrit : Hi, I installed a fresh copy of Solr 3.6.0 or my server but I get the following page when I try to access Solr: http://176.58.103.78:8080/solr/ It says errors t

Re: schema design question

(albums:query OR tracks:query) AND NOT(tracks:query -> albums:query) Is this it? That last clause does sound like a join. How do you shard? Is it possible to put all associated albums and tracks in one shard? You can then do a join query against each shard and merge the output yourself. On Fri,

Re: schema design question

Thanks, but I don't want to exclude all tracks that are associated with albums, I want to exclude tracks that are associated with albums *which match the query* (tracks and their associated albums may have different tags). I don't think your suggestion covers that. On Fri, Apr 6, 2012 at 9:35 AM,

Re: schema design question

I'd consider a field like "associated_with_album", and a field that identifies the kind of record this is "track or album". Then you can form a query like -associated_with_album:true (where '-' is the Lucene or NOT). And then group by kind to get separate groups of albums and tracks. Hope this h

Re: schema design help

On 13 March 2012 18:19, Abhishek tiwari wrote: [...] > My one more concern, > Though Establishments, Events, Movies are not related to each other, > > I have to make 3 search queries to their independent cores and club the > data to show, will that effect my relevancy? Yes, it will. The results f

Re: schema design help

Hi Gora, Thanks, My one more concern, Though Establishments, Events, Movies are not related to each other, I have to make 3 search queries to their independent cores and club the data to show, will that effect my relevancy? There is movie with title "Striker" and Establishment with title "Striker

Re: schema design help

On 8 March 2012 11:05, Abhishek tiwari wrote: > Gora, > we are not having the related search ... > like u have mentioned ... * will a search on an Establishment > also require results from Movie, such as what movies are showing > at the establishment* > > Establishment doesnot require movie reults

Re: schema design help

Gora, we are not having the related search ... like u have mentioned ... * will a search on an Establishment also require results from Movie, such as what movies are showing at the establishment* Establishment doesnot require movie reults .. each enitity has there separate search.. On Thu, Mar 8,

Re: schema design help

On 8 March 2012 10:40, Abhishek tiwari wrote: >  my page have layout in following manner >  *All tab* :which will contain all entities (Establishment/Event/Movie) > Establishment: contain Establishment search results > Event tab : will contain Event search results > Movie tab : will contain Movie

Re: schema design help

my page have layout in following manner *All tab* :which will contain all entities (Establishment/Event/Movie) Establishment: contain Establishment search results Event tab : will contain Event search results Movie tab : will contain Movie search results please suggest me how to design my schema

Re: schema design help

You should create multiple cores when each core is an independent search. If you have three separate search pages, you may want three separate cores. wunder Search Guy, Chegg.com On Mar 7, 2012, at 8:48 PM, Abhishek tiwari wrote: > please suggest me when one should create multiple core..? >

Re: schema design help

please suggest me when one should create multiple core..? On Thu, Mar 8, 2012 at 12:12 AM, Walter Underwood wrote: > Solr is not relational, so you will probably need to take a fresh look at > your data. > > Here is one method. > > 1. Sketch your search results page. > 2. Each result is a docum

Re: schema design help

Solr is not relational, so you will probably need to take a fresh look at your data. Here is one method. 1. Sketch your search results page. 2. Each result is a document in Solr. 3. Each displayed item is a stored field in Solr. 4. Each searched item is an indexed field in Solr. It may help to

Re: schema design help

I would say do both. If you have the capacity create a core for each and one that combines it and do some tests. There are pros and cons to both approaches. If you ever need joins in RDBMS terms then you probably want one index. If not then one index might still be a lot easier. The only real reaso

Re: schema design help

thanks for replying .. In our RDBMS schema we have Establishment/Event/Movie master relations. Establishment has title ,description , ratings, tags, cuisines (multivalued), services (multivalued) and features (multivalued) like fields..similarly in Event title, description, category(multivalued)

Re: schema design help

On 6 March 2012 18:01, Abhishek tiwari wrote: > i am new in solr  want help in shema design .  i have multiple entities > like Event , Establishments and Movies ..each have different types of > relations.. should i make diffrent core for each entities ? It depends on your use case, i.e., what wou

Re: schema,

On Sat, Dec 10, 2011 at 5:49 PM, E P wrote: > Hi > Dose anybody know a good source for schema.xml composition? > I am new to solr :) The Wiki contains a lot of information on Solr schemas. You could start with: * http://wiki.apache.org/solr/SchemaXml * http://wiki.apache.org/solr/SchemaDesign Sea

Re: schema changes changes 3.3 to 3.4?

Thanks, as a general rule a would totally agree, however the way we are using solr we don't want to be attach to any particular schema, we just want it to work with whatever the default is... but I will keep your suggestion in mind in the future thanks everyone.. you guys are always very helpful

Re: schema changes changes 3.3 to 3.4?

: I figure it out.. thanks for pointing me in the right direction... so at the : end solr field type text was changed for text_general they key take away here seems to be that when you upgraded from Solr 3.3 to Solr 3.4 you stoped using your old schema (which you copied from the 3.3 example), a

  1   2   3   >