doing?
Thanks,
Swarag
--
View this message in context:
http://www.nabble.com/Lower-Case-Filter-Factory-tp18930459p18930459.html
Sent from the Solr - User mailing list archive at Nabble.com.
I'm currently looking through the source, but just wanted to verify how
shards work. If a request is made to:
http://localhost:8983/solr/select?shards=localhost:8983/solr,localhost:7574/solr
Does the 8983 instance of Solr make an http request to both 7574 AND 8983 to
search? Or does it know
swarag wrote:
Yonik Seeley wrote:
On Tue, Jul 15, 2008 at 2:27 PM, swarag [EMAIL PROTECTED]
wrote:
To my understanding, this means I am using synonyms at index time and
NOT
query time. And yet, I am still having these problems with synonyms.
Can you give a specific example? Use
matt connolly wrote:
swarag wrote:
Knowing the Lucene struggles with multi-word query-time synonyms, my
question is, does this also affect index-time synonyms? What other
alternatives do we have if we require there to be multiple word synonyms?
No the multiple word problem doesn't
matt connolly wrote:
You won't have the multiple word problem if you use synonyms at index time
instead of query time.
swarag wrote:
Here is a basic example of some synonyms in my synonyms.txt:
club=club,bar,night cabaret
bar=bar,club
As you can see, a search for 'bar
Yonik Seeley wrote:
On Tue, Jul 15, 2008 at 2:27 PM, swarag [EMAIL PROTECTED]
wrote:
To my understanding, this means I am using synonyms at index time and NOT
query time. And yet, I am still having these problems with synonyms.
Can you give a specific example? Use debugQuery=true
hossman wrote:
This is Issue #1 regarding trying to use query time multi word synonyms
discussed on the wiki...
The Lucene QueryParser tokenizes on white space before giving any
text to the Analyzer, so if a person searches for the words sea biscit
the analyzer will be given the
hey,
I have a distributed search environment with one server hitting 3 shards.
for Example:
http://server1.cs.tmcs:15100/solr/search/?q=starbucksshards=server1.cs.tmcs:8983/solr,server2.cs.tmcs:8983/solr,server3.cs.tmcs:8983/solrcollapse.field=locChainId
So, where is the cache stored? Is is
- Original Message
From: swarag [EMAIL PROTECTED]
To: solr-user@lucene.apache.org
Sent: Monday, April 7, 2008 2:31:55 PM
Subject: Number of docs per segments
I have about 15 millions documents totalling 27GB I would like to know
how many segments I would need split them
Hi,
I am trying to search through a distributed index and when I enter this
link:
http://wil1devsch1.cs.tmcs:8983/select?shards=wil1devsch1.cs.tmcs:8983,wil1devsch1.cs.tmcs:8080q=pizza
But it always gives me results from the index stored on 8983 and not on
8080.
Is there anything wrong in what
I have about 15 millions documents totalling 27GB I would like to know
how many segments I would need split them into. I am trying to achieve a qps
of 100?
--
View this message in context:
http://www.nabble.com/Number-of-docs-per-segments-tp16538528p16538528.html
Sent from the Solr - User
So does it mean that Solr doesnt support QueryElevation (boost values)
wouldnt work on a distributed search?
Koji Sekiguchi-2 wrote:
Thank you, Yonik!
Koji
- doesn't currently support date faceting
- currently only supports sorted field facets
--
View this message in context:
I want to know if we can use index replication when we have segmented indexes
over multiple solr instances?
--
View this message in context:
http://www.nabble.com/Master-Slave-Replication-tp16293553p16293553.html
Sent from the Solr - User mailing list archive at Nabble.com.
In Lucene there is a Ram Based Index
org.apache.lucene.store.RAMDirectory.
Is there a way to setup my index in solr to use a RAMDirectory?
--
View this message in context:
http://www.nabble.com/RAM-Based-Index-for-Solr-tp16166036p16166036.html
Sent from the Solr - User mailing list archive at
14 matches
Mail list logo
