Re: Version Migration from solr 1.3

If you have time, you might as well wait for 4.0 to be released otherwise 3.6.1 -- View this message in context: http://lucene.472066.n3.nabble.com/Version-Migration-from-solr-1-3-tp4006193p4006200.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Version Migration from solr 1.3

I see that 4.0 alpha has been release after 3.6.1 , so should I look at 3.5 as the most stable release currently? Version Source : https://issues.apache.org/jira/browse/SOLR?selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel Regards Sujatha On Fri, Sep 7, 2012 at 11:17 PM, Su

Re: Porting from Solr 1.3 to 3.5

On Thu, Jun 7, 2012 at 1:18 PM, Ramprakash Ramamoorthy < youngestachie...@gmail.com> wrote: > I am porting my app from lucene 2.X(solr 1.3) to lucene 3.X(solr 3.5). The > following is my issue. > > This one was valid in 2.X, but 3.5 throws me an error. > > IndexReader r

Porting from Solr 1.3 to 3.5

I am porting my app from lucene 2.X(solr 1.3) to lucene 3.X(solr 3.5). The following is my issue. This one was valid in 2.X, but 3.5 throws me an error. IndexReader reader = IndexReader.open("/home/path/to/my/dataDir"); 2.X accepted a string, but 3.5 strictly wants a Directory obje

Re: solr 1.3 Multicores and maxboolean clause

al Message- From: Sujatha Arun > Sent: Wednesday, May 30, 2012 1:30 PM > To: solr-user@lucene.apache.org > Subject: solr 1.3 Multicores and maxboolean clause > > > Hello, > > The solrcore Wiki says that "Lucene's > BooleanQuery<http://wiki.**apache.

Re: solr 1.3 Multicores and maxboolean clause

pansky -Original Message- From: Sujatha Arun Sent: Wednesday, May 30, 2012 1:30 PM To: solr-user@lucene.apache.org Subject: solr 1.3 Multicores and maxboolean clause Hello, The solrcore Wiki says that "Lucene's BooleanQuery<http://wiki.apache.org/solr/BooleanQuery>maxCl

solr 1.3 Multicores and maxboolean clause

Hello, The solrcore Wiki says that "Lucene's BooleanQuerymaxClauseCount is a static variable, making it a single value across the entire JVM. Whichever Solr core initializes last will win the setting of the solrconfig.xml's maxBooleanClauses value. Workaro

Moving from Multiple webapps to Multi Cores -Solr 1.3

Hello All, On Protyping from moving from solr Multiple Webapps to Solr Multi Cores [1.3 Version both]..I am running into the following issues and Questions 1) We are primarily moving to Multicore because ,we saw the Permgen memory being increased ,each time we created a new solr webapp ,so t

Re: Solr 1.3 highlighting problem

Hi Markus, thanks for the tip. I replaced the string field with a tokenizer field and now it works. Thank you! Kind regards, Nick -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-1-3-highlighting-problem-tp2918089p2922785.html Sent from the Solr - User mailing list arch

Re: Solr 1.3 highlighting problem

Oh! I did't see the "string" - Thanx: Grijesh www.gettinhahead.co.in -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-1-3-highlighting-problem-tp2918089p2922532.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Solr 1.3 highlighting problem

You're using the string fieldType to get highlighting to work but it must be tokenized. Use a fieldType with a tokenizer. See also: http://wiki.apache.org/solr/FieldOptionsByUseCase > Hi, > > I'm using the "old" 1.3 Solr version on one of my sites and I decided to > add a highlighting feature.

Re: Solr 1.3 highlighting problem

I indeed changed the type from unstored to stored. But I did do a reindex (several times already) and a commit, restarted Tomcat, restarted PC, nothing works. When I do a search the text field shows up in the results. But that is the only thing that has changed. tag only shows id's. I have no idea

Re: Solr 1.3 highlighting problem

Have you recently change its type from unstored to stored? if so you have to reindex . - Thanx: Grijesh www.gettinhahead.co.in -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-1-3-highlighting-problem-tp2918089p2922117.html Sent from the Solr - User mailing list arc

Re: Solr 1.3 highlighting problem

Hi Grijesh, The field text is stored and yet it is not working. Kind regards, Nick -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-1-3-highlighting-problem-tp2918089p2918518.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Solr 1.3 highlighting problem

