-Original Message-
From: Funtick [mailto:f...@efendi.ca]
Sent: 26 January 2010 02:44
To: solr-user@lucene.apache.org
Subject: RE: Solr vs. Compass
Minutello, Nick wrote:
>
> Maybe spend some time playing with Compass rather than speculating ;)
>
I spent few weeks by studyin
. Compass
On 25.01.2010, at 22:16, Minutello, Nick wrote:
> Sorry, you have completely lost me :/
>
> In simple terms, there are times when you want the primary storage
> (database) and the Lucene index to be in synch - and updated
atomically.
> It all depends on the kind of applica
Maybe spend some time playing with Compass rather than speculating ;)
If it helps, on the project where I last used compass, we had what I
consider to be a small dataset - just a few million documents. Nothing
related to indexing/searching took more than a second or 2 - mostly it
was 10's or 100's
Sorry, you have completely lost me :/
In simple terms, there are times when you want the primary storage
(database) and the Lucene index to be in synch - and updated atomically.
It all depends on the kind of application.
-N
-Original Message-
From: Fuad Efendi [mailto:f...@efendi.ca]
>> Why to embed "indexing" as a transaction dependency? Extremely weird idea.
There is nothing weird about different use cases requiring different
approaches
If you're just thinking documents and text search ... then its less of an issue.
If you have an online application where the indexing
I would tend to agree.
-Original Message-
From: Otis Gospodnetic [mailto:otis_gospodne...@yahoo.com]
Sent: 22 January 2010 05:18
To: solr-user@lucene.apache.org
Subject: Re: Solr vs. Compass
Hi Ken,
Based on this, Solr sounds like the way to go.
Otis
--
Sematext -- http://sematext.c
Agree with everything you said.
-Original Message-
From: Uri Boness [mailto:ubon...@gmail.com]
Sent: 22 January 2010 01:25
To: solr-user@lucene.apache.org
Subject: Re: Solr vs. Compass
>
> There seems to be an implication that compass wont scale as well as
solr - and I'm not sure that
Actually, that's true. But IMO it's not that great :)
After fighting it for a bit, we gave up on it ... (maybe more of a
reflection of our capabilities rather than Solr's - but Id like to think
we are some-way competant)
-N
-Original Message-
From: Adamsky, Robert [mailto:radam...@techt
Oops!
>> Solr does a number of things that are really nice (that aren't really
>> addressed by Solr)
I obviously meant:
"Solr does a number of things that are really nice (that aren't really
addressed by Compass)"
-N
-Original Message-
From: Minute
Not sure how many here have used both ...
I've used raw Lucene in the past - and after that, Compass. More recently Solr.
Here are some of the things I have noticed:
1) Stating the obvious: Solr has a server capability that Compass/Lucene does
not. This means indexing/searching is available to
angar [mailto:shalinman...@gmail.com]
Sent: 19 January 2010 12:04
To: solr-user@lucene.apache.org
Subject: Re: Interesting OutOfMemoryError on a 170M index
On Thu, Jan 14, 2010 at 4:04 AM, Minutello, Nick <
nick.minute...@credit-suisse.com> wrote:
> Agreed, commit every second.
>
> Assumi
at a time is far from ideal - even with the buffering). I
may have to either implement some client-side buffering to make it more
efficient - or eliminate the http layer (go embedded).
Thanks.
-Nick
-Original Message-
From: Minutello, Nick
Sent: 13 January 2010 23:29
To: solr-user
it has
-Nick
-Original Message-
From: Ryan McKinley [mailto:ryan...@gmail.com]
Sent: 13 January 2010 23:16
To: solr-user@lucene.apache.org
Subject: Re: Interesting OutOfMemoryError on a 170M index
On Jan 13, 2010, at 5:34 PM, Minutello, Nick wrote:
> Agreed, commit every second.
Do you
, which is probably the out-of-memory.
On Wed, Jan 13, 2010 at 10:36 AM, Minutello, Nick
wrote:
>
> Hi,
>
> I have a bit of an interesting OutOfMemoryError that I'm trying to
> figure out.
>
> My client & Solr server are running in the same JVM (for deployment
>
Hi,
I have a bit of an interesting OutOfMemoryError that I'm trying to
figure out.
My client & Solr server are running in the same JVM (for deployment
simplicity). FWIW, I'm using Jetty to host Solr. I'm using the supplied
code for the http-based client interface. Solr 1.3.0.
My app is adding a
15 matches
Mail list logo
