just-in-time consumption of repository changes

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.0-beta-2
  • Fix Version/s: 1.0-beta-3
  • Component/s: repository scanning
  • Labels:
    None

Description

need to have a simple, reusable way to be able to trigger consumers for a given artifact just-in-time for things like addition via a proxy, removal via purge, etc.

Issue Links

is related to

Bug - A problem which impairs or prevents the functions of the product. MRM-454 Index not updated after repository purge

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

Improvement - An improvement or enhancement to an existing feature or task. MRM-158 automatically index proxied artifacts

  • Critical - Crashes, loss of data, severe memory leak.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Brett Porter added a comment -

it seems like the best thing to do here is:

  • wait until completion of any known batch of operations (eg, for purge, collect a list of artifacts removed)
  • for each consumer, execute beginScan; then for each file execute processFile; then for each consumer execute completeScan
  • rinse and repeat for database consumers

Things to check:

  • fault tolerance of running consumers at the same time (in case a scheduled scan occurs)
Show
Brett Porter added a comment - it seems like the best thing to do here is:
  • wait until completion of any known batch of operations (eg, for purge, collect a list of artifacts removed)
  • for each consumer, execute beginScan; then for each file execute processFile; then for each consumer execute completeScan
  • rinse and repeat for database consumers
Things to check:
  • fault tolerance of running consumers at the same time (in case a scheduled scan occurs)
Hide
Permalink
Brett Porter added a comment -

Also need to consider impact on design - do not want to highly couple other modules to the consumers architecture. Review current dependencies, consider being able to push these onto a queue instead of running them exactly just-in-time.

Show
Brett Porter added a comment - Also need to consider impact on design - do not want to highly couple other modules to the consumers architecture. Review current dependencies, consider being able to push these onto a queue instead of running them exactly just-in-time.

People

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

Dates

  • Created:
    Updated:
    Resolved: