just a suggestion ... If the shards are know, you can add them as the default params in the requesthandler so they are added always. and the URL would just have the qt parameter.
As the limit for uri is browser dependent. How are you querying solr ...... any client api ?? through browser ?? is it hitting the max header length ?? Can you use post instead ?? Regards, Jayendra On Thu, Jun 2, 2011 at 7:12 PM, JohnRodey <timothydd...@yahoo.com> wrote: > I have a master solr instance that I sent my request to, it hosts no > documents it just farms the request out to a large number of shards. All the > other solr instances that host the data contain multiple cores. > > Therefore my search string looks like > "http://host:port/solr/select?...&shards=nodeA:1234/solr/core01,nodeA:1234/solr/core02,nodeA:1234/solr/core03,..."; > This shard list is pretty long and has finally hit "the limit". > > So my question is how to best avoid having to build such a long uri? > > Is there a way to have mutiple tiers, where the master server has a list of > servers (nodeA:1234,nodeB:1234,...) and each of those nodes query the cores > that they host (nodeA hosts core01, core02, core03, ...)? > > Thanks! > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Hitting-the-URI-limit-how-to-get-around-this-tp3017837p3017837.html > Sent from the Solr - User mailing list archive at Nabble.com. >
