Hi,
You have many basic questions about search. Can I recommend one of the books?
http://lucene.apache.org/solr/books.html
Also, you'll find a lot of answers on the Solr WIKI:
http://wiki.apache.org/solr/ if you're not aware of it.
I think Solr may solve your performance problems well.
Whether
Thanks for your replies, you're good expert :)
I've read documentation on Solr basicaly, I'm familiar with it around 2
days.
The documentation is very huge at first sight :). Me and my company is
being deciding to use Solr or other solution.
Maybe you're right about re-implementing our sorting
1. Just trust that Lucene will perform :)
Incremental updates are actually stored in separate new index segments with
own caches, so all the old existing data is left un-touched with caches in
place.
2. Please explain what you expect from semantic search which is an overloaded
word.
3. On
Hi everyone :)
Our company is very interesting in Solr engine for searching people.
I have 3 questions below about extended capabilities of Solr, but first I'd
like to present you the problem
Let's say we have ~100 mln users with many characteristics - some of them
described below.
We want to
Hi everyone :)
Hi :)
So, these are my 3 questions:
1. Does Solr provide searching among different count fields with different
types like in WHERE condition?
Yes. As long as these are not full-text you should use filter queries for
these, e.g.
q=*:*
fq=country:USA
fq=language:SPA
fq=age:[30
I'm wondering if Solr is the best tool for this kind of usage. Solr is a
text search engine, so even if it supports all those features, it is
design for text search, which doesn't seem to be what you need. Which are
the reasons for moving from a DB implementation to Solr?
Don't misunderstand me,
2012/4/16 Tomás Fernández Löbbe tomasflo...@gmail.com:
I'm wondering if Solr is the best tool for this kind of usage. Solr is a
text search engine
Well, Lucene is a full-text search library, but Solr has always been far more.
Dating back to it's first use in CNET, it was used as a browse engine
Thanks for your reply :)
I have some new questions now:
1. How stable is trunk version? Has anyone used it on any kind of highload
project in production?
2. Does version 3.6 support near real time index update?
3. What is scheme of Solr index storing? Is it all in memory for each shard
or in disk
