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.068 seconds. Displaying page 5 of 12,175, sorted by

  1. [lucene-user] Re: Fields with Field.Store.NO and Field.Index.ANALYZED not being indexed

    Sent 2010-08-29 by Erick Erickson <erickerickson@...>

    Adding to Uwe's comment, you may be operating under a false assumption. Lucene has no capability to update fields in a document. Period. This is one of the most frequently requested changes, but the nature of an inverted index makes this...er...tricky. Updates are really a document delete followe...

  2. [lucene-user] RE: Fields with Field.Store.NO and Field.Index.ANALYZED not being indexed

    Sent 2010-08-29 by Uwe Schindler <uwe@...>

    You cannot retrieve non-stored fields. They are analyzed and tokenized during indexing and this is a one-way transformation. If you update documents you have to reindex the contents. If you do not have access to the original contents anymore, you may consider adding a stored-only "raw document" f...

  3. [lucene-user] Re: Fields with Field.Store.NO and Field.Index.ANALYZED not being indexed

    Sent 2010-08-29 by Constantine Vetoshev <gepardcv@...>

    Thanks Erick. I finally had time to go back and look at this problem. I discovered that the analyzed fields work fine for searching until I use IndexWriter.updateDocument(). The way my application runs, it has to update documents several times to update one specific field. The update code queri...

  4. [lucene-general] Re: Performance Optimizations and Expected Benchmark Results

    Sent 2010-08-29 by Ted Dunning <ted.dunning@...>

    So the current state of your problem is this: a) desired indexing speed = 10,000 objects per second (peak rate) (ish) b) total number of objects = 10,000,000 This gives desired from-scratch indexing time of 1000 seconds = 17 minutes c) object life = 2+ days but 2 days = 170,000 seconds. At ...

  5. [lucene-general] Re: Performance Optimizations and Expected Benchmark Results

    Sent 2010-08-29 by Ted Dunning <ted.dunning@...>

    I think you missed Jenny's point. She was asking whether you could buffer up a hundred or a thousand (or more) items and index them all at once. This doesn't require that you go to the data store, just that you have a buffer that sticks around for a few minutes (or seconds from your apparent in...

  6. [lucene-general] Omitting unstemmed words in GermanAnalyzer

    Sent 2010-08-29 by exlibrit <exlibrit@...>

    Hi, I am beginner of Java and Lucene. Maybe it is very easy, but i could not find any solutions, my problem is that: 1. I want to stem German words, 2. If the word isn't stemmed then don't include it into the index, by doing this, dont lose nex word's position. Which code blocks i need to chang...

  7. [lucene-general] Re: Performance Optimizations and Expected Benchmark Results

    Sent 2010-08-29 by Ron Ratovsky <ronr@...>

    Answers are within the message. On Fri, Aug 27, 2010 at 22:05, Ted Dunning wrote: > Can you say a bit more about your application? How many object total are > there? > > Our goal is to hold a few tens of millions objects at any given time. > What is an object lifetime...

  8. [lucene-general] Re: Performance Optimizations and Expected Benchmark Results

    Sent 2010-08-29 by Ron Ratovsky <ronr@...>

    The indexing is done synchronously to saving the data. Doing it asynchronously works slower since then the data to be indexed needs to be read from the data store, which is slower. On Thu, Aug 26, 2010 at 18:58, Jenny Brown wrote: > Do you index as you go along, or do you ba...

  9. [lucene-solr-dev] Build failed in Hudson: Lucene-trunk #1272

    Sent 2010-08-29 by Apache Hudson Server <hudson@...>

    See Changes: [rmuir] LUCENE-2624: add armenian, basque, catalan analyzers from snowball [rmuir] LUCENE-2624: add armenian, basque, catalan analyzers from snowball [rmuir] SOLR-2059: Add types attribute to WordDelimiterFilterFact...

  10. [lucene-solr-dev] Re: Build failed in Hudson: Lucene-3.x #99

    Sent 2010-08-28 by Robert Muir <rcmuir@...>

    my mistake... this test should be toned down, its a bit too intense On Aug 28, 2010 8:53 PM, "Apache Hudson Server" wrote: > See > > Changes: > > [rmuir] LUCENE-2624: add armenian, basque, catalan analyzers f...

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

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.