Thanks very much the trace idea is a brilliant way to dig into it. Did not occur to me.
I had another coworker suggest the custom http://lucene.apache.org/solr/6_3_0/solr-core/org/apache/solr/update/processor/LogUpdateProcessorFactory.html this is beyond my litmited abilites. I will see what we can dig up out of the logs... the original request was this... "Is there any configuration, plugin, or application that will create an audit trail for Solr requests? We have teams that would like to be able to pull back changes/requests to documents in solr given a time period. The information they would like to retrieve is the request to solr, where it came from, and what the request did." I am starting to think there is not a simple solution to this. I was hoping there was an UpdateAudit class or something I could flip a switch on or some such... On Tue, Dec 6, 2016 at 2:20 PM, Alexandre Rafalovitch <arafa...@gmail.com> wrote: > You could turn the trace mode for everything in the Admin UI (under > logs/levels) and see if any of the existing information is sufficient > for your needs. If yes, then you change log level in the configuration > just for that class/element. > > Alternatively, you could do a custom UpdateRequestProcessor in the > request handler(s) that deal with update. Or perhaps > LogUpdateProcessor (that's in every standard chain) is sufficient: > http://www.solr-start.com/javadoc/solr-lucene/org/ > apache/solr/update/processor/LogUpdateProcessorFactory.html > > But it is also possible that the audit.log is something that has a > specific format that other tools use. So, you could start from asking > how that file would be used and then working backwards into Solr. > Which would most likely be a custom URP, as I mentioned earlier. > > Regards, > Alex. > P.s. Remember that there are full document updates and partial > updates. What you want to log about that is your business level > decision. > -- Thanks, Jeff Courtade M: 240.507.6116
