uing
> the point...
>
> -N
>
>
> -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:
>>
>> Mayb
-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
Minutello, Nick wrote:
>
> Maybe spend some time playing with Compass rather than speculating ;)
>
I spent few weeks by studying Compass source code, it was three years ago,
and Compass docs (3 years ago) were saying the same as now:
"Compass::Core provides support for two phase commits transa
Correct. Its not 2PC. It just makes the window for inconistancy quite
small ... without the user having to write anything.
-N
-Original Message-
From: Lukas Kahwe Smith [mailto:m...@pooteeweet.org]
Sent: 25 January 2010 21:19
To: solr-user@lucene.apache.org
Subject: Re: Solr vs
From: Fuad Efendi [mailto:f...@efendi.ca]
Sent: 25 January 2010 16:46
To: solr-user@lucene.apache.org
Subject: RE: Solr vs. Compass
> >> Even if "commit" takes 20 minutes?
> I've never seen a commit take 20 minutes... (anything taking that long
> is broken, perhaps i
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 application.
Sure. I guess L
]
Sent: 25 January 2010 16:06
To: solr-user@lucene.apache.org
Subject: RE: Solr vs. Compass
> >> Why to embed "indexing" as a transaction dependency? Extremely
> >> weird
> idea.
> There is nothing weird about different use cases requiring different
> approa
> >> Even if "commit" takes 20 minutes?
> I've never seen a commit take 20 minutes... (anything taking that long
> is broken, perhaps in concept)
"index merge" can take from few minutes to few hours. That's why nothing can
beat SOLR Master/Slave and sharding for huge datasets. And reopening of
I
> >> 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
s mentioned before, they address different kinds of problems
-Nick
-----Original Message-
From: Fuad Efendi [mailto:f...@efendi.ca]
Sent: 23 January 2010 05:01
To: solr-user@lucene.apache.org
Subject: RE: Solr vs. Compass
Of course, I understand what "transaction" means;
http://www.linkedin.com/in/liferay
Tokenizer Inc.
http://www.tokenizer.ca/
Data Mining, Vertical Search
-Original Message-
From: Fuad Efendi [mailto:f...@efendi.ca]
Sent: January-22-10 11:23 PM
To: solr-user@lucene.apache.org
Subject: RE: Solr vs. Compass
Yes, "transactional&qu
hanks,
Fuad Efendi
+1 416-993-2060
http://www.linkedin.com/in/liferay
Tokenizer Inc.
http://www.tokenizer.ca/
Data Mining, Vertical Search
> -Original Message-
> From: Fuad Efendi [mailto:f...@efendi.ca]
> Sent: January-22-10 11:23 PM
> To: solr-user@lucene.apache.org
> Sub
uot;.
I wrote this 2 years ago:
http://www.theserverside.com/news/thread.tss?thread_id=50711#272351
Fuad Efendi
+1 416-993-2060
http://www.tokenizer.ca/
> -Original Message-----
> From: Uri Boness [mailto:ubon...@gmail.com]
> Sent: January-21-10 11:35 AM
> To: solr-user@lucene.ap
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
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'
Hi Ken,
Based on this, Solr sounds like the way to go.
Otis
--
Sematext -- http://sematext.com/ -- Solr - Lucene - Nutch
- Original Message
> From: Ken Lane (kenlane)
> To: solr-user@lucene.apache.org
> Sent: Thu, January 21, 2010 12:07:56 PM
> Subject: RE: Solr
There seems to be an implication that compass wont scale as well as solr - and
I'm not sure that's true at all. They will both scale as well as the underlying
Lucene.
Lucene doesn't handle distributed search or replication out of the box,
you have to implement it using some of it's features (d
t [mailto:radam...@techtarget.com]
Sent: 21 January 2010 18:16
To: solr-user@lucene.apache.org
Subject: RE: Solr vs. Compass
> 2) Compass does a number of things really nicely (that afaik, isn't
> addressed by Solr)
> + Object-search engine mapping (great for structured data - i.e. not
> 2) Compass does a number of things really nicely (that afaik, isn't addressed
> by Solr)
> + Object-search engine mapping (great for structured data - i.e. not just
> text documents). I find writing the code that converts to/from a SolrDocument
> a bit annoying (but in my current project, the
llo, Nick
Sent: 21 January 2010 17:52
To: solr-user@lucene.apache.org
Subject: RE: Solr vs. Compass
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 obvio
ill both scale as well as the
underlying Lucene.
-Original Message-
From: Ken Lane (kenlane) [mailto:kenl...@cisco.com]
Sent: 21 January 2010 17:08
To: solr-user@lucene.apache.org
Subject: RE: Solr vs. Compass
Uri, Lucas,
Thanks for your feedback. To clarify on some specifics,
1.
;t be transactional, we will update the indexes periodically
throughout the day probably via dataimport handler.
Regards, Ken
-Original Message-
From: Uri Boness [mailto:ubon...@gmail.com]
Sent: Thursday, January 21, 2010 11:35 AM
To: solr-user@lucene.apache.org
Subject: Re: Solr vs. Compas
SOLR is, first and foremost, a text searching tool that scales. Are
you searching lots of text here or not? There are situations
in which you need both in order to accomplish your business
needs, so asking "which one is best" is tricky to answer
FWIW
Erick
On Thu, Jan 21, 2010 at 10:40 AM, Ke
In addition, the biggest appealing feature in Compass is that it's
transactional and therefore integrates well with your infrastructure
(Spring/EJB, Hibernate, JPA, etc...). This obviously is nice for some
systems (not very large scale ones) and the programming model is clean.
On the other hand
Hi,
I think that these products do not compete directly that much, each fit
different business case. Can you tell us more about our specific situation?
What do you need to search and where your data is? (DB, Filesystem, Web
...?)
Solr provides some specific extensions which are not supported dire
25 matches
Mail list logo
