Re: [E] Re: Stemming and Managed Schema

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" &

Re: [E] Re: Stemming and Managed Schema

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

Re: [E] Re: Stemming and Managed Schema

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 an

RE: [E] Re: Stemming and Managed Schema

Awesome, So just to make sure I got it right: I would edit the managed-schema, make my changes, shutdown solr? And start it back up and verify it is still there? Or is there another way to reload the core/collection? Thanks! Sas -Original Message- From: Shawn Heisey [mailto:apa

Re: Stemming and Managed Schema

On 6/3/2016 9:07 AM, Jamal, Sarfaraz wrote: > I found the following article: > http://thinknook.com/keyword-stemming-and-lemmatisation-with-apache-solr-2013-08-02/ > > And I want to do stemming on one of our fields. > > However, I am using a Managed Schema and I am unsure ho

Re: Stemming and Managed Schema

Sure, this is the API reference [1] where you can see, you can add types and fields Andrea [1] https://cwiki.apache.org/confluence/display/solr/Schema+API On 03/06/16 17:07, Jamal, Sarfaraz wrote: Hi Guys, I found the following article: http://thinknook.com/keyword-stemming

Stemming and Managed Schema

Hi Guys, I found the following article: http://thinknook.com/keyword-stemming-and-lemmatisation-with-apache-solr-2013-08-02/ And I want to do stemming on one of our fields. However, I am using a Managed Schema and I am unsure how to add these two blocks to it - I know there is an API

答复: help need example code of solrj to get schema of a given core

Thanks Georg very much! Ming -邮件原件- 发件人: Georg Sorst [mailto:georg.so...@gmail.com] 发送时间: 2016年5月31日 18:22 收件人: solr-user@lucene.apache.org 主题: Re: help need example code of solrj to get schema of a given core Querying the schema can be done with the Schema API ( https

Re: help need example code of solrj to get schema of a given core

Querying the schema can be done with the Schema API ( https://cwiki.apache.org/confluence/display/solr/Schema+API), which is fully supported by SolrJ: http://lucene.apache.org/solr/6_0_0/solr-solrj/org/apache/solr/client/solrj/request/schema/package-summary.html . Liu, Ming (Ming) <m

help need example code of solrj to get schema of a given core

Hello, I am very new to Solr, I want to write a simple Java program to get a core's schema information. Like how many field and details of each field. I spent a few time searching on internet, but cannot get much information about this. The solrj wiki seems not updated for long time. I am

Re: SolrCloud multiple collections each with unique schema via SolrJ?

Got it! I now use uploadConfig to load the default config for each new collection I create, and then modify the schema. Thanks! -- View this message in context: http://lucene.472066.n3.nabble.com/SolrCloud-multiple-collections-each-with-unique-schema-via-SolrJ-tp4277397p4277406.html Sent from

Re: SolrCloud multiple collections each with unique schema via SolrJ?

On 5/17/2016 7:00 PM, Boman wrote: > I load the defaul config using scripts/cloud-scripts/zkcli.sh -cmd upconfig > after which collections are created programmatically and the schema modified > as per each collection's requirements. > > I now notice that it is the SAME "defa

SolrCloud multiple collections each with unique schema via SolrJ?

I load the defaul config using scripts/cloud-scripts/zkcli.sh -cmd upconfig after which collections are created programmatically and the schema modified as per each collection's requirements. I now notice that it is the SAME "default" original schema that holds ALL the modifications (

Re: BigDecimal Solr Field in schema

n import to use. For something that is not covered by the built-in field classes, you will need a custom solr schema class that knows how to handle your data, and that class will need to use Lucene classes (perhaps those will need to be custom too) to read and write the information in the Lucene index. Therea

BigDecimal Solr Field in schema

Hello All, I am using Solr 6.0.0 in cloud mode and have requirement to support all number in BigDecimal Does anyone know which solr field type should be used for BigDecimal? I tried using DoubleTrieField but it does not meet the requirement and round up very big number approx. after 16 digit.

Re: Schema API

Haddorp wrote: > Hi, > > I have a Solr Cloud 6 setup with a managed schema. It seems like when I > create multiple collections from the same config set that they still > share the same schema. That was rather unexpected, as in the REST and > SolrJ API I do specify a collection whe

Schema API

Hi, I have a Solr Cloud 6 setup with a managed schema. It seems like when I create multiple collections from the same config set that they still share the same schema. That was rather unexpected, as in the REST and SolrJ API I do specify a collection when doing the schema change. Looking

Re: Build Java Package for required schema and solrconfig files field and configuration.

Hi Nitin, If I understand correctly, you have configured suggest component in solr instance. Solr instance is an independent java program and it will be running on its own when you start and stop. You cannot package solr/suggest component in your java application/project. You can use SolrJ apis

Build Java Package for required schema and solrconfig files field and configuration.

Hello Everyone, I have created a autosuggest using Solr suggester. I have added a field and field type in schema.xml and did some changes in /suggest request handler into solrconfig.xml. Now, I need to build a java package using those configuration which I need to plug

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?

You're mixing managed and non-managed schema terms here. "schema.xml" is the old default and is (usually) _not_ editable by the managed schema stuff. Managed schema schemas are usually named just that "managed_schema". You can hand edit this if you want, but when you do I'

Re: Making managed schema unmutable correctly?

Where do I find the shema.xml to hand edit? I can't find it on my node running ZK. I'm not sure what's happening, but when I try to add a field to the schema for one of the collections (I am running in SolrCloud mode), I get: curl -X POST -H 'Content-type:application/json' --data-binary '{ &quo

Re: Adding docValues in schema - Solr Cloud 4.8.1

ry document again. > > The problem with not reindexing is that certain Solr features will > switch to use docValues if the schema says the field has them ... but > until you reindex, your existing documents will not actually contain > docValues, so those features will not work

Re: Adding docValues in schema - Solr Cloud 4.8.1

l switch to use docValues if the schema says the field has them ... but until you reindex, your existing documents will not actually contain docValues, so those features will not work on the majority of your index. Those features will *not* fall back to indexed data if the schema says docValues=&q

Adding docValues in schema - Solr Cloud 4.8.1

to full reindex everything. The question is: what I have to avoid adding docValues to field definition to an existing production collection, or may the partial reindexing switch the collection to an inconsistent situation (or critical)? In other words, should I full reindex immediately after the schema

Re: How to declare field type for IntPoint field in solr 6.0 schema?

Thank you, Shawn! It can wait. There are other features in 6.0 I was waiting for. It is always nice to have such improvements! -- View this message in context: http://lucene.472066.n3.nabble.com/How-to-declare-field-type-for-IntPoint-field-in-solr-6-0-schema-tp4270040p4270256.html Sent from

Re: How to declare field type for IntPoint field in solr 6.0 schema?

On 4/13/2016 8:57 PM, Rafis Ismagilov wrote: > Should it be PointType, BinaryField, or something else. All examples use > TrieIntField for int. Solr doesn't have support for the new Point types in Lucene yet. They are a recent introduction, and Solr was caught a little off guard by how fast

How to declare field type for IntPoint field in solr 6.0 schema?

Should it be PointType, BinaryField, or something else. All examples use TrieIntField for int. Thanks,Rafis

Re: Slor 5.5.0 : SolrException: fieldType 'booleans' not found in the schema

an and other similar fileds and it worked correctly :) > > This has happened because you mixed the solrconfig.xml file from > data_driven_schema_configs with the schema from a completely different > example. > > The config and schema in each example are intended to be used as a > matche

Re: Slor 5.5.0 : SolrException: fieldType 'booleans' not found in the schema

onfig.xml file from data_driven_schema_configs with the schema from a completely different example. The config and schema in each example are intended to be used as a matched pair. If you mix pieces from examples without checking to make sure they are compatible and fixing anything you find,

Re: Slor 5.5.0 : SolrException: fieldType 'booleans' not found in the schema

I think it's a bug... Ah, the key clue is here: Caused by: org.apache.solr.common.SolrException: fieldType 'booleans' not found in the schema at org.apache.solr.update.processor.AddSchemaFieldsUpdateProcessor Factory$TypeMapping.populateValueClasses(AddSchemaFieldsUpdateProcessor Factory.java

Re: Slor 5.5.0 : SolrException: fieldType 'booleans' not found in the schema

Hi Shawn, Finally i'm able to figure out the problem. The issue was in solrconfig.xml where the booleans was defined. I replaced booleans with boolean and other similar fileds and it worked correctly :) Regards, GNT.

Re: Slor 5.5.0 : SolrException: fieldType 'booleans' not found in the schema

Hi Shawn, Thank you for responding and informing me about the attachments. Here is the log file details.. 016-04-01 18:24:08.191 INFO (coreLoadExecutor-6-thread-1) [ x:myDatabase] o.a.s.c.CachingDirectoryFactory looking to close solr-5.5.0\server\solr\myDatabase\data\index

Re: Slor 5.5.0 : SolrException: fieldType 'booleans' not found in the schema

mefield" type="booleans" indexed="true" stored="true"/> You are correct, "booleans" does not show up in that file. Either the schema you sent is not the schema that's actually being used, or the error message that you sent is not a precise copy/paste of

Re: Slor 5.5.0 : SolrException: fieldType 'booleans' not found in the schema

Here is the error message "*myDatabase:* org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: fieldType 'booleans' not found in the schema" On Fri, Apr 1, 2016 at 11:41 PM, Girish Tavag <send2mymail...@gmail.com> wrote: > Hi Jack, > > I copied s

Re: Slor 5.5.0 : SolrException: fieldType 'booleans' not found in the schema

e working example provided by > > solr itself. Solr provided dih example i'm able to run successfully .How > > could this be a problem? > > > > On Fri, Apr 1, 2016 at 12:39 AM, Binoy Dalal <binoydala...@gmail.com> > > wrote: > > > > > Somewhere

Re: Slor 5.5.0 : SolrException: fieldType 'booleans' not found in the schema

Solr provided dih example i'm able to run successfully .How > could this be a problem? > > On Fri, Apr 1, 2016 at 12:39 AM, Binoy Dalal <binoydala...@gmail.com> > wrote: > > > Somewhere in your schema you've defined a field with type as "booleans". > > You shou

Re: Slor 5.5.0 : SolrException: fieldType 'booleans' not found in the schema

that I am including example config info. In your schema, you've got at least one field definition that looks like this -- with the type attribute set to "booleans": But you do NOT have a fieldType definition named "booleans" in your schema, which would look something like thi

Re: Slor 5.5.0 : SolrException: fieldType 'booleans' not found in the schema

Hi Binoy, I copied the entire file schema.xml from the working example provided by solr itself. Solr provided dih example i'm able to run successfully .How could this be a problem? On Fri, Apr 1, 2016 at 12:39 AM, Binoy Dalal <binoydala...@gmail.com> wrote: > Somewhere in your sche

Re: Slor 5.5.0 : SolrException: fieldType 'booleans' not found in the schema

Somewhere in your schema you've defined a field with type as "booleans". You should check if you've made a typo somewhere by adding that extra s after boolean. Else if it is a separate field that you're looking to add, define a new fieldtype called booleans. All the info to help you wit

Slor 5.5.0 : SolrException: fieldType 'booleans' not found in the schema

Hi, I am new to solr, I started using this only from today, when I wanted to create dih, i'm getting the below error. SolrException: fieldType 'booleans' not found in the schema What does this mean? and How to resolve this. Regards, GNT

Re: Making managed schema unmutable correctly?

/ On 17 March 2016 at 04:08, Erick Erickson <erickerick...@gmail.com> wrote: > 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 shoul

Re: Making managed schema unmutable correctly?

Thanks appreciate the feedback. On Wed, Mar 16, 2016 at 8:23 PM, Shawn Heisey <apa...@elyograg.org> 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 wh

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 t

Re: Making managed schema unmutable correctly?

gt; I just made this transition, both to SolrCloud and to managed schema. > In QA and Production, you update solrconfig.xml to say the schema is not > mutable: > > > true > managed-schema > > > My workflow in development is as follows: > > - Start

RE: Making managed schema unmutable correctly?

Alexandre, I just made this transition, both to SolrCloud and to managed schema. In QA and Production, you update solrconfig.xml to say the schema is not mutable: true managed-schema My workflow in development is as follows: - Start with gettingstarted configuration

Would it be better to make my Schema changes within the renamed "/solr-5.3.0/server/solr/configsets/data_driven_schema_configs/conf/schema.xml" instead of the way that I am doing it now via curl -X PO

I noticed that within "/solr-5.3.0/server/solr/configsets/data_driven_schema_configs/conf" it has a file called "managed-schema" and within this file it says "This is the Solr schema file. This file should be named "schema.xml" and should be in the conf direct

Re: Making managed schema unmutable correctly?

the above configuration, you can use the Schema API to modify > the schema as much as you want, and then later change the value of > mutable to false if you wish to "lock" the schema in place and prevent > future changes." > > Which sounds great, except right above t

Re: Making managed schema unmutable correctly?

On Wed, Mar 16, 2016 at 11:10 PM, Erick Erickson <erickerick...@gmail.com> 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: Would it be better to make my Schema changes within the renamed "/solr-5.3.0/server/solr/configsets/data_driven_schema_configs/conf/schema.xml" instead of the way that I am doing it now via curl -

On 3/18/2016 7:31 AM, John Mitchell wrote: > My question would it be better to make my Schema changes within the renamed > "/solr-5.3.0/server/solr/configsets/data_driven_schema_configs/conf/schema.xml" > instead of the way that I am doing it now via curl -X POST -H > 'Co

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, pick

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 <apa...@elyograg.org> wrote: > On 3/16/2016 1:14 AM, Alexandre Ra

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

Re: Solr Managed Schema by Default in 5.5

Data driven mode is different from managed schema. It is unfortunate that in our example configurations we implemented them together. Managed schema is about using APIs to read/write schema changes. Not requiring people to hand edit schema.xml is a good thing, IMO. Data driven schema uses

Re: Solr Managed Schema by Default in 5.5

be I am missing something, if that is the case what is the difference > > between data_driven_schema_configs and basic_configs? I thought that the > > only difference was that the data_driven_schema_configs comes with the > > managed schema and the basic_configs come with regula

Re: Solr Managed Schema by Default in 5.5

On 3/11/2016 9:28 AM, Nick Vasilyev wrote: > Maybe I am missing something, if that is the case what is the difference > between data_driven_schema_configs and basic_configs? I thought that the > only difference was that the data_driven_schema_configs comes with the > ma

Re: Solr Managed Schema by Default in 5.5

Hi Shawn, Maybe I am missing something, if that is the case what is the difference between data_driven_schema_configs and basic_configs? I thought that the only difference was that the data_driven_schema_configs comes with the managed schema and the basic_configs come with regular? Also, I

Re: Solr Managed Schema by Default in 5.5

On 3/11/2016 7:01 AM, Nick Vasilyev wrote: > Is this now the default behavior for basic_configs? I would really like to > maintain an option to easily create collection with classic schema settings > without jumping through all of these hoops. Starting in 5.5, all examples now use th

Solr Managed Schema by Default in 5.5

Hi, I started playing around with Solr 5.5 and created a collection using the following: ./solr create_collection -c test -p 9000 -replicationFactor 2 -d basic_configs -shards 2 The collection created fine, however I see that although I specified basic_configs, it was deployed in managed schema

need help on solr schema design

HI, i am building small search application with solr. i need help in designing the solr schema. data structure is like one to many. when user search text matches with parent document fields, system should not display any child fields information. when user search text matches with child

Re: (Solr 5.5) How do beginners modify dynamic schema now that it is default?

Good point. We should definitely aim for GUI support for adding field types. Perhaps also support a text-field where people can copy-paste a Schema JSON command, e.g. “add-field-type”, that will be processed just as if it was POST’ed. A cool extra feature would be to detect whether people paste

(Solr 5.5) How do beginners modify dynamic schema now that it is default?

Hi, In Solr 5.5, all the shipped examples now use dynamic schema. So, how are they expected to add new types? We have "add/delete fields" UI in the new Admin UI, but not "add/delete types". Do we expect them to use REST end points and curl? Or to not modify types at all? Or e

Fwd: Best Practice to Design Solr Schema in the case of Multistore market place and frequent update

ou.. Sumit Agarwal On Mon, Feb 22, 2016 at 6:35 PM, Sumit Agarwal <2005.su...@gmail.com> wrote: > Dear All,. > > > Please share your input to design schema on the basis of below input? > > > How to design Solr schema in the case of Multi store marketplace > application like

Re: schemaless vs schema based core

Yes, and also underflow in the case of double/float. -- Steve www.lucidworks.com > On Jan 22, 2016, at 12:25 PM, Shyam R <shyam.reme...@gmail.com> wrote: > > I think, schema-less mode might allocate double instead of float, long > instead of int to guard against overflow, whi

Re: schemaless vs schema based core

I think, schema-less mode might allocate double instead of float, long instead of int to guard against overflow, which increases index size. Is my assumption valid? Thanks On Thu, Jan 21, 2016 at 10:48 PM, Erick Erickson <erickerick...@gmail.com> wrote: > I guess it's all abou

Re: schemaless vs schema based core

And, more generally, schemaless makes a series of assumptions, any of which may be wrong. You _must_ hand-tweak your schema to squeeze all the performance out of Solr that you can. If your collection isn't big enough that you need to squeeze, don't bother FWIW, Erick On Fri, Jan 22, 2016

Re: schemaless vs schema based core

Yo. That is the truth. You can get stuff indexed with an automatic schema, but if you want to make your customers happy, tune it. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Jan 22, 2016, at 6:22 PM, Erick Erickson <erickerick...@gma

Recall: schemaless vs schema based core

Prateek Jain J would like to recall the message, "schemaless vs schema based core".

RE: schemaless vs schema based core

. One doubt still remains in mind w.r.t auto-detection of types in solr: Is there a performance benefit of using defined types (schema based) vs un-defined types while adding documents? Does "solrj" ships this meta-information like type of attributes to solr, because code looks somet

Re: schemaless vs schema based core

oring documents on separate disk; we are > storing them in solr but not as backup copies. One doubt still remains in > mind w.r.t auto-detection of types in solr: > > Is there a performance benefit of using defined types (schema based) vs > un-defined types while adding documents? D

Re: schemaless vs schema based core

e _real_ prod environment we need to be more rigorous about the schema", well shortening development time is A Good Thing. Part of moving to prod could be taking the schema generated by schemaless and tweaking it for instance. Best, Erick On Thu, Jan 21, 2016 at 8:54 AM, Shawn Heisey &l

Re: schemaless vs schema based core

I would really avoid schemaless in _any_ situation where I know the schema ahead of time. bq: But in my case, I am planning to use solrj (so, no spelling mistakes) On, I'm quite sure there'll be some kind of mistake sometime ;) I know of at at least one situation where a programming mistake

schemaless vs schema based core

the information required to define schema file for this solr core. Now my question, is there any advantage of using schema based solr against schemaless? What all I could gather from various blogs is, defining schema stops developers from accidently adding fields to solr. But in my case, I am

Re: schemaless vs schema based core

On 1/20/2016 10:17 AM, Prateek Jain J wrote: What all I could gather from various blogs is, defining schema stops developers from accidently adding fields to solr. But in my case, I am planning to use solrj (so, no spelling mistakes). My point is: 1. Is there any advantage like

Re: Parent Child Schema Design

Hi Binay, Are you saying there is no need to add anything to the existing schema that I have ? While indexing all I have to provide is a _childDocuments_ key and the key => value pair as per I want without needing to specify it in the schema.xml ? On Thursday 07 January 2016

Re: Parent Child Schema Design

Yes. Provided your fields are already defined. On Thu, 7 Jan 2016, 17:52 Pranaya Behera <pranaya.beh...@igp.com> wrote: > Hi Binay, >Are you saying there is no need to add anything to the > existing schema that I have ? While indexing all I have to provide is a >

Re: Parent Child Schema Design

To clarify, what I meant was any field that you wish to use either in your child or parent document has to already be defined in the schema. You need to define these fields normally, meaning no you are not required to make any special changes to the field definition for use in either parent

Re: Parent Child Schema Design

On Thu, Jan 7, 2016 at 1:50 PM, Steven White wrote: > How nested can a parent / child document be? And how many child documents > can be in a parent node? No real limit (other than the normal ones... you can't have more than 2B docs in a single segment)... probably just a

Parent Child Schema Design

Hi, I have read yonik.com/solr-nested-objects/ which states that there is no need for additional schema changes other than having a _root_ which is already present in the schema.xml. But it never specified on for the child elements what would the schema look like. And the post actually

Re: Testing Solr configuration, schema, and other fields

ish" it into > ZooKeeper/SolrCloud. > > Working on my own, it is only a very small pain to note foolish errors I've > made, fix them, and restart.However, I want my users to be able to edit > their own Solr schema and config *most* of the time, at least on developmen

RE: Testing Solr configuration, schema, and other fields

not. > > -Original Message- > From: Alexandre Rafalovitch [mailto:arafa...@gmail.com] > Sent: Thursday, December 31, 2015 11:40 AM > To: solr-user <solr-user@lucene.apache.org> > Subject: Re: Testing Solr configuration, schema, and other fields > > Makes sense

Re: Testing Solr configuration, schema, and other fields

and so I've been seeking the > wisdom of the crowd. > > -Original Message- > From: Alexandre Rafalovitch [mailto:arafa...@gmail.com] > Sent: Thursday, December 31, 2015 12:42 AM > To: solr-user <solr-user@lucene.apache.org> > Subject: Re: Testing Solr configuration, schema

RE: Testing Solr configuration, schema, and other fields

negotiate EC2 for dev later this year, maybe not. -Original Message- From: Alexandre Rafalovitch [mailto:arafa...@gmail.com] Sent: Thursday, December 31, 2015 11:40 AM To: solr-user <solr-user@lucene.apache.org> Subject: Re: Testing Solr configuration, schema, and other fields Makes

Re: Testing Solr configuration, schema, and other fields

SolrServer. > > -Original Message- > From: Erik Hatcher [mailto:erik.hatc...@gmail.com] > Sent: Thursday, December 31, 2015 10:00 AM > To: solr-user@lucene.apache.org > Subject: Re: Testing Solr configuration, schema, and other fields > > Dan - I’m a fan of the ide

RE: Testing Solr configuration, schema, and other fields

Sent: Thursday, December 31, 2015 12:42 AM To: solr-user <solr-user@lucene.apache.org> Subject: Re: Testing Solr configuration, schema, and other fields I might be just confused here, but I am not sure what your bottle neck actually is. You seem to know your critical path already, so how

RE: Testing Solr configuration, schema, and other fields

ovitch [mailto:arafa...@gmail.com] Sent: Thursday, December 31, 2015 12:24 PM To: solr-user <solr-user@lucene.apache.org> Subject: RE: Testing Solr configuration, schema, and other fields Well, I guess NIH stands for Not Invented Here. No idea what NLM is for. P.s. sorry, could not resist. I wor

RE: Testing Solr configuration, schema, and other fields

--- From: Erik Hatcher [mailto:erik.hatc...@gmail.com] Sent: Thursday, December 31, 2015 10:00 AM To: solr-user@lucene.apache.org Subject: Re: Testing Solr configuration, schema, and other fields Dan - I’m a fan of the idea of using EmbeddedSolrServer for the type of thing you mention, but since you’re

Re: Testing Solr configuration, schema, and other fields

nly a very small pain to note foolish errors > I've made, fix them, and restart.However, I want my users to be able to > edit their own Solr schema and config *most* of the time, at least on > development servers.They will not have command-line access to these > servers, and

Testing Solr configuration, schema, and other fields

very small pain to note foolish errors I've made, fix them, and restart.However, I want my users to be able to edit their own Solr schema and config *most* of the time, at least on development servers.They will not have command-line access to these servers, and I want to avoid endless rest

RE: Testing Solr configuration, schema, and other fields

[mailto:mhornin...@grayhairsoftware.com] Sent: Wednesday, December 30, 2015 3:25 PM To: solr-user@lucene.apache.org Subject: RE: Testing Solr configuration, schema, and other fields Daniel, Sounds almost like you're reinventing the wheel. Could you possibly automate this through puppet or Chef

RE: Testing Solr configuration, schema, and other fields

a thought on that subject. v/r, -Mark H. -Original Message- From: Davis, Daniel (NIH/NLM) [C] [mailto:daniel.da...@nih.gov] Sent: Wednesday, December 30, 2015 3:10 PM To: solr-user@lucene.apache.org Subject: Testing Solr configuration, schema, and other fields At my organization, I want

RE: Testing Solr configuration, schema, and other fields

I think of enterprise search as very similar to RDBMS: - It belongs in the backend behind your app. - Each project ought to control its own schema and data. So, I want the configset for each team's Solr collections to be stored in our Git server just as the RDBMS schema is if a developer

Re: Testing Solr configuration, schema, and other fields

. The managed schema stuff allows modifications of the schema via REST calls and there is some equivalent functionality for solrconfig.xml, but the interesting bit about that is that then your VCS is not the "one true source" of the configs, it almost goes backwards: Modify the configs in

Re: Changing Solr Schema with Data

> > Solr as well. > > > > Thanks for your help. > > > > Regards, > > Salman > > > > > > On Tue, Dec 29, 2015 at 9:44 AM, Shalin Shekhar Mangar < > > shalinman...@gmail.com> wrote: > > > > > Adding new fields is not

Re: Changing Solr Schema with Data

that this is possible in the old Solr as well. Thanks for your help. Regards, Salman On Tue, Dec 29, 2015 at 9:44 AM, Shalin Shekhar Mangar < shalinman...@gmail.com> wrote: > Adding new fields is not a problem. You can continue to use your > existing index with the new schema. > &

Re: Changing Solr Schema with Data

mail.com> wrote: > > > Adding new fields is not a problem. You can continue to use your > > existing index with the new schema. > > > > On Tue, Dec 29, 2015 at 1:58 AM, Salman Ansari <salman.rah...@gmail.com> > > wrote: > > > You can say that we

<    1   2   3   4   5   6   7   8   9   10   >