Hi, In a project I'm working on, we adopted the same approach as the one commented by Jorge Luis (use a separate core and let the front-end send the query to solr to store it). Depending on the analysis you want to achieve it could be interesting to delete duplicates or not (have 1 solr document per reqeuest). Apart from that, in order to inject all the legacy data we used logstash <http://logstash.net/> (for log parsing) and banana <https://github.com/LucidWorks/banana> (for reporting).
Regards. On Mon, Feb 9, 2015 at 9:14 AM, Siegfried Goeschl <sgoes...@gmx.at> wrote: > Hi folks, > > I implemented something similar but never got around to contribute it - > see https://issues.apache.org/jira/browse/SOLR-4056 > > The code was initially for SOLR3 but was recently ported to SOLR4 > > * capturing the most frequent search terms per core > * supports ad-hoc queries > * CSV export > > If you are interested we could team up and make a proper SOLR contribution > :-) > > Cheers, > > Siegfried Goeschl > > > > On 08.02.15 05:26, S.L wrote: > >> Folks, >> >> Is there a way to implement the trending functionality using Solr , to >> give >> the results using a query for say the most searched terms in the past >> hours >> or so , if the most searched terms is not possible is it possible to at >> least the get results for the last 100 terms? >> >> Thanks >> >> >
