Hi Alex & Andrea for the reply.
But Alex, Our main idea was to reduce network latency, since the only
processing needed is only i/p to the next call, which is totally Solr
params, like facets, sorting query etc. Thats the reason I am looking
for the same.
Thanks, Andrea but in my case the cores ar
Hi,
What Alexander said is right, but if in your scenario you would still go
for that, you could try this [1], that should fit your need.
Best,
Andrea
[1] https://github.com/SeaseLtd/composite-request-handler
On Mon, 3 Dec 2018, 13:26 Alexandre Rafalovitch You should not be exposing Solr direc
You should not be exposing Solr directly to the client, but treating
it more as a database.
Given that, why would you not write your processing code in that
middle-ware layer?
Regards,
Alex.
On Mon, 3 Dec 2018 at 06:43, Lucky Sharma wrote:
>
> Hi have one scenario,
> where I need to make a se
Is it not possible to expose the shards to your IP and eclipse-debug the
queries via the solr frontend? If you need to intercept the queries between
frontend and shards in a non-windows environment, you could try wireshark
or tcpmon (http://ws.apache.org/commons/tcpmon/)
On Wed, Dec 7, 2011 at 10:
i am already using eclipse jetty for debugging but it is really hectic when
we have shards and queries going to each shard i want to skip it and see in
the fiddler rather.
--
Kashif Khan. B.E.,
+91 99805 57379
http://www.kashifkhan.in
On Wed, Dec 7, 2011 at 12:54 PM, Dmitry Kan [via Lucene] <
ml
If you mean debugging the queries, you can use eclipse+jetty plugin setup (
http://code.google.com/p/run-jetty-run/) with solr web app (
http://hokiesuns.blogspot.com/2010/01/setting-up-apache-solr-in-eclipse.html
)
On Tue, Dec 6, 2011 at 2:57 PM, Kashif Khan wrote:
> Hi all,
>
> I have develope