Whether your field text is stored or not? Highlighting works with stored fields of schema only. - Thanx: Grijesh www.gettinhahead.co.in -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-1-3-highlighting-problem-tp2918089p2918299.html Sent from the Solr - User mailing

Solr 1.3 highlighting problem

Hi, I'm using the "old" 1.3 Solr version on one of my sites and I decided to add a highlighting feature. Unfortunately I can not get it to work. I'm doing some testing in the Sorl admin interface without much luck. Below is some information that describes the problem. I would like to highlight te

Re: Solr 1.4.1 using more memory than Solr 1.3

http://svn.apache.org/repos/asf/lucene/solr/branches/branch-1.4/CHANGES.txt On Wednesday 09 February 2011 16:07:01 Rachita Choudhary wrote: > Hi Solr Users, > > We are in the process of upgrading from Solr 1.3 to Solr 1.4.1. > While performing stress test on Solr 1.4.1 to measure the performa

Solr 1.4.1 using more memory than Solr 1.3

Hi Solr Users, We are in the process of upgrading from Solr 1.3 to Solr 1.4.1. While performing stress test on Solr 1.4.1 to measure the performance improvement in Query times (QTime) and no more blocked threads, we ran into memory issues with Solr 1.4.1. Test Setup details: - 2 identical hosts

Re: geospatial search support for SOLR 1.3 and 1.4?

n 1.3. But we only used it to show near by items for a given document, no distance sorting. On Tuesday 28 December 2010 15:55:43 Bharat Jain wrote: > hi, > we are currently using SOLR 1.3 and planning to use location based search > for some of functionality. Is there any support for such

geospatial search support for SOLR 1.3 and 1.4?

hi, we are currently using SOLR 1.3 and planning to use location based search for some of functionality. Is there any support for such a thing in 1.3? Do we need to upgrade to 1.4+ version. Thanks Bharat Jain

Re: Upgraing from SOLR 1.3 to 3

like this: > > > > > Also, the ISOLatin1AccentFilterFactory is deprecated, replaced with > ASCIIFoldingFilterFactory. It's still around, but could be removed at > any time. > > Shawn > > > On 11/18/2010 4:56 AM, Moritz Krinke wrote: &

Re: Upgraing from SOLR 1.3 to 3

y is deprecated, replaced with ASCIIFoldingFilterFactory. It's still around, but could be removed at any time. Shawn On 11/18/2010 4:56 AM, Moritz Krinke wrote: Hello, i have a running solr 1.3 installation and would like to migrate it to solr 3 in order to get speed improvements by

Upgraing from SOLR 1.3 to 3

Hello, i have a running solr 1.3 installation and would like to migrate it to solr 3 in order to get speed improvements by using the multiple threads for indexing. When starting SOLR 3, i get the following error message: SEVERE: org.apache.solr.common.SolrException: Unknown fieldtype 't

Re: solr 1.3 how to parse "rich" documents

Did you do a 'commit' after this? If there is no error in the log or the HTTP response, the document should get added. Solr 1.4.1 has much newer versions of this software. On Thu, Nov 11, 2010 at 6:46 AM, Nikola Garafolic wrote: > Hi, > > I use solr 1.3 with patch for par

solr 1.3 how to parse "rich" documents

