The request proxying does not work with tomcat without calling an explicit flush in the code - jetty (which the unit tests are written against) worked without this flush. The flush is added to 4.3.
- Mark On Apr 23, 2013, at 2:02 PM, Furkan KAMACI <furkankam...@gmail.com> wrote: > Oopps, Mark you said: "If you use tomcat, this won't work in 4.2 or 4.2.1" > > Can you explain more what won't be at Tomcat and what will change at 4.3? > > 2013/4/23 Mark Miller <markrmil...@gmail.com> > >> If you use jetty - which you should :) It's what we test with. Tomcat only >> gets user testing. >> >> If you use tomcat, this won't work in 4.2 or 4.2.1, but probably will in >> 4.3 (we are voting on 4.3 now). >> >> No clue on other containers. >> >> - Mark >> >> On Apr 23, 2013, at 10:59 AM, Michael Della Bitta < >> michael.della.bi...@appinions.com> wrote: >> >>> I believe as of 4.2 you can talk to any host in the cloud. >>> >>> Michael Della Bitta >>> >>> ------------------------------------------------ >>> Appinions >>> 18 East 41st Street, 2nd Floor >>> New York, NY 10017-6271 >>> >>> www.appinions.com >>> >>> Where Influence Isn’t a Game >>> >>> >>> On Tue, Apr 23, 2013 at 10:45 AM, Arkadi Colson <ark...@smartbit.be> >> wrote: >>>> Hi >>>> >>>> Is it correct that when inserting or updating document into solr you >> have to >>>> talk to a solr host where at least one shard of that collection is >> stored? >>>> For select you can talk to any host within the collection.configName? >>>> >>>> BR, >>>> Arkadi >> >>
