Uploaded image for project: 'NetarchiveSuite'
  1. NetarchiveSuite
  2. NAS-2752

We always look for duplicationmigration records during indexing

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Fixed
    • Minor
    • 5.4.1
    • 5.4
    • IndexServer
    • None
    • Hide

      1) Upload metadata-warc file for job X with duplicationmigrationrecords
      reset cache directory used by indexserver
      2) Order index for for Job X using testTool dk.netarkivet.harvester.tools.test.SendDedupIndexRequestToIndexserver
      3) Verify that no logentry in Indexserver looks like this 

      "Looking for a duplicationmigration record for id

      4) Shutdown indexserver and reset cachedir
      set tryToMigrateDuplicationRecords=true:

      <settings>
<harvester>
<indexserver>
<tryToMigrateDuplicationRecords>true</tryToMigrateDuplicationRecords>
</indexserver>
</harvester>
</settings

      5) Order index for for Job X using testTool dk.netarkivet.harvester.tools.test.SendDedupIndexRequestToIndexserver
      6) Verify that we now do find a logentry in Indexserver like this 

      "Looking for a duplicationmigration record for id

      This is only shown, if logging at debug level is enabled

      Show
      1) Upload metadata-warc file for job X with duplicationmigrationrecords reset cache directory used by indexserver 2) Order index for for Job X using testTool dk.netarkivet.harvester.tools.test.SendDedupIndexRequestToIndexserver 3) Verify that no logentry in Indexserver looks like this "Looking for a duplicationmigration record for id 4) Shutdown indexserver and reset cachedir set tryToMigrateDuplicationRecords=true: <settings> <harvester> <indexserver> <tryToMigrateDuplicationRecords> true </tryToMigrateDuplicationRecords> </indexserver> </harvester> </settings 5) Order index for for Job X using testTool dk.netarkivet.harvester.tools.test.SendDedupIndexRequestToIndexserver 6) Verify that we now do find a logentry in Indexserver like this "Looking for a duplicationmigration record for id This is only shown, if logging at debug level is enabled

    Description

      It is extra overhead to always look for duplicationmigration records during the indexing phase.
      This feature should be something we can turn off, and it should be turned off by default

      Attachments

        Activity

          People

            svc Søren Vejrup Carlsen (Inactive)
            svc Søren Vejrup Carlsen (Inactive)
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - Not Specified
                Not Specified
                Logged:
                Time Spent - 2m
                2m