RE: Query over migrating a solr database from 7.7.1 to 8.7.0

by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all devices. -Original Message- From: Flowerday, Matthew J Sent: 15 January 2021 11:18 To: solr-user@lucene.apache.org Subject: RE: Query over migrating

RE: Query over migrating a solr database from 7.7.1 to 8.7.0

endon | Milton Keynes | MK17 8LX <http://www.unisys.com/> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its a

RE: Query over migrating a solr database from 7.7.1 to 8.7.0

I think if you have _root_ in schema.xml you should look elsewhere. My memory is merely adding this one line to schema.xml took care of our problem. From: Flowerday, Matthew J Sent: Tuesday, January 12, 2021 3:23 AM To: solr-user@lucene.apache.org Subject: RE: Query over migrating a solr

RE: Query over migrating a solr database from 7.7.1 to 8.7.0

Jim Sent: 11 January 2021 22:58 To: solr-user@lucene.apache.org Subject: RE: Query over migrating a solr database from 7.7.1 to 8.7.0 EXTERNAL EMAIL - Be cautious of all links and attachments. When we upgraded from 7.x to 8.x, I ran into an issue similar to yours: when updating an existing documen

RE: Query over migrating a solr database from 7.7.1 to 8.7.0

a feature was added for nested documents, this field somehow became mandatory in order for updates to work properly, at least in some cases. From: Flowerday, Matthew J Sent: Saturday, January 9, 2021 4:44 AM To: solr-user@lucene.apache.org Subject: RE: Query over migrating a solr database from 7.7.

RE: Re:Query over migrating a solr database from 7.7.1 to 8.7.0

linkedin.com/company/unisys><http://twitter.com/unisyscorp> <http://www.youtube.com/theunisyschannel> <http://www.facebook.com/unisyscorp> <https://vimeo.com/unisys> <http://blogs.unisys.com/> From: matthew sporleder Sent: 10 January 2021 21:38 To: solr-use

Re: Re:Query over migrating a solr database from 7.7.1 to 8.7.0

RY > MATERIAL and is for use only by the intended recipient. If you received > this in error, please contact the sender and delete the e-mail and its > attachments from all devices. > > [image: Grey_LI] <http://www.linkedin.com/company/unisys> [image: > Grey_TW] <htt

Re:Query over migrating a solr database from 7.7.1 to 8.7.0

can you show the update request? At 2021-01-07 20:25:13, "Flowerday, Matthew J" wrote: Hi There I have recently upgraded a solr database from 7.7.1 to 8.7.0 and not wiped the database and re-indexed (as this would take too long to run on site). On my local windows

Re: Query over migrating a solr database from 7.7.1 to 8.7.0

; > > > > > > > From: Flowerday, Matthew J > Sent: 07 January 2021 12:25 > To: solr-user@lucene.apache.org > Subject: Query over migrating a solr database from 7.7.1 to 8.7.0 > > Hi There > > I have recently upgraded a solr database from 7.7.1

RE: Query over migrating a solr database from 7.7.1 to 8.7.0

m/unisyscorp> <https://vimeo.com/unisys> <http://blogs.unisys.com/> From: Flowerday, Matthew J Sent: 07 January 2021 12:25 To: solr-user@lucene.apache.org Subject: Query over migrating a solr database from 7.7.1 to 8.7.0 Hi There I have recently upgraded a solr databas

Query over migrating a solr database from 7.7.1 to 8.7.0

Hi There I have recently upgraded a solr database from 7.7.1 to 8.7.0 and not wiped the database and re-indexed (as this would take too long to run on site). On my local windows machine I have a single solr server 7.7.1 installation I upgraded in the following manner *

Migrating from solr 7.7 to solr 8.6 issues

We are trying to migrate from solr 7.7 to solr 8.6 on Kubernetes. We are using zookeeper-3.4.13. While adding a replica to the cluster, it returns 500 status code. While in the background it is added sometimes successfully while sometime it is in the inactive node. We are using http2 without SSL.

Re: Default Searches not working after migrating from Solr 4.7 to 7.3

Ok this is fixed. the _text_<\df> was not the issue. Certain copyFields had to be changed from dest="text" to dest="_text_". this issue is closed. thank you -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Default Searches not working after migrating from Solr 4.7 to 7.3

