Uploaded image for project: 'Configuration Persistence Service'
  1. Configuration Persistence Service
  2. CPS-1821

Use moduleSetTagCache to be cleared or updates as algorithm wil re-use existing schema set name


    • Icon: Story Story
    • Resolution: Duplicate
    • Icon: Medium Medium
    • Montreal Release
    • None
    • NCMP
    • None

      Using of the Hazelcast map:

          - check the new Hazelcast cache before checking the DB when processing a new moduleSetTag

          - if the module reference is already in the cache then we should not query the DB/DMI

          - if it's in the DB but not in the cache --> retrieve all the module references and store in the cache

          - if its not in the DB then retrieve from the DMI and then store in DB

          - new entries should be stored for 1hr


          - Hazelcast port documentation should be updated before this ticket is closed

          - System should query the DB/DMI once for the same moduleSetTag within the same instance

            sourabh_sourabh Sourabh Sourabh
            sourabh_sourabh Sourabh Sourabh
            0 Vote for this issue
            1 Start watching this issue