Yes, that’s how it is generally done - adding extra Solr-ignoring parameters to the requests.
— Erik Hatcher, Senior Solutions Architect http://www.lucidworks.com <http://www.lucidworks.com/> > On Jul 17, 2015, at 5:47 AM, marotosg <marot...@gmail.com> wrote: > > Hi, > > i have a use case where We would like to know what are the users searching > for. Most commonly used criteria etc. > One requirement is related to the user who is searching. We need to know who > is making each search but this is not criteria itself. It is just analysis > information. > > I was wondering what is the approach to add to the query to be logged > analytical information which is not searchable and which is the best > approach to do analytics on Solr. > > For Instance. I have a person collection and a user searches for Person > name. I need to inject the user who is searching but it's is not going to > filter by that user. I am thinking on adding this as an extra param. > Person collection q=PersonName:Peter&*UserID:55* > > Thanks for your help > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Analytics-on-Solr-logs-tp4217807.html > Sent from the Solr - User mailing list archive at Nabble.com.
