Re: Searching for Tika Jira issues using Lucene
Woops, thank you for moving this to the right mailing list Oleg! Mike McCandless http://blog.mikemccandless.com On Thu, Mar 6, 2014 at 12:56 AM, Oleg Tikhonov wrote: > Hi Mike! > Sounds great! Thanks. > > Oleg > > > On Wed, Mar 5, 2014 at 6:47 PM, Michael McCandless < > luc...@mikemccandless.com> wrote: > >> Team, >> >> If you want to search for Tika Jira issues, I just added Tika coverage >> into the Lucene "dog food" server we use for finding Lucene/Solr >> issues at http://jirasearch.mikemccandless.com. >> >> I just posted a blog post describing recent changes: >> >> >> http://blog.mikemccandless.com/2014/03/using-lucenes-search-server-to-search.html >> >> Basically I started this as an effort to test Lucene's functionality >> in a "real" application/server (searching for issues), and to eat our >> own dog food, but then over time I think it's proven quite useful >> and I now use it almost exclusively when I need to find a Lucene issue. >> >> Compared to Jira's builtin search, it's more "full text" like; e.g., >> makes suggestions as you type, produces snippets and highlights, ranks >> by blended relevence+recency, etc. It has facets so you can quickly >> drill down/sideways by various metadata. In the results, you can >> click on a snippet to go straight to the specific comment and issue >> that it came from. >> >> It uses Lucene's near-real-time indexing + searching, so issue updates >> should be visible within ~ 30 seconds or so. >> >> I hope you find it useful too! >> >> Mike McCandless >> >> http://blog.mikemccandless.com >>
Re: Searching for Tika Jira issues using Lucene
Hi Mike! Sounds great! Thanks. Oleg On Wed, Mar 5, 2014 at 6:47 PM, Michael McCandless < luc...@mikemccandless.com> wrote: > Team, > > If you want to search for Tika Jira issues, I just added Tika coverage > into the Lucene "dog food" server we use for finding Lucene/Solr > issues at http://jirasearch.mikemccandless.com. > > I just posted a blog post describing recent changes: > > > http://blog.mikemccandless.com/2014/03/using-lucenes-search-server-to-search.html > > Basically I started this as an effort to test Lucene's functionality > in a "real" application/server (searching for issues), and to eat our > own dog food, but then over time I think it's proven quite useful > and I now use it almost exclusively when I need to find a Lucene issue. > > Compared to Jira's builtin search, it's more "full text" like; e.g., > makes suggestions as you type, produces snippets and highlights, ranks > by blended relevence+recency, etc. It has facets so you can quickly > drill down/sideways by various metadata. In the results, you can > click on a snippet to go straight to the specific comment and issue > that it came from. > > It uses Lucene's near-real-time indexing + searching, so issue updates > should be visible within ~ 30 seconds or so. > > I hope you find it useful too! > > Mike McCandless > > http://blog.mikemccandless.com >
Searching for Tika Jira issues using Lucene
Team, If you want to search for Tika Jira issues, I just added Tika coverage into the Lucene "dog food" server we use for finding Lucene/Solr issues at http://jirasearch.mikemccandless.com. I just posted a blog post describing recent changes: http://blog.mikemccandless.com/2014/03/using-lucenes-search-server-to-search.html Basically I started this as an effort to test Lucene's functionality in a "real" application/server (searching for issues), and to eat our own dog food, but then over time I think it's proven quite useful and I now use it almost exclusively when I need to find a Lucene issue. Compared to Jira's builtin search, it's more "full text" like; e.g., makes suggestions as you type, produces snippets and highlights, ranks by blended relevence+recency, etc. It has facets so you can quickly drill down/sideways by various metadata. In the results, you can click on a snippet to go straight to the specific comment and issue that it came from. It uses Lucene's near-real-time indexing + searching, so issue updates should be visible within ~ 30 seconds or so. I hope you find it useful too! Mike McCandless http://blog.mikemccandless.com