On 5/17/2018 7:23 AM, THADC wrote: , however for 7.3, "defaultSearchField" apparently no longer a valid type. I switched to "df". Also, "text" is no longer default data type, but rather "_text_". So, I replaced above with: _text_ , but still default search not working properly. By the way,

Default Searches not working after migrating from Solr 4.7 to 7.3

Hello, Migrating our system from solr 4.7 to 7.3. Simple default searches are not working. For our simply searches, we had the following in our schema.xml for 4.7: text , however for 7.3, "defaultSearchField" apparently no longer a valid type. I switched to "df". Also, "text" is no longer

RE: change in the Standard Query Parser behavior when migrating from Solr 5 to 7.

To: solr-user@lucene.apache.org Subject: Re: change in the Standard Query Parser behavior when migrating from Solr 5 to 7. On 5/9/2018 2:37 PM, Piyush Kumar Nayak wrote: > Same here. "sow" restores the old behavior. This might be a bug.  I'd like someone who has better understanding of t

Re: change in the Standard Query Parser behavior when migrating from Solr 5 to 7.

On 5/9/2018 2:37 PM, Piyush Kumar Nayak wrote: > Same here. "sow" restores the old behavior. This might be a bug.  I'd like someone who has better understanding of the low-level internals to comment before assuming that it's a bug, though.  Sounds like sow=false (default as of 7.0) might be

RE: change in the Standard Query Parser behavior when migrating from Solr 5 to 7.

(WT, SF ...) in 7 list a property (termFrequency = 1) that is missing in 5. Lemme see if I can share the schemas. -Original Message- From: David Hastings [mailto:hastings.recurs...@gmail.com] Sent: Thursday, May 10, 2018 1:38 AM To: solr-user@lucene.apache.org Subject: Re: change in the

Re: change in the Standard Query Parser behavior when migrating from Solr 5 to 7.

sow=true made 7 mimic 5. On Wed, May 9, 2018 at 3:57 PM, Shawn Heisey wrote: > On 5/9/2018 1:25 PM, David Hastings wrote: > > https://pastebin.com/0QUseqrN > > > > here is mine for an example with the exact same behavior > > Can you try the query in the Analysis tab in

Re: change in the Standard Query Parser behavior when migrating from Solr 5 to 7.

On 5/9/2018 1:25 PM, David Hastings wrote: > https://pastebin.com/0QUseqrN > > here is mine for an example with the exact same behavior Can you try the query in the Analysis tab in the admin UI on both versions and see which step in the analysis chain is the point at which the two diverge from

Re: change in the Standard Query Parser behavior when migrating from Solr 5 to 7.

id rather not at least on my part, but in both cases i have: and text as my default field, changed from text_general On Wed, May 9, 2018 at 3:43 PM, Shawn Heisey wrote: > On 5/9/2018 1:25 PM, David Hastings wrote: > > https://pastebin.com/0QUseqrN > > Can you provide

Re: change in the Standard Query Parser behavior when migrating from Solr 5 to 7.

On 5/9/2018 1:25 PM, David Hastings wrote: > https://pastebin.com/0QUseqrN Can you provide the *full* schema for both versions? Thanks, Shawn

Re: change in the Standard Query Parser behavior when migrating from Solr 5 to 7.

https://pastebin.com/0QUseqrN here is mine for an example with the exact same behavior On Wed, May 9, 2018 at 3:14 PM, Shawn Heisey wrote: > On 5/9/2018 12:39 PM, Piyush Kumar Nayak wrote: > > we have recently upgraded from Solr5 to Solr7. I'm running into a change > of

Re: change in the Standard Query Parser behavior when migrating from Solr 5 to 7.

On 5/9/2018 12:39 PM, Piyush Kumar Nayak wrote: > we have recently upgraded from Solr5 to Solr7. I'm running into a change of > behavior that I cannot fathom. > For the term "test3" Solr7 splits the numeric and alphabetical components and > does a simple term search while Solr 5 did a phrase

Re: change in the Standard Query Parser behavior when migrating from Solr 5 to 7.

Strange, I have the exact same results, whats more interesting is the analyzer shows identical for both 5 and 7, so its definetly a change in the LuceneQParser On Wed, May 9, 2018 at 2:39 PM, Piyush Kumar Nayak wrote: > we have recently upgraded from Solr5 to Solr7.

change in the Standard Query Parser behavior when migrating from Solr 5 to 7.

