Uploaded image for project: 'AdMaxLocal'
  1. AdMaxLocal
  2. AML-4397

Ad loader does not over write the existing ETAs

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Not a Bug
    • Affects Version/s: Giraffe
    • Fix Version/s: Giraffe
    • Component/s: Data Loader
    • Labels:
      None
    • Environment:

      Ad loader

    • Sprint:
      Sprint 8

      Description

      On loading the ETAs into the DB, it doesn't overwrite the old ETA ads if any.
      It doesn't affect the STAs as the contentElementTokenID for ETAs and STAs are different.
      In production, this would not be a problem as ETAs will be loaded into DB for the 1st time.
      But, in any case if you re-load the ETA file for a particular BA again, then there will be duplicates created. The work around is that before loading the ETAs for the 2nd time, you could delete the old ETAs manually and reload them.

      QA4
      SELECT * FROM content_repository.contentElementVariations WHERE contentGroupID IN (SELECT id FROM content_repository.contentGroups WHERE businessAreaID=10002)

      has multiple entries of contentElementTokenID=17,18,19 from the previous load and the new load.

        Attachments

          Activity

            People

            • Assignee:
              gurpreet.singh Gurpreet Singh
              Reporter:
              varshini.padmanabhan Varshini Padmanabhan (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: