You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@lucenenet.apache.org by Sean Newham <Se...@grantadesign.com> on 2011/12/13 16:13:41 UTC
[Lucene.Net] Decoding an index
Hi,
I'm new to Lucene, and I was wondering if there was a quick, code way (preferably in c#, but I'll take python or java) of getting the list of most common search queries out. I've done a google, and found Luke (which is cool) and may start looking through its code as it clearly must be doing this somewhere, but my next step is to look through the Lucene docs. Any help would be appreciated, including telling me which docs to read, etc.
Best wishes,
Sean
Re: [Lucene.Net] Decoding an index
Posted by Ben West <bw...@yahoo.com>.
Lucid Imagination did a post on how to do this: http://www.lucidimagination.com/blog/2009/09/08/auto-suggest-from-popular-queries-using-edgengrams/
You basically just store each query in Lucene along with a count of how many times it's been searched.
----- Original Message -----
From: Sean Newham <Se...@grantadesign.com>
To: "lucene-net-user@lucene.apache.org" <lu...@lucene.apache.org>
Cc:
Sent: Tuesday, December 13, 2011 9:25 AM
Subject: RE: [Lucene.Net] Decoding an index
Ah, I see. Maybe I should do this somewhere else.
Thank you both for your help,
Sean
-----Original Message-----
From: Wyatt Barnett [mailto:wyatt.barnett@gmail.com]
Sent: 13 December 2011 15:22
To: lucene-net-user@lucene.apache.org
Subject: Re: [Lucene.Net] Decoding an index
We do some tracking of this ourselves, and I don't think lucene has
this sort of capability as it is something that makes alot more sense
to handle on the application layer where it understands the semantics
of your search.
On Tue, Dec 13, 2011 at 10:19 AM, Kevin Miller <sc...@gmail.com> wrote:
> We do this but it involves logging the search query to a database. We
> have an abstraction about search clients to do this.
>
> I recommend the Lucene In Action book. Quite good.
>
> On Dec 13, 2011, at 9:14 AM, Sean Newham <Se...@grantadesign.com> wrote:
>
>> Hi,
>> I'm new to Lucene, and I was wondering if there was a quick, code way (preferably in c#, but I'll take python or java) of getting the list of most common search queries out. I've done a google, and found Luke (which is cool) and may start looking through its code as it clearly must be doing this somewhere, but my next step is to look through the Lucene docs. Any help would be appreciated, including telling me which docs to read, etc.
>> Best wishes,
>> Sean
RE: [Lucene.Net] Decoding an index
Posted by Moray McConnachie <mm...@oxford-analytica.com>.
I highly recommend writing application layer wrapper objects for all
Lucene functionality, which can provide the features you and Wyatt are
discussing.
For example, we have a hierarchy of wrapper search objects, all of which
implement an interface ILuceneSearch.
ILuceneSearch has just one method:
Lucene.Net.Query BuildLuceneQuery()
This allows us to keep Lucene and our application logic entirely
separate - our search objects also implement a serialisation interface
so they can be stored persistently wherever we want (in our case to a
database).
Yours,
Moray
-----Original Message-----
From: Sean Newham [mailto:Sean.Newham@grantadesign.com]
Sent: 13 December 2011 15:25
To: lucene-net-user@lucene.apache.org
Subject: RE: [Lucene.Net] Decoding an index
Ah, I see. Maybe I should do this somewhere else.
Thank you both for your help,
Sean
-----Original Message-----
From: Wyatt Barnett [mailto:wyatt.barnett@gmail.com]
Sent: 13 December 2011 15:22
To: lucene-net-user@lucene.apache.org
Subject: Re: [Lucene.Net] Decoding an index
We do some tracking of this ourselves, and I don't think lucene has this
sort of capability as it is something that makes alot more sense to
handle on the application layer where it understands the semantics of
your search.
On Tue, Dec 13, 2011 at 10:19 AM, Kevin Miller <sc...@gmail.com>
wrote:
> We do this but it involves logging the search query to a database. We
> have an abstraction about search clients to do this.
>
> I recommend the Lucene In Action book. Quite good.
>
> On Dec 13, 2011, at 9:14 AM, Sean Newham
<Se...@grantadesign.com> wrote:
>
>> Hi,
>> I'm new to Lucene, and I was wondering if there was a quick, code way
(preferably in c#, but I'll take python or java) of getting the list of
most common search queries out. I've done a google, and found Luke
(which is cool) and may start looking through its code as it clearly
must be doing this somewhere, but my next step is to look through the
Lucene docs. Any help would be appreciated, including telling me which
docs to read, etc.
>> Best wishes,
>> Sean
---------------------------------------------------------
Disclaimer
This message and any attachments are confidential and/or privileged. If this has been sent to you in error, please do not use, retain or disclose them, and contact the sender as soon as possible.
Oxford Analytica Ltd
Registered in England: No. 1196703
5 Alfred Street, Oxford
United Kingdom, OX1 4EH
---------------------------------------------------------
RE: [Lucene.Net] Decoding an index
Posted by Sean Newham <Se...@grantadesign.com>.
Ah, I see. Maybe I should do this somewhere else.
Thank you both for your help,
Sean
-----Original Message-----
From: Wyatt Barnett [mailto:wyatt.barnett@gmail.com]
Sent: 13 December 2011 15:22
To: lucene-net-user@lucene.apache.org
Subject: Re: [Lucene.Net] Decoding an index
We do some tracking of this ourselves, and I don't think lucene has
this sort of capability as it is something that makes alot more sense
to handle on the application layer where it understands the semantics
of your search.
On Tue, Dec 13, 2011 at 10:19 AM, Kevin Miller <sc...@gmail.com> wrote:
> We do this but it involves logging the search query to a database. We
> have an abstraction about search clients to do this.
>
> I recommend the Lucene In Action book. Quite good.
>
> On Dec 13, 2011, at 9:14 AM, Sean Newham <Se...@grantadesign.com> wrote:
>
>> Hi,
>> I'm new to Lucene, and I was wondering if there was a quick, code way (preferably in c#, but I'll take python or java) of getting the list of most common search queries out. I've done a google, and found Luke (which is cool) and may start looking through its code as it clearly must be doing this somewhere, but my next step is to look through the Lucene docs. Any help would be appreciated, including telling me which docs to read, etc.
>> Best wishes,
>> Sean
Re: [Lucene.Net] Decoding an index
Posted by Wyatt Barnett <wy...@gmail.com>.
We do some tracking of this ourselves, and I don't think lucene has
this sort of capability as it is something that makes alot more sense
to handle on the application layer where it understands the semantics
of your search.
On Tue, Dec 13, 2011 at 10:19 AM, Kevin Miller <sc...@gmail.com> wrote:
> We do this but it involves logging the search query to a database. We
> have an abstraction about search clients to do this.
>
> I recommend the Lucene In Action book. Quite good.
>
> On Dec 13, 2011, at 9:14 AM, Sean Newham <Se...@grantadesign.com> wrote:
>
>> Hi,
>> I'm new to Lucene, and I was wondering if there was a quick, code way (preferably in c#, but I'll take python or java) of getting the list of most common search queries out. I've done a google, and found Luke (which is cool) and may start looking through its code as it clearly must be doing this somewhere, but my next step is to look through the Lucene docs. Any help would be appreciated, including telling me which docs to read, etc.
>> Best wishes,
>> Sean
Re: [Lucene.Net] Decoding an index
Posted by Kevin Miller <sc...@gmail.com>.
We do this but it involves logging the search query to a database. We
have an abstraction about search clients to do this.
I recommend the Lucene In Action book. Quite good.
On Dec 13, 2011, at 9:14 AM, Sean Newham <Se...@grantadesign.com> wrote:
> Hi,
> I'm new to Lucene, and I was wondering if there was a quick, code way (preferably in c#, but I'll take python or java) of getting the list of most common search queries out. I've done a google, and found Luke (which is cool) and may start looking through its code as it clearly must be doing this somewhere, but my next step is to look through the Lucene docs. Any help would be appreciated, including telling me which docs to read, etc.
> Best wishes,
> Sean