we have recently upgraded from Solr5 to Solr7. I'm running into a change of behavior that I cannot fathom. For the term "test3" Solr7 splits the numeric and alphabetical components and does a simple term search while Solr 5 did a phrase search.

Re: Migrating from Solr 6.6 getStatistics() to Solr 7.x

Thank you! On Fri, Apr 6, 2018 at 10:34 PM, Chris Hostetter wrote: > > : In my Solr 6.6 based code, I have the following line that get the total > : number of documents in a collection: > : > : totalDocs=indexSearcher.getStatistics().get("numDocs")) > ... > :

Re: Migrating from Solr 6.6 getStatistics() to Solr 7.x

: In my Solr 6.6 based code, I have the following line that get the total : number of documents in a collection: : : totalDocs=indexSearcher.getStatistics().get("numDocs")) ... : With Solr 7.2.1, 'getStatistics' is no longer available, and it seems that : it is replaced by

Migrating from Solr 6.6 getStatistics() to Solr 7.x

Hi all In my Solr 6.6 based code, I have the following line that get the total number of documents in a collection: totalDocs=indexSearcher.getStatistics().get("numDocs")) where indexSearcher is an instance of "SolrIndexSearcher". With Solr 7.2.1, 'getStatistics' is no longer available, and

Re: Migrating from Solr 6.X to Solr 7.X: "non legacy mode coreNodeName missing"

If at all possible you shouldn't run with legacyCloud=true. I was just mentioning that in order to see if that was the place to start looking, I could have been clearer. Let's back up a bit though. I just tried this creating a collection with 6.6.0, changing to 7.1.0 and I can add replicas just

Re: Migrating from Solr 6.X to Solr 7.X: "non legacy mode coreNodeName missing"

Thanks Erick, I've looked over the documentation. Quick follow-up question: What are the consequences of running with legacyCloud=true? Would I need to point a new Solr cluster at a new Zookeeper instance to avoid this? Many thanks! -Dave On Mon, Oct 30, 2017 at 1:36 PM, Erick Erickson

Re: Migrating from Solr 6.X to Solr 7.X: "non legacy mode coreNodeName missing"

