Re: custom response writer which extends RawResponseWriter fails when shards > 1

rg : To: solr-user@lucene.apache.org : Subject: Re: custom response writer which extends RawResponseWriter fails when : shards > 1 : : Hi, : I've ended up processing the doclist in the response twice. Once in the : write method and once in getContent. Its a bit inefficient but i'm only : look

Re: custom response writer which extends RawResponseWriter fails when shards > 1

riter delegate to the javabin >> responsewriter if/when you see that this is an "isShard=true" request? >> >> >> >> : Date: Thu, 19 Apr 2018 18:42:58 +0100 >> : From: Lee Carroll <lee.a.carr...@googlemail.com> >> : Reply-To: solr-user@lucene.

Re: custom response writer which extends RawResponseWriter fails when shards > 1

; : Date: Thu, 19 Apr 2018 18:42:58 +0100 > : From: Lee Carroll <lee.a.carr...@googlemail.com> > : Reply-To: solr-user@lucene.apache.org > : To: solr-user@lucene.apache.org > : Subject: Re: custom response writer which extends RawResponseWriter > fails when > : shards >

Re: custom response writer which extends RawResponseWriter fails when shards > 1

rg : To: solr-user@lucene.apache.org : Subject: Re: custom response writer which extends RawResponseWriter fails when : shards > 1 : : Hi, : : I rewrote all of my tests to use SolrCloudTestCase rather than SolrTestCaseJ4 : and was able to replicate the responsewriter issue and debug wit

Re: custom response writer which extends RawResponseWriter fails when shards > 1

You can introduce own searchHandler with wt invariant. When aggreator request slaves it will use regular /select with default wt=javabin (it's condrolled by shards.qt, btw) Providing such comprehensive application logic on top of neat solrconfig.xml is not the best idea, though. On Thu, Apr 19,

Re: custom response writer which extends RawResponseWriter fails when shards > 1

Default works. However in the case (which is maybe my case) where request handler implies a response type and really should be locked down to prevent abuse or error you could argue invariant is needed. I guess its also not very elegant having an arbitrary rule, no wt as invariant in cloud mode

Re: custom response writer which extends RawResponseWriter fails when shards > 1

what if you put it into "defaults"? On Thu, Apr 19, 2018 at 8:42 PM, Lee Carroll wrote: > Hi, > > I rewrote all of my tests to use SolrCloudTestCase rather than > SolrTestCaseJ4 > and was able to replicate the responsewriter issue and debug with a sharded >

Re: custom response writer which extends RawResponseWriter fails when shards > 1

Hi, I rewrote all of my tests to use SolrCloudTestCase rather than SolrTestCaseJ4 and was able to replicate the responsewriter issue and debug with a sharded collection. It turned out the issue was not with my response writer really but rather my config. content In

Re: custom response writer which extends RawResponseWriter fails when shards > 1

Injecting headers might require deeper customisation up to establishing own filter or so. Speaking regarding your own WT, there might be some issues because usually it's not a big deal to use one wt for responding user query like (wt=csv) and wt=javabin in internal communication between aggregator

Re: custom response writer which extends RawResponseWriter fails when shards > 1

Inventive. I need to control content-type of the response from the document field value. I have the actual content field and the content-type field to use configured in the response writer. I've just noticed that the xslt transformer allows you to do this but not controlled by document values. I

Re: custom response writer which extends RawResponseWriter fails when shards > 1

well .. what if http://localhost:8983/solr/images/select?fl=content=id:1=1=csv; csv.separator==null ? On Wed, Apr 18, 2018 at 1:18 PM, Lee Carroll wrote: > sorry cut n paste error i'd get > > { > "responseHeader":{ > "zkConnected":true, > "status":0, >

Re: custom response writer which extends RawResponseWriter fails when shards > 1

sorry cut n paste error i'd get { "responseHeader":{ "zkConnected":true, "status":0, "QTime":0, "params":{ "q":"*:*", "fl":"content", "rows":"1"}}, "response":{"numFound":1,"start":0,"docs":[ { "content":"my-content-value"}] }} but you get

Re: custom response writer which extends RawResponseWriter fails when shards > 1

for http://localhost:8983/solr/images/select?fl=content=id:1=1 I'd get { "responseHeader":{ "zkConnected":true, "status":0, "QTime":1, "params":{ "q":"*:*", "_":"1524046333220"}}, "response":{"numFound":1,"start":0,"docs":[ { "id":"1",

Re: custom response writer which extends RawResponseWriter fails when shards > 1

Lee, from this description I don see why it can't be addressed by fl,rows params. What makes it different form the typical Solr usage? On Wed, Apr 18, 2018 at 12:31 PM, Lee Carroll wrote: > Sure, we want to return a single field's value for the top matching >

Re: custom response writer which extends RawResponseWriter fails when shards > 1

Sure, we want to return a single field's value for the top matching document for a given query. Bare content rather than a full search result listing. To be concrete: For a schema of fields id [unique key], content[stored],content-type[stored] For a request: 1. Request URL:

Re: custom response writer which extends RawResponseWriter fails when shards > 1

In distributed search response writer is used twice https://lucene.apache.org/solr/guide/7_1/distributed-requests.html once slave node that's where response writer yields "json" content and it upset aggregator node which is expect only javabin. I hardly can comment on rrw, it's probably used for

Re: custom response writer which extends RawResponseWriter fails when shards > 1

Ok. My expectation was the response writer would not be used until the final serialization of the result. If my response writer breaks the response writer contract, exactly the way rawResponseWriter does and just out puts a filed value how does that work? Does rawResponseWriter support cloud mode?

Re: custom response writer which extends RawResponseWriter fails when shards > 1

That's what should happen. Expected mime type application/octet-stream but got application/json. Distributed search coordinator expect to merge slave responses in javabin format. But slave's wt indicated json. As far as I know only javabin might be used to distributed search underneath.

Re: custom response writer which extends RawResponseWriter fails when shards > 1

Sure with 1 shard 1 replica this request works fine 1. Request URL: http://localhost:8983/solr/images/image?q=id:1 2. Request Method: GET 3. Status Code: 200 OK logs are clean with 2 shards 2 replicas the same request fails and in the logs INFO - 2018-04-17 13:20:32.052;

Re: custom response writer which extends RawResponseWriter fails when shards > 1

Lee, It's worth to send a stacktrace for such kind of inquiries. I guess it goes from QueryComponent.mergeIds() or so. Shard response should contains from schema.xml field. I encounter something like this while troubleshooting

custom response writer which extends RawResponseWriter fails when shards > 1

I've created a custom response writer which extends RawResponseWriter. The basic operation is to output a single field value from the top matching doc as the entire response. This works when shards = 1 but fails when shards are greater than 1. I throw an error if the field in question is missing