Uploaded image for project: 'Talend Data Prep'
  1. Talend Data Prep
  2. TDP-4934

[Migration] Regressions found by migrating 6.4.1 dq dict types

Apply templateInsert Lucidchart Diagram
    XMLWordPrintable

Details

    • All
    • Sprint 21 TDP, Sprint 22 TDP, Sprint 23 TDP (feb 26), Sprint 24 TDP (mar 19)
    • Small
    • 'Waiting for External Projects'

    Description

      Plz note that we don't need to do republish action. The migration should be done at the start of the dq dict server.

      This prb is identified by DQ team, cf TDQ-14658

      Plz contact me if you need a database and an env to test.

      Steps to do the migration with DQ dict:

      1. Create / delete / update semantic types in 6.4.1 platform.
      2. Did some preparations using the customer types
      3. Perform migration from 6.4.1 to 6.5.1 platform as documented @ https://help.talend.com/reader/A5L7iwIz4xh7_MplMw8P3g/Qe2K6K7aiJ1PyWQZuRj5_w
        TL;DR:
        1. Stop TDP and DQDICT on 6.4.1 platform
        2. Dump TDP and DQDICT Mongo DBs on 6.4.1 platform
        3. Restore TDP and DQDICT Mongo DBs on 6.5.1 platform
        4. Restart DQDICT on 6.5.1 platform
        5. Restart TDP on 6.5.1 platform

      Current results:

      Plz see my screenshot, for the column Land_copy, it should be recognized as "test_de_land" type, a customer type. But in its sub menu, there is no this new type.

      Expected results:

      The customer types as "test_de_land" should be available after migration.

      FYI, if I did a republish, all my 641 types are available on 651

      Attachments

        1. app.log
          38 kB
        2. compoundOn641Prep.PNG
          compoundOn641Prep.PNG
          10 kB
        3. compoundOn651prep.PNG
          compoundOn651prep.PNG
          13 kB
        4. DQ_afterMigration.png
          DQ_afterMigration.png
          89 kB
        5. Phone.csv
          0.0 kB
        6. Sélection_201.png
          Sélection_201.png
          104 kB
        7. test_compound+2018-01-10_21-52-24-332.json
          2 kB
        8. type651_missing_after_restart.png
          type651_missing_after_restart.png
          41 kB
        9. types_on651.PNG
          types_on651.PNG
          33 kB

        Issue Links

          depends on

          New Feature - TDQ-7819 The browse button in the synonym index view should be smarter

          • Minor - Less important parts of the product are affected by the problem or a solution is available for avoiding major consequences. A minor impairment of the customer's business is possible.
          • New
          is duplicated by

          Bug - TDP-4975 641 Migrated compound type cannot have a correct quality bar on a new 651 dataset

          • Major - There are major errors in a system function. However, the error situation is not critical. The customer's business may be impaired by it.
          • closed
          is related to

          Bug - TDP-5811 [Migration from 701 to 711] Republish event is not propagated well when start producer server

          • Critical - The customer's production system is in a critical error situation. Basic functions of the supported software are not usable. The consequences can have a serious impact on the customer's business. This is the highest error category for issues arising outside of production systems.
          • closed

          Bug - TDQ-14794 CategoryRecognizerBuilder don't get compound categories correctly

          • Critical - The customer's production system is in a critical error situation. Basic functions of the supported software are not usable. The consequences can have a serious impact on the customer's business. This is the highest error category for issues arising outside of production systems.
          • closed

          Bug - TDQ-14703 Dq dict events disordered when re started TDP server

          • Blocker - The customer's production system is blocked. The production system cannot be started, is functionally unusable or disproportionately slow. This category can only be used for the productive system. The highest priority category for issues in non-productive systems is priority Category 2.
          • closed

          Activity

            People

              Unassigned Unassigned
              mbocquet Matthieu Bocquet
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 0 minutes
                  0m
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 3 hours
                  3h