Hi, I use solr 1.3 with patch for parsing rich documents, and when uploading for example pdf file, only thing I see in solr.log is following: INFO: [] webapp=/solr path=/update/rich params={id=250&stream.type=pdf&fieldnames=id,name&commit=true&stream.fieldname=body&name=i

Re: solr 1.3 suggester component

hi erick, I was able to implement this using link you posted. I am using SOLR 1.3 I wanted to add spellcheck component to it so did this explicit spellcheck but for some reason it does not return suggestion for misspelled words. For instance

Re: SOLR 1.4.1 to SOLR 1.3 issues (backward compatability issue)

Thank you Otis. It solved the problem. -- View this message in context: http://lucene.472066.n3.nabble.com/SOLR-1-4-1-to-SOLR-1-3-issues-backward-compatability-issue-tp1649789p1664057.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: SOLR 1.4.1 to SOLR 1.3 issues (backward compatability issue)

Thank you Otis. I will try these steps. Yes, it is not about indexing issue. Index and search functionality are working fine. Only admin page is not accessible. There is a process in our company to look for the roll back option while moving any changes to LIVE/Production. As part of that we found

Re: SOLR 1.4.1 to SOLR 1.3 issues (backward compatability issue)

> Subject: SOLR 1.4.1 to SOLR 1.3 issues (backward compatability issue) > > > When I tried to roll back from SOLR 1.4.1 to SOLR 1.3, I am unable to view > the admin page alone rest of the functionality are fine. > I removed the index folder before reverting back to SOLR

SOLR 1.4.1 to SOLR 1.3 issues (backward compatability issue)

When I tried to roll back from SOLR 1.4.1 to SOLR 1.3, I am unable to view the admin page alone rest of the functionality are fine. I removed the index folder before reverting back to SOLR 1.3. Does any one have answer for this? -- View this message in context: http://lucene.472066.n3

Re: Filter Performance in Solr 1.3

There was a major Lucene change in filter handling from Solr 1.3 to Solr 1.4. They are much much faster in 1.4. Really Lucene 2.4.1 to Lucene 2.9.2. The filter is now consulted much earlier in the search process, thus weeding out many more documents early. It sounds like in Solr 1.3, you should

RE: Filter Performance in Solr 1.3

results, or does it still seem like something strange might be happening? Thanks, Matt -Original Message- From: Geert-Jan Brits [mailto:gbr...@gmail.com] Sent: Wednesday, August 11, 2010 2:55 PM To: solr-user@lucene.apache.org Subject: Re: Filter Performance in Solr 1.3 fq's ar

Re: Filter Performance in Solr 1.3

Bargar, Matthew B > Hi there, I have a question about filter (fq) performance in Solr 1.3. > After doing some testing it seems as though adding a filter increases > search time. From what I've read here > http://www.derivante.com/2009/06/23/solr-filtering-performance-increase/ &

Filter Performance in Solr 1.3

Hi there, I have a question about filter (fq) performance in Solr 1.3. After doing some testing it seems as though adding a filter increases search time. From what I've read here http://www.derivante.com/2009/06/23/solr-filtering-performance-increase/ and here http://www.lucidimagination.com

Re: migrating from solr 1.3 to 1.4

On Fri, Feb 12, 2010 at 19:46, Sachin Sebastian 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 'tdo

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

Re: Deploying Solr 1.3 in JBoss 5

Done. L.M. On 5 February 2010 12:56, Sascha Szott wrote: > Hi Luca, > > could you add a note to the Wiki page [1]. Thanks! > > -Sascha > > [1] http://wiki.apache.org/solr/SolrJBoss > > Luca Molteni wrote: >> >> Bye the way, I finally solved it. >>

Re: Deploying Solr 1.3 in JBoss 5

Hi Luca, could you add a note to the Wiki page [1]. Thanks! -Sascha [1] http://wiki.apache.org/solr/SolrJBoss Luca Molteni wrote: Bye the way, I finally solved it. To deploy solr 1.3 in jboss 5, you simply have to remove xercesImpl-2.8.1.jar xml-apis-1.3.03.jar From the WEB-INF/lib

Re: Deploying Solr 1.3 in JBoss 5

Bye the way, I finally solved it. To deploy solr 1.3 in jboss 5, you simply have to remove xercesImpl-2.8.1.jar xml-apis-1.3.03.jar >From the WEB-INF/lib folder of solr.war Solr will use the lib provided by jboss 5. Thank you again. L.M. On 3 February 2010 10:38, Luca Molteni wr

Re: Deploying Solr 1.3 in JBoss 5

be cast to org.apache.xerces.xni.parser.XMLParserConfiguration It seems I'm not not the only one in the web, but I'm still working on it. Just to make some statistics, did someone manage to depoy solr 1.3 to jBoss 5? I should update the wiki page too, maybe. Thank you very much, Sascha. Bye L.M. On 2 Februar

Re: Deploying Solr 1.3 in JBoss 5

Luca Molteni wrote: Actually, if I hard-code the value, it gives me the same error... interesting. According to the error message: The content of element type "env-entry" must match "(description?,env-entry-name,env-entry-value?,env-entry-type)" Maybe it helps to change the order of elements w

Re: Deploying Solr 1.3 in JBoss 5

Hello, You're probably right. This is probably a problem related to Jboss 5, but since I used the procedure of solr deployment described there I thought that someone would have already dealt with this problem. Actually, if I hard-code the value, it gives me the same error... interesting. L.M.

Re: Deploying Solr 1.3 in JBoss 5

Hi, I'm not sure if that's a Solr issue. However, what happens if you set env-entry-value to C:/mypath/solr instead of ${solr.home.myhome}? -Sascha Am 02.02.2010 15:20, schrieb Luca Molteni: Hello list, I'm having some problem deploying solr to JBoss 5. The problem is with environment vari

Re: Deploying Solr 1.3 in JBoss 5

Because the current release of our software is based on solr 1.3, and we scheduled the migration to JBoss 5 before the migration to solr 1.4. It's a concurrency problem! L.M. On 2 February 2010 16:05, Erik Hatcher wrote: > Out of curiosity, why are you deploying Solr 1.3 rather t

Re: Deploying Solr 1.3 in JBoss 5

Out of curiosity, why are you deploying Solr 1.3 rather than Solr 1.4? Sorry, but I don't know about the JBoss issues first hand myself. Erik On Feb 2, 2010, at 9:20 AM, Luca Molteni wrote: Hello list, I'm having some problem deploying solr to JBoss 5. The probl

Deploying Solr 1.3 in JBoss 5

Hello list, I'm having some problem deploying solr to JBoss 5. The problem is with environment variables: Following this page of the wiki: http://wiki.apache.org/solr/SolrJBoss I've added to the web.xml of WEB-INF of solr solr/home java.lang.String ${solr.home.myhome} Since I'm

Re: Solr 1.3 query and index perf tank during optimize

Oops, you're right, term listings and counts for deleted docs are adjusted during merges. I had the impression that optimize had some special powers here that merge does not. Thank you for bringing expungeDeletes to my attention. On Sat, Nov 21, 2009 at 7:46 AM, Yonik Seeley wrote: > On Sat, Nov

Re: Solr 1.3 query and index perf tank during optimize

On Sat, Nov 21, 2009 at 12:33 AM, Lance Norskog wrote: > And, terms whose documents have been deleted are not purged. So, you > can merge all you like and the index will not shrink back completely. Under what conditions? Certainly not all, since I just tried a simple test and a merge removed the

Re: Solr 1.3 query and index perf tank during optimize

And, terms whose documents have been deleted are not purged. So, you can merge all you like and the index will not shrink back completely. Only an optimize will remove the "orphan" terms. This is important because the orphan terms affect relevance calculations. So you really want to purge them wit

Re: Solr 1.3 query and index perf tank during optimize

On Fri, Nov 20, 2009 at 2:32 PM, Michael wrote: > On Fri, Nov 20, 2009 at 12:35 PM, Yonik Seeley > wrote: >> On Fri, Nov 20, 2009 at 12:24 PM, Michael wrote: >>> So -- I thought I understood you to mean that if I frequently merge, >>> it's basically the same as an optimize, and cruft will get pu

Re: Solr 1.3 query and index perf tank during optimize

On Fri, Nov 20, 2009 at 12:35 PM, Yonik Seeley wrote: > On Fri, Nov 20, 2009 at 12:24 PM, Michael wrote: >> So -- I thought I understood you to mean that if I frequently merge, >> it's basically the same as an optimize, and cruft will get purged.  Am >> I misunderstanding you? > > That only appli

Re: Solr 1.3 query and index perf tank during optimize

On Fri, Nov 20, 2009 at 12:24 PM, Michael wrote: > So -- I thought I understood you to mean that if I frequently merge, > it's basically the same as an optimize, and cruft will get purged.  Am > I misunderstanding you? That only applies to the segments involved in the merge. The deleted document

Re: Solr 1.3 query and index perf tank during optimize

Hoss, Using Solr 1.4, I see constant index growth until an optimize. I commit (hundreds of updates) every 5 minutes and have a mergefactor of 10, but every 50 minutes I don't see the index collapse down to its original size -- it's slightly larger. Over the course of a week, the index grew from

Re: Solr 1.3 query and index perf tank during optimize

On Tue, Nov 17, 2009 at 2:24 PM, Chris Hostetter wrote: > > : Basically, search entries are keyed to other documents. We have finite > : storage, > : so we purge old documents. My understanding was that deleted documents > : still > : take space until an optimize is done. Therefore, if I don't

Re: Solr 1.3 query and index perf tank during optimize

: Basically, search entries are keyed to other documents. We have finite : storage, : so we purge old documents. My understanding was that deleted documents : still : take space until an optimize is done. Therefore, if I don't optimize, the : index : size on disk will grow without bound. : : A

Re: Solr 1.3 query and index perf tank during optimize

R, IR - Original Message > From: Jerome L Quinn > To: solr-user@lucene.apache.org > Sent: Mon, November 16, 2009 10:05:55 AM > Subject: Re: Solr 1.3 query and index perf tank during optimize > > > > Otis Gospodnetic wrote on 11/13/2009 11:15:43 > PM: >

Re: Solr 1.3 query and index perf tank during optimize

Otis Gospodnetic wrote on 11/13/2009 11:15:43 PM: > Let's take a step back. Why do you need to optimize? You said: "As > long as I'm not optimizing, search and indexing times are satisfactory." :) > > You don't need to optimize just because you are continuously adding > and deleting documents

Re: Solr 1.3 query and index perf tank during optimize

Good question! The terms in the deleted documents are left behind, and so the relevance behavior will be off. The other space used directly by documents will be reabsorbed. (??) On Sat, Nov 14, 2009 at 1:28 PM, Jerome L Quinn wrote: > > > Lance Norskog wrote on 11/13/2009 11:18:42 PM: > >> The

Re: Solr 1.3 query and index perf tank during optimize

Lance Norskog wrote on 11/13/2009 11:18:42 PM: > The 'maxSegments' feature is new with 1.4. I'm not sure that it will > cause any less disk I/O during optimize. It could still be useful to manage the "too many open files" problem that rears its ugly head on occasion. > The 'mergeFactor=2' id

Re: Solr 1.3 query and index perf tank during optimize

The 'maxSegments' feature is new with 1.4. I'm not sure that it will cause any less disk I/O during optimize. The 'mergeFactor=2' idea is not what you think: in this case the index is always "mostly optimized", so you never need to run optimize. Indexing is always slower, because you amortize the

Re: Solr 1.3 query and index perf tank during optimize

ematext is hiring -- http://sematext.com/about/jobs.html?mls Lucene, Solr, Nutch, Katta, Hadoop, HBase, UIMA, NLP, NER, IR - Original Message > From: Jerome L Quinn > To: solr-user@lucene.apache.org > Sent: Thu, November 12, 2009 6:30:42 PM > Subject: Solr 1.3 query and index

Re: Solr 1.3 query and index perf tank during optimize

ysee...@gmail.com wrote on 11/13/2009 09:06:29 AM: > On Fri, Nov 13, 2009 at 6:27 AM, Michael McCandless > wrote: > > I think we sorely need a Directory impl that down-prioritizes IO > > performed by merging. > > It's unclear if this case is caused by IO contention, or the OS cache > of the hot p

Re: Solr 1.3 query and index perf tank during optimize

ysee...@gmail.com wrote on 11/13/2009 09:06:29 AM: > > On Fri, Nov 13, 2009 at 6:27 AM, Michael McCandless > wrote: > > I think we sorely need a Directory impl that down-prioritizes IO > > performed by merging. > > It's unclear if this case is caused by IO contention, or the OS cache > of the hot

Re: Solr 1.3 query and index perf tank during optimize

Mark Miller wrote on 11/12/2009 07:18:03 PM: > Ah, the pains of optimization. Its kind of just how it is. One solution > is to use two boxes and replication - optimize on the master, and then > queries only hit the slave. Out of reach for some though, and adds many > complications. Yes, in my us

Re: Solr 1.3 query and index perf tank during optimize

On Fri, Nov 13, 2009 at 6:27 AM, Michael McCandless wrote: > I think we sorely need a Directory impl that down-prioritizes IO > performed by merging. It's unclear if this case is caused by IO contention, or the OS cache of the hot parts of the index being lost by that extra IO activity. Of course

Re: Solr 1.3 query and index perf tank during optimize

On Fri, Nov 13, 2009 at 6:27 AM, Michael McCandless wrote: > I think we sorely need a Directory impl that down-prioritizes IO > performed by merging. Presumably this "prioritizing Directory impl" could wrap/decorate any existing Directory. Mike

Re: Solr 1.3 query and index perf tank during optimize

roblem I've had for quite a while, > and have basically avoided optimizing because of it.  However, > eventually we will get to the point where we must delete as > well as add docs continuously. > > I have a Solr 1.3 index with ~4M docs at around 90G.  This is a single > insta

Re: Solr 1.3 query and index perf tank during optimize

Mark Miller wrote: > Jerome L Quinn wrote: >> Hi, everyone, this is a problem I've had for quite a while, >> and have basically avoided optimizing because of it.  However, >> eventually we will get to the point where we must delete as >> well as add docs continuou

Re: Solr 1.3 query and index perf tank during optimize

Jerome L Quinn wrote: > Hi, everyone, this is a problem I've had for quite a while, > and have basically avoided optimizing because of it. However, > eventually we will get to the point where we must delete as > well as add docs continuously. > > I have a Solr 1.3 index

Solr 1.3 query and index perf tank during optimize

Hi, everyone, this is a problem I've had for quite a while, and have basically avoided optimizing because of it. However, eventually we will get to the point where we must delete as well as add docs continuously. I have a Solr 1.3 index with ~4M docs at around 90G. This is a single ins

Re: How to configure Solr 1.3 on Websphere 6.1

: I have been trying to deploy Solr on websphere but no luck yet. : I was trying to deploy the war file under "dist" folder, but I kept getting : errors. (recent one is that it couldn't find the configuration file). When I Did you start by going through the tutorial using the instance of jetty in

How to configure Solr 1.3 on Websphere 6.1

Hi all, Solr 1.3 Websphere 6.1 I have been looking for some documentation on how to configure Solr on Websphere but no luck yet. Can some one suggest me some document which can give me the overview on how to get started with Solr on Websphere and how to integrate it with websites (Java/JSP). I

Re: Solr 1.3 deletes not working?

On Fri, Sep 18, 2009 at 6:26 AM, Lee Theobald wrote: > I also seem to be having a similar problem deleting.  As far as I can tell, > the system thinks we are deleting the records (it logs that it's executing > the commands and all looks OK) but the records always remain.  Regardsless > if we try a

Re: Solr 1.3 deletes not working?

s also not extra characters in our deletion queries. Can anyone think of anything else that I should be checking? I'm sure it's probably a small bit of config we've missed but I can't track it down. Regards, Lee -- View this message in context: http://www.nabble.co

Re: OutOfMemory error on solr 1.3

solr-1.3.0/example/solr > > Francis > > -Original Message- > From: Constantijn Visinescu [mailto:baeli...@gmail.com] > Sent: Wednesday, September 09, 2009 11:35 PM > To: solr-user@lucene.apache.org > Subject: Re: OutOfMemory error on solr 1.3 > > Just wondering, how much

RE: OutOfMemory error on solr 1.3

Subject: Re: OutOfMemory error on solr 1.3 Just wondering, how much memory are you giving your JVM ? On Thu, Sep 10, 2009 at 7:46 AM, Francis Yakin wrote: > > I am having OutOfMemory error on our slaves server, I would like to know if > someone has the same issue and have the solution

Re: solr 1.3 and multicore data directory

xml in each folder: > >  ${solr.data.dir:./solr/exhibits/data} > > I can't wait for solr 1.4! > > Noble Paul നോബിള്‍ नोब्ळ् wrote: >> >> the dataDir is a Solr1.4 feature >> >> On Thu, Sep 10, 2009 at 1:57 AM, Paul Rosen >> wrote: >>> &

Re: solr 1.3 and multicore data directory

2009 at 1:57 AM, Paul Rosen wrote: Hi All, I'm trying to set up solr 1.3 to use multicore but I'm getting some puzzling results. My solr.xml file is: When I start up solr, everything looks normal until I get this line in the log: INFO: [resources] Opening new SolrCo

RE: OutOfMemory error on solr 1.3

--Original Message- From: Constantijn Visinescu [mailto:baeli...@gmail.com] Sent: Wednesday, September 09, 2009 11:35 PM To: solr-user@lucene.apache.org Subject: Re: OutOfMemory error on solr 1.3 Just wondering, how much memory are you giving your JVM ? On Thu, Sep 10, 2009 at 7:46 AM, Fra

Re: OutOfMemory error on solr 1.3

ze: 5320, > Num elements: 2649 > java.lang.OutOfMemoryError: allocLargeObjectOrArray - Object size: 16400, > Num elements: 8192 > java.lang.OutOfMemoryError: allocLargeObjectOrArray - Object size: 4136, > Num elements: 2058 > SEVERE: java.lang.OutOfMemoryError: allocLargeObjectOrArray - Object size: > 8208, Num elements: 2048 > SEVERE: java.lang.OutOfMemoryError: allocLargeObjectOrArray - Object size: > 4112, Num elements: 2048 > SEVERE: Error during auto-warming of > key:org.apache.solr.search.queryresult...@3b8f69ee:java.lang.OutOfMemoryError: > allocLargeObjectOrArray - Object > > We just upgraded to Solr 1.3 last two months ago, before that we were > running 1.2 and it had the same issue, but it stopped for awhile until today > it appears again. > > I attached our solrconfig.xml to see if someone can pin-point the issue. > > Thanks > > Francis > > >

Re: solr 1.3 and multicore data directory

the dataDir is a Solr1.4 feature On Thu, Sep 10, 2009 at 1:57 AM, Paul Rosen wrote: > Hi All, > > I'm trying to set up solr 1.3 to use multicore but I'm getting some puzzling > results. My solr.xml file is: > > > >   >   dataDir="solr/re

solr 1.3 and multicore data directory

Hi All, I'm trying to set up solr 1.3 to use multicore but I'm getting some puzzling results. My solr.xml file is: dataDir="solr/resources/data/" /> dataDir="solr/exhibits/data/" /> dataDir="solr/reindex_resources/data/" /> When

Re: abortOnConfigurationError=false not taking effect in solr 1.3

al/app/data/search/core09/index >> > > That error suggests that you don't have a configuration error. The data > directory you have given either does not exist or is read-only. It is a > runtime error. > > -- > Regards, > Shalin Shekhar Mangar. > > -- Vie

Re: abortOnConfigurationError=false not taking effect in solr 1.3

On Mon, Sep 7, 2009 at 8:58 PM, djain101 wrote: > > > Please suggest what is the right way to configure so that if one core fails > due to configuration errors, all other cores remain unaffected? > > * > Check your log files for more

Re: abortOnConfigurationError=false not taking effect in solr 1.3

t;>> >>>>>> ***** >>>>>> Check your log files for more detailed information on what may be >>>>>> wrong. >>>>>> >>>>>> If you want solr to continue after configuration errors, change: >>>>>> >>>>>> >>>>>> <abortOnConfigurationError>false</abortOnConfigurationError> >>>>>> >>>>>> in solr.xml >>>>>> >>>>>> java.lang.RuntimeException: java.io.IOException: Cannot create >>>>>> directory: >>>>>> /usr/local/app/data/search/core09/index >>>>>> *** >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> >>>> >>> >>> >> >> >> -- >> - Mark >> >> http://www.lucidimagination.com >> >> >> >> >> > > -- View this message in context: http://www.nabble.com/abortOnConfigurationError%3Dfalse-not-taking-effect-in-solr-1.3-tp25332254p25358007.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: abortOnConfigurationError=false not taking effect in solr 1.3

>>>>> Check your log files for more detailed information on what may be >>>>> wrong. >>>>> >>>>> If you want solr to continue after configuration errors, change: >>>>> >>>>> >>>>> <abortOnConfigurationError>false</abortOnConfigurationError> >>>>> >>>>> in solr.xml >>>>> >>>>> java.lang.RuntimeException: java.io.IOException: Cannot create >>>>> directory: >>>>> /usr/local/app/data/search/core09/index >>>>> *** >>>>> >>>>> >>>>> >>>> >>>> >>> >>> >>> >>> >>> >> >> > > > -- > - Mark > > http://www.lucidimagination.com > > > > > -- View this message in context: http://www.nabble.com/abortOnConfigurationError%3Dfalse-not-taking-effect-in-solr-1.3-tp25332254p25355662.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: abortOnConfigurationError=false not taking effect in solr 1.3

false djain101 wrote: > Thanks !!! Can you please give an example to put it in solr.xml? How is the > xml structure look like for enabling this property? > > > markrmiller wrote: > >> Yes - try adding it to solr.xml - thats where the CoreContainer looks >> for it. >>

Re: abortOnConfigurationError=false not taking effect in solr 1.3

or> >>> >>> in solr.xml >>> >>> java.lang.RuntimeException: java.io.IOException: Cannot create >>> directory: >>> /usr/local/app/data/search/core09/index >>> *** >>> >>> >> >> > > > > > > -- View this message in context: http://www.nabble.com/abortOnConfigurationError%3Dfalse-not-taking-effect-in-solr-1.3-tp25332254p25355527.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: abortOnConfigurationError=false not taking effect in solr 1.3

Yes - try adding it to solr.xml - thats where the CoreContainer looks for it. -- - Mark http://www.lucidimagination.com djain101 wrote: > Any help is much appreciated. > > Thanks, > Dharmveer > > > djain101 wrote: > >> Hi, >> >> We have set false >> in solrconfig.xml for all the cores but

Re: abortOnConfigurationError=false not taking effect in solr 1.3

java.lang.RuntimeException: java.io.IOException: Cannot create directory: > /usr/local/app/data/search/core09/index > *** > -- View this message in context: http://www.nabble.com/abortOnConfigurationError%3Dfalse-not-taking-effect-in-solr-1.3-tp25332254p25354786.html Sent from the Solr - User mailing list archive at Nabble.com.

abortOnConfigurationError=false not taking the effect in solr 1.3

ntext: http://www.nabble.com/abortOnConfigurationError%3Dfalse-not-taking-the-effect-in-solr-1.3-tp25332254p25332254.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: tag cloud with solr 1.3

Or you can just use facet counts. Bill On Thu, Aug 27, 2009 at 5:23 PM, AHMET ARSLAN wrote: > > > Hi all,How would I go about > > implementing a 'tag cloud' with Solr1.3? All I > > want to do is to display a list of most occurring terms in > > the corpus. Is there an easy way to go about that i

Re: tag cloud with solr 1.3

> Hi all,How would I go about > implementing a 'tag cloud' with Solr1.3? All I > want to do is to display a list of most occurring terms in > the corpus. Is there an easy way to go about that in 1.3? Yes http://localhost:8983/solr/admin/luke?fl=text&numTerms=100 will give you top 100 most occur

tag cloud with solr 1.3

Hi all,How would I go about implementing a 'tag cloud' with Solr1.3? All I want to do is to display a list of most occurring terms in the corpus. Is there an easy way to go about that in 1.3? I saw a couple of postings about implementing it with TermVectorComponent but thats in 1.4. I'd really appr

Re: Solr 1.3 JNDI Datasource

ce for our data import handler to work with our Weblogic configured > JNDI datasource.   Can anyone lead me in the right direction how to > configure this in my dataconfig.xml? We are using Solr 1.3. > > Thanks, > Brian > -- > View this message in context: > http://

Solr 1.3 JNDI Datasource

configure this in my dataconfig.xml? We are using Solr 1.3. Thanks, Brian -- View this message in context: http://www.nabble.com/Solr-1.3-JNDI-Datasource-tp25025740p25025740.html Sent from the Solr - User mailing list archive at Nabble.com.

RE: Solr 1.3 and JDK1.6

We have been using solr 1.3 with jdk1.6 for quite sometime in production, no issues yet Thanks, Kalyan Manepalli -Original Message- From: vaibhav joshi [mailto:callvaib...@hotmail.com] Sent: Wednesday, August 12, 2009 1:21 PM To: solr-user@lucene.apache.org Subject: Solr 1.3 and JDK1.6

RE: Solr 1.3 and JDK1.6

Oracle JRockit (Mission Control 1.3) latest-greatest (Java 6), -server, AMD64, SLES 10 Solr 1.3/1.4 Tomcat 6.0.20, APR No any problem. But you need licensing for production. JRockit seems to be at least 20 times faster than SUN's JVM. P.S. I only had constant problems with latest A

Re: Solr 1.3 and JDK1.6

Hi, I'm running solr 1.3 with java -version java version "1.6..." . No problem to report. Cheers. J 2009/8/12 vaibhav joshi : > > Hi > > I am using Solr 1.3 ( official released version) and JDk1.5. My company is > moving towards upgrading all systems to JD

Solr 1.3 and JDK1.6

Hi I am using Solr 1.3 ( official released version) and JDk1.5. My company is moving towards upgrading all systems to JDK1.6. is it safe to upgrade to JDK1.6 with Solr 1.3 wars? Are there any compatible issues with JDK1.6? Thanks Vaibhav

  1   2   3   4   5   >