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

Build 382: Staging Area problems

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: Data Loader 1.0
    • Fix Version/s: Data Loader 1.0
    • Component/s: None
    • Labels:
      None
    • Environment:

      Build 382

    • Story Points:
      5
    • Sprint:
      Sprint 10, Sprint 11

      Description

      Cleared cache, restarted tomcat and restarted Firefox so hopefully it's not my Firefox being weird.

      1. Keywords don't seem to be getting loaded into respective tables in the Staging Area schema anymore. Assuming a merge conflict in the past few Builds. (Column count doesn't match value count at row 1)

      2. When moving multiple keyword files to Staging Area a lot of them don't seem to properly grab the respective BAID (INFO: Checking/clearing/creating/dropping table 'keywords_tmp_0') (3/4) Seemed to resolve itself after bypassing/refreshing cache(ctrl + F5). Seems like preference -> clear cache isn't good enough

      3. Deleting the current Staging Area sometimes doesn't remove all/any file tabs (deletes it in DB)

      4. Re-selecting the Staging Area deletes a file tab every time. When all file tabs are gone, re-selecting Staging Area repopulates the table with file tabs using data from tables in Staging Area database

        Attachments

          Activity

            People

            • Assignee:
              dylan.kirby Dylan Kirby (Inactive)
              Reporter:
              endy.nicol Endy Nicol (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: