Enterprise Search support for Apache Lucene and Solr by Lucid Imagination

Secondary links

  • Contact Us
  • Log in
  • Downloads
  • Solutions
    • Software |
    • Services |
    • Training |
    • White Papers & Case Studies |
    • Webinars & Events |
  • Developers
    • Blog |
    • Tech Articles |
    • Community |
    • Documentation |
    • Downloads |
    • Webcasts & Podcasts |
  • About
    • Market Overview |
    • Management |
    • Company News |
    • In the Media |
    • Contact |

beta

Start new search

Options

  • results per page

Clear all facets

  • Project clear projects

  • Source clear sources

  • Author clear authors

Search Results for

Results loading...

Found 90,988 results in 0.229 seconds. Displaying page 1 of 9,099, sorted by

  1. [lucene-dev] Re: Baby steps towards making Lucene's scoring more flexible...

    Sent 2010-03-15 by Marvin Humphrey <marvin@...>

    On Mon, Mar 15, 2010 at 05:28:33AM -0500, Michael McCandless wrote: > I mean specifically one should not have to commit to the precise > scoring model they will use for a given field, when they index that > field. Yeah, I've never seen committing to a precise scoring model at index-time via Sim ...

  2. [lucene-user] RE: Increase number of available positions?

    Sent 2010-03-15 by Steven A Rowe <sarowe@...>

    Hi Rene, Have you seen SpanNotQuery?: For a document that looks like: T1 T2 T3 T4 T5 T6

  3. [lucene-user] Re: Increase number of available positions?

    Sent 2010-03-15 by Erick Erickson <erickerickson@...>

    Not quite what I had in mind, more like level1-1/level2-1/level3-1/Term1 level1-1/level2-1/level3-1/Term2 level1-1/level2-1/level3-2/Term3 level1-1/level2-1/level3-2/Term4 With an increment gap 0f 100 and an analyzer that split on slashes, the term positions would be something like: term term...

  4. [lucene-dev] Re: [DISCUSS] Do away with Contrib Committers and make core committers

    Sent 2010-03-15 by Ryan McKinley <ryantxu@...>

    > > Personally I'd prefer we just stop adding them, and the current ones work > their way up like normal if they are so inclined, or the ones that are not > even around anymore can just stay as they are. > This seems reasonable to me. ------------------------------------------------------------...

  5. [lucene-user] Re: Increase number of available positions?

    Sent 2010-03-15 by Rene Hackl-Sommer <rene.a.hackl@...>

    Hi Erick, > What about indexing > the triplets with a small increment gap between? That is: > ... > gets indexed as: > > level1-1/level2-1/level3-1 +gap 100 > level1-1/level2-1/level3-2 +gap 100 > level1-1/level2-2/level3-3 +gap 100 > level1-1/level2-2/level3-4 > If I understand this corr...

  6. [lucene-user] Re: Increase number of available positions?

    Sent 2010-03-15 by Rene Hackl-Sommer <rene.a.hackl@...>

    Hi Steve, > Why can't you use a different field for each of the Level_X's, i.e. MyLevel1Field, MyLevel2Field, MyLevel3Field? > Well, the hierarchical structure needs to be maintained. As hundreds of Level_X entities can be found on levels 2 and 3, I need to be able to tell for instance wh...

  7. [lucene-dev] Re: [DISCUSS] Do away with Contrib Committers and make core committers

    Sent 2010-03-15 by DM Smith <dmsmith555@...>

    My 2 cents as one who has no aspirations of ever being a committer. I think with the pending re-org of contrib and the value of contrib, it doesn't make much sense to have the distinction between core and contrib let alone for contributors. Regarding the former low bar, either prune the list ...

  8. [lucene-dev] Re: [DISCUSS] Do away with Contrib Committers and make core committers

    Sent 2010-03-15 by Grant Ingersoll <gsingers@...>

    On Mar 15, 2010, at 1:25 PM, Mark Miller wrote: > On 03/15/2010 08:33 AM, Grant Ingersoll wrote: >> Right, Mark. I think we would be effectively raising the bar to some extent for what it takes to be a committer. > > That's part of my point though - some are contrib committers with a lower bar...

  9. [lucene-dev] Re: [DISCUSS] Do away with Contrib Committers and make core committers

    Sent 2010-03-15 by Mark Miller <markrmiller@...>

    On 03/15/2010 08:33 AM, Grant Ingersoll wrote: > Right, Mark. I think we would be effectively raising the bar to some extent for what it takes to be a committer. That's part of my point though - some are contrib committers with a lower bar - now they are core/solr committers with that lower ba...

  10. [lucene-user] Re: Batch Indexing - best practice?

    Sent 2010-03-15 by Erick Erickson <erickerickson@...>

    What's a document? What's indexing? Here's what I'd do as a very first step. Time the actual indexing and report it out. By that I mean how long does IndexWriter.addDocument() take? If you actually get the document from wherever first then add all the fields and add the document, I'd time adding...

  1. 1
  2. 2
  3. 3
  4. 4
  5. 5
  6. 6
  7. 7
  8. 8
  9. 9
  10. 10
  11. >>

Solr Powered

Give us your feedback

  • Lucene
  • Solr
  • Nutch
  • Tika
  • Mahout
  • Droids
  • PyLucene
  • Lucene.Net
  • Lucy
  • Lucene4c
  • Open Relevance Project
  • How We Can Help:
    • Getting Started |
    • Support Subscriptions |
    • White Papers |
    • Training |
    • Consulting |
    • Contact Us |
  • Developers:
    • Blog |
    • Documentation |
    • Tech Articles |
    • Podcasts and Videos |
    • Community |
  • Downloads:
    • LucidWorks for Solr |
    • LucidWorks for Lucene |
    • LucidGaze for Solr |
    • LucidGaze for Lucene |
  • Products:
  • Services:

Contact | Privacy Policy | Legal Terms of Use | Copyrights and Disclaimers | Admin

Apache Solr, Apache Lucene, ApacheCon and their logos are trademarks of the Apache Software Foundation.

© 2010 Lucid Imagination. All Right reserved.