jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Archiva
  • MRM-129

flush the index periodically during rebuild

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: None
  • Fix Version/s: 1.0-alpha-1
  • Component/s: indexing
  • Labels:
    None

Description

currently, the indexing can take some time when it is done from scratch on a large repository, and requires a large amount of memory. It would be good to periodically checkpoint the index with a set of artifacts already completed.

How this affects the timestamp used needs to be interpreted, as if the indexing is stopped it may want to avoid reindexing those already done. Perhaps an alternative is to sort the discovered artifacts by timestamp, and setting it to the most recent one done - this can be considered in conjunction with the current issue that synced artifacts sometimes are new but have a timestamp older than the last indexing time and so are not indexed.

Issue Links

relates to

Bug - A problem which impairs or prevents the functions of the product. MRM-133 discovery might not find artifacts added as a result of rsync

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Brett Porter added a comment - 04/Sep/06 12:28 AM

this isn't necessary after the refactoring, and a better solution will be to allow some parallelism in the indexing process, which a new issue will be opened for.

Show
Brett Porter added a comment - 04/Sep/06 12:28 AM this isn't necessary after the refactoring, and a better solution will be to allow some parallelism in the indexing process, which a new issue will be opened for.

People

  • Assignee:
    Brett Porter
    Reporter:
    Brett Porter
Vote (0)
Watch (0)

Dates

  • Created:
    02/Aug/06 12:00 AM
    Updated:
    02/Jun/07 7:11 AM
    Resolved:
    04/Sep/06 12:28 AM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.