Thanks Jack i am using *q.alt* just for testing purpose only we uses *q=query* in our general production environment case and *mcat.intent* is our request handler to add extra number of rows and all.
Here i was doing some mistake to properly explaining the situation, so i am sorry for that. *Requirement:* I want to test my sharded environment that a unique document should present in single shard not in both. *core name*: mcats *core.properties*: name=mcats, so default collection name would be mcats as well. And i was taking my non sharded index(mcats index) and copying it to node1 as well as node 2 and starting the first node as: *java -DzkRun -DnumShards=2 -Dbootstrap_confdir=./solr/mcats/conf -Dcollection.configName=myconf -jar start.jar* And second node as *java -Djetty.port=1983 -DzkHost=localhost:9983 -jar start.jar* So i guess it is taking the whole index as it is because when i run the query. http://localhost:8983/solr/mcats/select?q.alt=*:*<http://localhost:8983/solr/mcats/select?q.alt=id:174060&shards=localhost:8983/solr/mcats> it was giving me the sum of documents in both the shards which is 2*no of docs in mcats index. So the same document is present in both the shard at node1:8983 and node2:1983 To figure this out i indexed it with the another different doc now when i queried with http://localhost:8983/solr/mcats/select?q.alt=id:17406780&distrib=false<http://localhost:8983/solr/mcats/select?q.alt=id:174060&shards=localhost:8983/solr/mcats> the document is present. But in another query http://localhost:8983/solr/mcats/select?q.alt=id:17406780&distrib=flase<http://localhost:8983/solr/mcats/select?q.alt=id:174060&shards=localhost:8983/solr/mcats> it is not found. which fulfilled my test case. So i thought i have to do the full indexing of my core mcats to validate my test case for each ids. Please correct me if i am wrong. With Regards Aman Tandon On Wed, May 14, 2014 at 5:52 PM, Jack Krupansky <j...@basetechnology.com>wrote: > The q.alt param specifies only the parameter to use if the q parameter is > missing. Could you verify whether that is really the case? Typically > solrconfig gives a default of "*:*" for the q parameter. Specifying a query > via the q.alt parameter seems like a strange approach - what is your > rationale? > > What is this odd "mcat.intent" query response writer type that you are > specifying with the qt parameter? > > -- Jack Krupansky > > -----Original Message----- From: Aman Tandon > Sent: Wednesday, May 14, 2014 1:35 AM > To: solr-user@lucene.apache.org > Subject: distrib=false is not honoring > > > I am trying to use the solr cloud for solr 4.2.0 and solr 4.7.1. > Here mcats is our collection name. > > *With solr 4.2* > > shard1: localhost:8019 > shard1: localhost:6019 > > *With solr 4.7.1* > > shard1: localhost:8983 > shard1: localhost:1983 > > With both the server i make the copy of example directory as mentioned in > wiki, and queried over the both nodes > > *query 1*: > http://localhost:8983/solr/mcats/select?q.alt=id:69763&; > distrib=false&qt=mcat.intent > *query 2*: > > http://localhost:1983/solr/mcats/select?q.alt=id:69763&; > distrib=false&qt=mcat.intent > > total number of docs count become half but i search for specific id then > the result is same, if distrib=false this enables to search on particular > node then one of these node should not return the return the result. If i > am incorrect please help me out to test that one record is present in one > shard only. > > With Regards > Aman Tandon >
