Suresh
If you have a web app in front of Solr and it or Apache logs all requests then
you should be able to match the log entries to the solr.log entries. That would
tell you a source IP, but it might not help if the users are behind a nat
firewall. But yes, you could look at the nat firewall lo
There is no need to change anything related to query parsers. A search
component should be enough.
On Wed, Aug 9, 2017 at 9:56 PM, suresh pendap wrote:
> Thanks Shalin for the reply.
> Do I need to also update the query parsers in order to handle the new query
> param?
> I can build a custom comp
Thanks Shalin for the reply.
Do I need to also update the query parsers in order to handle the new query
param?
I can build a custom component but dabbling with query parsers would be way
too much for me to handle.
Thanks
Suresh
On Tue, Aug 8, 2017 at 9:49 PM, Shalin Shekhar Mangar <
shalinman
There is no in-built way but if you are willing to create a custom
query component then it should be easy to mandate that every query
must have a tag parameter by throwing an exception otherwise. Any
query param you pass to a distributed query request should be
propagated to all query nodes as well
Hi,
We have found that application teams often fire ad-hoc queries, some of
these are very expensive queries and can bring the solr cluster down. Some
times they just build custom scripts which does some offline analytics by
firing expensive queries, the solr cluster was originally not sized for
e