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.
*Requ
> 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
>
Hi,
There is one more problem today, i indexed the mcat core and again copied
the same and then starting the shard
(as decribed in above thread)
*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: *
I noticed that there i
I also tried it to query specific shard to make sure that the unique record
is present in different shards but still no success.
http://localhost:8983/solr/mcats/select?q.alt=id:174060&shards=localhost:8983/solr/mcats
http://localhost:8983/solr/mcats/select?q.alt=id:174060&shards=localhost:1983/so
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
rationa