empty clusterstate.json node. OK, you're on state format 2 (the modern one) so that's good. No need to MIGRATESTATE The admin UI>>cloud>>tree view should have a cluster.properties (IIRC the name correctly, it'll be fairly obvious). If you have no non-default values it'll be totally missing. It's

Re: Migrating from Solr 6.X to Solr 7.X: "non legacy mode coreNodeName missing"

> You may have to set legacyCloud=true in your cluster properties > Check your cluster properties (top level znode in ZooKeeper). How would I check this? Would it appear in the Solr Cloud interface, or do I have to query Zookeeper? > Or, try the MIGRATESTATEFORMAT collection API on your 6x

Re: Migrating from Solr 6.X to Solr 7.X: "non legacy mode coreNodeName missing"

You may have to set legacyCloud=true in your cluster properties. In the Solr reference guide (7.0) there's a section "Changes to Default Behaviors" that'll tell you a bit about that. Check your cluster properties (top level znode in ZooKeeper). Or, try the MIGRATESTATEFORMAT collection API on

Migrating from Solr 6.X to Solr 7.X: "non legacy mode coreNodeName missing"

I have a Solr collection with 1 shard and around 40 replicas hosted on Solr 6.6.0 I added a Solr 7.1 server to the cluster and then tried to add a replica (ADDREPLICA) onto the new server but got this message: > Error CREATEing SolrCore 'content_collection_20171013_shard1_replica37': non legacy

Re: Excessive resources consumption migrating from Solr 6.6.0 Master/Slave to SolrCloud 6.6.0 (dozen times more resources)

Dani, It might be time to attach some instrumentation to one of your nodes. Finding out which classes are occupying the memory will help narrow the issue. Are you using a lot of facets, grouping, or stats during your queries? Also, when you were doing Master/Slave, was that on the same version

Re: Excessive resources consumption migrating from Solr 6.6.0 Master/Slave to SolrCloud 6.6.0 (dozen times more resources)

Hi Scott, Yes, we think that our usage scenario falls into Index-Heavy/Query-Heavy too. We have tested with several values in softcommit/hardcommit values (from few seconds to minutes) with no appreciable improvements :( Thanks for your reply! - Daniel 2017-08-25 6:45 GMT+02:00 Scott Stults

Re: Excessive resources consumption migrating from Solr 6.6.0 Master/Slave to SolrCloud 6.6.0 (dozen times more resources)

Hi Dani, It seems like your use case falls into the Index-Heavy / Query-Heavy category, so you might try increasing your hard commit frequency to 15 seconds rather than 15 minutes: https://lucidworks.com/2013/08/23/understanding-transaction-logs-softcommit-and-commit-in-sorlcloud/ -Scott On

Re: Excessive resources consumption migrating from Solr 6.6.0 Master/Slave to SolrCloud 6.6.0 (dozen times more resources)

Hi Scott, In our indexing service we are using that client too (org.apache.solr.client.solrj.impl.CloudSolrClient) :) This is out Update Request Processor chain configuration: true hash false solr.processor.Lookup3Signature < updateRequestProcessorChain processor="signature" name="dedupe">

Re: Excessive resources consumption migrating from Solr 6.6.0 Master/Slave to SolrCloud 6.6.0 (dozen times more resources)

Hi Daniel, SolrJ has a few client implementations to choose from: CloudSolrClient, ConcurrentUpdateSolrClient, HttpSolrClient, LBHttpSolrClient. You said your query service uses CloudSolrClient, but it would be good to verify which implementation your indexing service uses. One of the problems

Re: Excessive resources consumption migrating from Solr 6.6.0 Master/Slave to SolrCloud 6.6.0 (dozen times more resources)

Hi Scott, - *Can you describe the process that queries the DB and sends records to * *Solr?* We are enqueueing ids during every ORACLE transaction (in insert/updates). An application dequeues every id and perform queries against dozen of tables in the relational model to retrieve the fields to

Re: Excessive resources consumption migrating from Solr 6.6.0 Master/Slave to SolrCloud 6.6.0 (dozen times more resources)

Hi Daniel, Great background information about your setup! I've got just a few more questions: - Can you describe the process that queries the DB and sends records to Solr? - Is it a SolrJ-based application? - If it is, which client package are you using? - How many documents do you send at once?

Excessive resources consumption migrating from Solr 6.6.0 Master/Slave to SolrCloud 6.6.0 (dozen times more resources)

*Main Problems* We are involved in a migration from Solr Master/Slave infrastructure to SolrCloud infrastructure. The main problems that we have now are: - Excessive resources consumption: Currently we have 5 instances with 80 processors/768 GB RAM each instance using SSD Hard Disk

RE: Migrating to Solr 6.1.0 from 5.5.0

tial+Search --Arjun -Original Message- From: David Smiley [mailto:david.w.smi...@gmail.com] Sent: Thursday, September 29, 2016 8:03 PM To: solr-user@lucene.apache.org Subject: Re: Migrating to Solr 6.1.0 from 5.5.0 Arjun, Your input is a POLYGON -- as seen in the error message. The "Try J

Re: Migrating to Solr 6.1.0 from 5.5.0

on this. Not sure how to fix it either. > > On Tue, Sep 27, 2016 at 3:41 AM, M, Arjun (Nokia - IN/Bangalore) < > arju...@nokia.com> wrote: > > > Hi, > > > > We are getting the below errors when migrating Solr from 5.5.0 to > > 6

Re: Migrating to Solr 6.1.0 from 5.5.0

the documentation is not good on this. Not sure how to fix it either. On Tue, Sep 27, 2016 at 3:41 AM, M, Arjun (Nokia - IN/Bangalore) < arju...@nokia.com> wrote: > Hi, > > We are getting the below errors when migrating Solr from 5.5.0 to > 6.1.0. Could anyone help in r

Migrating to Solr 6.1.0 from 5.5.0

Hi, We are getting the below errors when migrating Solr from 5.5.0 to 6.1.0. Could anyone help in resolving the issue, if you have come across this? org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error from server at http://127.0.0.1:41569/solr

Re: Migrating from Solr 5.4 to Solr 6.0

ndex. > M. > > -Original message- > > From:Zheng Lin Edwin Yeo <edwinye...@gmail.com> > > Sent: Wednesday 4th May 2016 13:27 > > To: solr-user@lucene.apache.org > > Subject: Migrating from Solr 5.4 to Solr 6.0 > > > > Hi, > > > > Would like to

RE: Migrating from Solr 5.4 to Solr 6.0

No, you don't need to reindex. M. -Original message- > From:Zheng Lin Edwin Yeo <edwinye...@gmail.com> > Sent: Wednesday 4th May 2016 13:27 > To: solr-user@lucene.apache.org > Subject: Migrating from Solr 5.4 to Solr 6.0 > > Hi, > > Would like to find o

Migrating from Solr 5.4 to Solr 6.0

Hi, Would like to find out, do we need to re-index our document when we migrate from Solr 5.4 to Solr 6.0 because of the change in scoring algorithm to BM25? Regards, Edwin

Some errors migrating to solr cloud

I had a fairly simple plan for migrating my single solr instance with multiple cores, to a solrcloud implementation where core => collection. My testing locally (windows) worked fine, but the first linux (development) environment I tried to migrate had some failures. This is v5.2.1. The se

Re: Migrating from solr cores to collections

After playing with SolrCloud I answered my own question: multiple collections can live on the same node. Following the how-to in the solr-ref-guide was getting me confused. -- View this message in context: http://lucene.472066.n3.nabble.com/Migrating-from-solr-cores-to-collections

Migrating from solr cores to collections

to be ... is it better to have one massive JVM per physical server, or lots and lots of small ones? Thanks! running 4.10 now but considering upgrading to 5.x -- View this message in context: http://lucene.472066.n3.nabble.com/Migrating-from-solr-cores-to-collections-tp4217346.html Sent from the Solr - User

Re: Migrating from solr cores to collections

On 7/14/2015 2:39 PM, tedsolr wrote: I am in the process of migrating from a single Solr instance, with multiple cores, to the SolrCloud. My product uses cores to physically separate our customers' data: CocaCola has its own core, Pepsi has its own, etc. I want to keep that physical separation

Re: Migrating from solr 1.4.1 to 4.7

On 7/7/2015 4:08 AM, anil.chandgude wrote: currently I am using apache-solr1.4 which does not contain lucene internally .So w used lucene 2.9 jar for that to get work. Now we want to migrate from solr version 1.4 to 4.7 due to jdk version issue(we have jdk1.6 only ) But before migrating

Migrating from solr 1.4.1 to 4.7

hello, currently I am using apache-solr1.4 which does not contain lucene internally .So w used lucene 2.9 jar for that to get work. Now we want to migrate from solr version 1.4 to 4.7 due to jdk version issue(we have jdk1.6 only ) But before migrating to 4.7 , I am trying solr3.1.0

Re: Migrating from Solr 5.1 to Solr 5.2.1

Thank you Timothy. I've managed to start Solr 5.2.1 by using bin\solr.cmd. However, I could not get it to start it together with 3 instances of external ZooKeeper with this command - bin\solr.cmd -e cloud -z localhost:2181,localhost:2182,localhost:2183 I'll get the error *Invalid command-line

Re: Migrating from Solr 5.1 to Solr 5.2.1

I tried to put the 3 ZooKeeper ports together with the double-quotes and it works. - bin\solr.cmd -p 8983 -s example\node1\solr -z localhost:2181,localhost:2182,localhost:2183 Regards, Edwin On 7 July 2015 at 10:59, Zheng Lin Edwin Yeo edwinye...@gmail.com wrote: Thank you Timothy. I've

RE: Migrating from Solr 5.1 to Solr 5.2.1

@lucene.apache.org Subject: Re: Migrating from Solr 5.1 to Solr 5.2.1 I tried to put the 3 ZooKeeper ports together with the double-quotes and it works. - bin\solr.cmd -p 8983 -s example\node1\solr -z localhost:2181,localhost:2182,localhost:2183 Regards, Edwin On 7 July 2015 at 10:59, Zheng Lin

Re: Migrating from Solr 5.1 to Solr 5.2.1

: +6010-2288030 -Original Message- From: Zheng Lin Edwin Yeo [mailto:edwinye...@gmail.com] Sent: Tuesday, July 7, 2015 11:46 AM To: solr-user@lucene.apache.org Subject: Re: Migrating from Solr 5.1 to Solr 5.2.1 I tried to put the 3 ZooKeeper ports together with the double-quotes

Re: Migrating from Solr 5.1 to Solr 5.2.1

Hi Edwin, You'll need to use the bin\solr.cmd to start Solr as it now requires some additional system properties to be set. Put simply, starting solr using java -jar start.jar is not supported. Please try bin\solr.cmd and let us know if you run into any issues. You can set any additional system

Migrating from Solr 5.1 to Solr 5.2.1

Hi, I'm trying to migrate from Solr 5.1 to Solr 5.2.1. However, I faced some problems when I'm trying to migrate my index over, and when I'm trying to link up the external ZooKeeper to Solr. I'm using ZooKeeper 3.4.6 In Solr 5.1, I used this command to start Solr for both Shard1 and Shard2:

Migrating from solr 3.5 to 4.4

Hi, We are migrating or solr from 3.5 to 4.4, but stuck at the strategy to migrate the index. I read that we can point the new solr 4.4 to the data index from previous solr i.e. 3.5. Is my understanding correct? If this is true, can we change the schema in 4.4 solr. We have many un

Re: Migrating from solr 3.5 to 4.4

.nabble.com/Migrating-from-solr-3-5-to-4-4-tp4085049p4085051.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Migrating from solr 3.5 to 4.4

On 8/16/2013 6:43 AM, Kuchekar wrote: If we do a csv export from 3.5 solr and then import it in the 4.4 index, we get a problem with copy fields i.e. the value in the copy field is computed twice. Once from the csv import and other from solr internal computation. Supplemental reply on

Re: Migrating from Solr 3.6.1 to Solr 4

encapsulating the response and response content. Greetings! - Mensaje original - De: Upayavira u...@odoko.co.uk Para: solr-user@lucene.apache.org Enviados: Sábado, 5 de Enero 2013 4:49:01 Asunto: Re: Migrating from Solr 3.6.1 to Solr 4 Try pointing your app at 4.0. I converted an app

Migrating from Solr 3.6.1 to Solr 4

Hi: I'm currently working with solr 3.6.1, but solr 4 has great features like the ones bundled with SolrCloud, the content in the index is really not the problem to the transition, the thing is that I've a large app written in PHP + Solarium that interacts with the index in solr 3. As far as I

Re: Migrating from Solr 3.6.1 to Solr 4

Try pointing your app at 4.0. I converted an app recently. Here's the steps I took (as I recall): * get original solrconfig.xml for the release I'm using * diff that and my solrconfig.xml * apply those changes to a 4.0 solrconfig.xml * try to start up solr with this new solrconfig and an old

Re: Migrating from Solr 3.6.1 to Solr 4

high level objects encapsulating the response and response content. Greetings! - Mensaje original - De: Upayavira u...@odoko.co.uk Para: solr-user@lucene.apache.org Enviados: Sábado, 5 de Enero 2013 4:49:01 Asunto: Re: Migrating from Solr 3.6.1 to Solr 4 Try pointing your app at 4.0. I

Timeout when calling Luke request handler after migrating from Solr 3.5 to 3.6.1

Hi all, As part of our business logic we query the Luke request handler to extract the fields in the index from our code using the following url: http://server:8080/solr/admin/luke?wt=jsonnumTerms=0 This worked fine with Solr 3.5, but now with 3.6.1 this call never returns, it hangs, and

Re: Lucene version error after migrating to Solr 3.5

After migrating to Solr 3.5, i restart tomcat and i get the error below. Any ideas what i am doing wrong? SEVERE: org.apache.solr.common.SolrException: Invalid luceneMatchVersion 'LUCENE_35', valid values are: [LUCENE_20, LUCENE_21, LUCENE_22, LU CENE_23, LUCENE_24, LUCENE_29, LUCENE_30

Re: Lucene version error after migrating to Solr 3.5

OK, migrating to Solr 3.5 from what? But what it *looks* like is that you are running a 3.5 config (see luceneMatchVersion in solrconfig.xml) against a 3.3 Solr installation. In other words it might be that you're running the old code against a new schema. But I'll freely admit

Re: Migrating from solr 1.4.1 to 3.1.0

: Solr 3.1.0 uses different javabin format from 1.4.1 : So if I use Solrj 1.4.1 jar , then i get javabin error while saving to : 3.1.0 : and if I use Solrj 3.1.0 jar , then I get javabin error while reading the : document from solr 1.4.1. you can use the XML format to get portability during

Migrating from solr 1.4.1 to 3.1.0

Hi all, Solr 3.1.0 uses different javabin format from 1.4.1 So if I use Solrj 1.4.1 jar , then i get javabin error while saving to 3.1.0 and if I use Solrj 3.1.0 jar , then I get javabin error while reading the document from solr 1.4.1. How to go for reindexing in this situation. -- Thanks

Re: Migrating to Solr

: is this true, no downloaded copy of the documentprocessor : anywhere available? By the looks of that URL the SVN respository seems to have been hozed -- but more the point if people have questions about sesat.no code, then perhaps you should try emailing the Contact us address at the bottom

Re: Migrating to Solr

Hi list, is this true, no downloaded copy of the documentprocessor anywhere available? Regards, Bernd Bernd Fehling schrieb: Was anyone able to get a copy of: http://sesat.no/svn/sesat-documentprocessor/ Unfortunately it is offline. Would be pleased to get a copy. Regards, Bernd

Re: migrating from solr 1.3 to 1.4

On Fri, Feb 12, 2010 at 19:46, Sachin Sebastian sac...@gossamer-threads.com wrote: Hi there,       I'm trying to migrate from solr 1.3 to solr 1.4 and I've few issues. Initially my localsolr was throwing NullPointer exception and I fixed it by changing type of lat and lng to 'tdouble'. But

migrating from solr 1.3 to 1.4

Hi there, I'm trying to migrate from solr 1.3 to solr 1.4 and I've few issues. Initially my localsolr was throwing NullPointer exception and I fixed it by changing type of lat and lng to 'tdouble'. But now I'm not able to update index. When I try to update index it throws out error

Re: Need help Migrating to Solr

I've done a fair number of migrations, but it's kind of hard to give generic advice on it. Specific questions as you dig in would be best. I'd probably, at least, just start with a simple schema that models most of your data and get Solr up and ingesting it. Then run some queries against it

Re: Need help Migrating to Solr

Hi, since we did some kind of migration in a similar situation in the recent past, I might add some (hopefully helpful) remarks: If You use a Lucene-based application right now, You might already have an idea of which fields You want to store in Solr. Since You already do analyzing of

RE: Need help Migrating to Solr

@lucene.apache.org Subject: Need help Migrating to Solr Hi I am new to the solr technology. We have been using lucene for handling searching in our web application www.toostep.com which is a knowledge sharing platform developed in java using Spring MVC architecture and iBatis as the persistance framework

Need help Migrating to Solr

Hi I am new to the solr technology. We have been using lucene for handling searching in our web application www.toostep.com which is a knowledge sharing platform developed in java using Spring MVC architecture and iBatis as the persistance framework. Now that the application is getting very

Migrating to Solr

Hi, I'm new at Solr and i need to make a test pilot of a migration from Fast ESP to Apache Solr, anyone had this experience before? Att,

Re: Migrating to Solr

Hi, I think there were some links about FAST to Solr migration published recently. See: http://blog.isabel-drost.de/index.php/archives/110/moving-from-fast-to-solr However, as of writing those links are not working, not sure what happend... Regards, Lukas On Tue, Nov 24, 2009 at 2:55 PM, Tommy

Re: Migrating to Solr

I've done been involved with a fair share of these migrations now, what are you looking for? On Nov 24, 2009, at 8:55 AM, Tommy Molto wrote: Hi, I'm new at Solr and i need to make a test pilot of a migration from Fast ESP to Apache Solr, anyone had this experience before? Att,

Re: Migrating to Solr

Here is a link that might be helpful: http://sesat.no/moving-from-fast-to-solr-review.html The site is choc-a-bloc with great information on their migration experience. On Tue, Nov 24, 2009 at 8:55 AM, Tommy Molto tommymo...@gmail.com wrote: Hi, I'm new at Solr and i need to make a test

Re: Migrating to Solr

This is really a great source of migration. I guess i will have good questions after trying. But what i know that will be a little harder will be the use of collections (facets in Solr) and hierarquical navigators. On Tue, Nov 24, 2009 at 1:05 PM, Shashi Kant sk...@sloan.mit.edu wrote: Here is

Re: Migrating to Solr

Except http://sesat.no/ hasn't been reachable for about 2 days now Google cache to the rescue! Otis - Original Message From: Shashi Kant sk...@sloan.mit.edu To: solr-user@lucene.apache.org Sent: Tue, November 24, 2009 10:05:30 AM Subject: Re: Migrating to Solr Here