Lucid Imagination

Secondary links

  • Contact Us
  • Log out
  • Downloads
  • Solutions
    • Partners |
    • Blog |
    • Software |
    • Services |
    • Training |
    • Case Studies |
    • Webinars |
  • Developers
    • Blog |
    • Tech Articles |
    • Community |
    • Docs |
    • Downloads |
    • Whitepapers |
    • 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 121,742 results in 0.053 seconds. Displaying page 1 of 12,175, sorted by

  1. [lucene-solr-dev] commitReserveDuration, backups and saveCommitPoint

    Sent 2010-09-02 by Peter Sturge <peter.sturge@...>

    Hi, This post is related to SOLR-1475 - 'Java-based remplication doesn't properly reserve its commit point during backups', and index backups in general. In Solr 1.4 and 1.4.1, the SOLR-1475 patch is certainly there, but I don't believe it truly addresses the problem. Here's why: When a 'back...

  2. [lucene-solr-dev] Build failed in Hudson: Solr-trunk #1235

    Sent 2010-09-02 by Apache Hudson Server <hudson@...>

    See Changes: [rmuir] optimize surrogate case [mikemccand] allow leading wildcard in contrib/benchmark's FileBasedQueryMaker ------------------------------------------ [...truncated 6199 lines...] [junit] 2010-09-02 09.54.43 or...

  3. [lucene-solr-dev] Build failed in Hudson: Solr-3.x #91

    Sent 2010-09-02 by Apache Hudson Server <hudson@...>

    See Changes: [simonw] LUCENE-2239: Documented NIOFSDirectory and MMapDirectory limitations due to Java NIO behavior when a Thread is interrupted while blocking on IO. [simonw] LUCENE-2590: Enable access to the freq information in a Que...

  4. [lucene-solr-dev] Re: In Need of Direction; Phrase-Context Tracking / Injection (Child Indexes) / Dismissal

    Sent 2010-09-02 by Lance Norskog <goksron@...>

    Do you mean a new Solr/Lucene index, or a new document with only the snippet? On Wed, Sep 1, 2010 at 5:29 PM, Scott Gonyea wrote: > Hi, > > I'm looking to get some direction on where I should focus my attention, with > regards to the Solr codebase and documentation.  Rather t...

  5. [lucene-user] Re: Combine data from index and db before sorting and pagination

    Sent 2010-09-01 by Chris Lu <chris.lu@...>

    If there is an API to adjust the inverted index directly, it would be much efficient. I guess Mirko's problem is similar to this: There could be a "main_record" table and "category" table. Each "main_record" has a "category". When one "category" is changed, quite some "main_record" are affected....

  6. [lucene-solr-dev] Hudson build is back to normal : Lucene-3.x #103

    Sent 2010-09-01 by Apache Hudson Server <hudson@...>

    See --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional commands, e-mail: dev-help@lucene.apache.org

  7. [lucene-solr-dev] In Need of Direction; Phrase-Context Tracking / Injection (Child Indexes) / Dismissal

    Sent 2010-09-01 by Scott Gonyea <scott@...>

    Hi, I'm looking to get some direction on where I should focus my attention, with regards to the Solr codebase and documentation. Rather than write a ton of stuff no one wants to read, I'll just start with a use-case. For context, the data originates from Nutch crawls and is indexed into Solr. ...

  8. [lucene-user] Re: Combine data from index and db before sorting and pagination

    Sent 2010-09-01 by Erick Erickson <erickerickson@...>

    The usual first choice when using Lucene to search database data is to denormalize the db data into the index. Yes, it's redundant, but it's often a better solution than trying to use both. Synchronization can be an issue, but you have to deal with that anyway since you're indexing from the db an...

  9. [lucene-user] AW: Combine data from index and db before sorting and pagination

    Sent 2010-09-01 by "Sertic Mirko, Bedag" <Mirko.Sertic@...>

    The data from db is required for sorting, and one db entry matches to many index entries, so storing it in the index would be redundant. Also there would be the challenge to keep index and db in sync. Any ideas? Mirko -----Ursprüngliche Nachricht----- Von: Ian Lea [mailto:ian.lea@gmail.com] G...

  10. [lucene-user] Re: Combine data from index and db before sorting and pagination

    Sent 2010-09-01 by Ian Lea <ian.lea@...>

    If the sorting and pagination doesn't require data from the database, just do db lookups for the hits on a page, page by page as required. But if the db data is required I'd suggest storing it in the index. -- Ian. On Wed, Sep 1, 2010 at 1:43 PM, Sertic Mirko, Bedag wro...

  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 | Logout

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

© 2010 Lucid Imagination. All Right reserved.