Update Log4J dependency

[Hitesh Kulkarni <hi...@na.honda.com>]

Hello,

We are using Solr 7.5, currently it is using Log4j 2.11.0. So we just want to update Log4j version instead of updating Solr. So is it possible to update only Log4j version in Solr?


Thanks & Regards,
Hitesh N. Kulkarni
Confidentiality Notice: This transmission (including any attachments) may contain confidential information belonging to the sender and is intended only for the use of the party or entity to which it is addressed. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, retention or the taking of action in reliance on the contents of this transmission is strictly prohibited. If you have received this transmission in error, please immediately notify the sender and erase all information and attachments.

Re: Update Log4J dependency

[Shawn Heisey <ap...@elyograg.org>]

On 12/20/2021 12:48 PM, Hitesh Kulkarni wrote:
> We are using Solr 7.5, currently it is using Log4j 2.11.0. So we just want to update Log4j version instead of updating Solr. So is it possible to update only Log4j version in Solr?

We have had reports of success upgrading the log4j jars when the 
original version was 2.13.0 and 2.14.1.  I do not know if it will work 
when the original version is 2.11.0, but the chances are good.  If Solr 
starts successfully after the replacement and there are no new errors in 
solr.log, you're probably good.

I just did an upgrade to log4j 2.17.0 on solr 7.5.0 by replacing jars in 
server/lib/ext with their 2.17.0 counterparts and deleting the 2.11.0 
versions and it seems to be working perfectly.  I did a query that 
resulted in an error and I see the error log entry in the admin UI.  The 
contents of solr.log do not look problematic.

Thanks,
Shawn

Streaming evaluators - exists

[Susmit Shukla <sh...@gmail.com>]

Hi,

I need to annotate the documents matching a simple boolean "OR" query
with actual terms found in each document. It is possible in single pass
using exists() function in fl param with /select handler.
e.g
q=text:(val1 OR val2 OR val3)
&fl=foo1:exists(query({!v='text:(val1)'})),foo2:exists(query({!v='text:(val2)'})),foo3:termfreq(content,'val3')

Can the same thing be achieved using /stream and /export handlers? Any
pointers to create custom term frequency or term exist stream evaluator
would be useful.