On 4/27/06, Erik Hatcher <[EMAIL PROTECTED]> wrote: > I'm adding multiple documents per <add> POST and getting a response > that looks like this: > > <result status="0"></result><result status="0"></result><result > status="0"></result><result status="0"></result><result status="0"></ > result><result status="0"></result> > > This response is several separate XML documents, rather than a single > one as I was expecting - which makes parsing the response more > difficult. > > I'm curious why this approach was taken rather than a single well- > formed XML response being returned
The ability to add more than one document at once was an undocumented feature (untested even) that became semi-documented/supported when someone discovered it (mostly) worked. Things just sort of defaulted to responding as if multiple add commands had been received. Since the request is a single XML document, so should the response. >, and whether changing this is > acceptable. +1 > It would perhaps also be nice to get some context back > for each document added, like its unique key, so a response can > easily be correlated with an <add> other than aligning indexes. Document's aren't always required to have a unique id, but when they do, it could be added to a response. What about other commands that aren't related to a single document? Is there a need for a correlationId that Solr can echo back? -Yonik
