Uploaded image for project: 'Talend Component Kit'
  1. Talend Component Kit
  2. TCOMP-794

Fix repository key conversion for metadata value retrieval

Apply templateInsert Lucidchart Diagram
    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • 1.0.1
    • None
    • None
    • Hide

      1. Create dataset for ServiceNow component in 7.0.1 released Studio
      2. Export this dataset
      3. Launch 7.1.0-SNAPSHOT Studio
      4. Import the dataset and try to create component using it (either drag and drop metadata or create component and then choose repository value)
      5. Component properties are not set

      Show
      1. Create dataset for ServiceNow component in 7.0.1 released Studio 2. Export this dataset 3. Launch 7.1.0-SNAPSHOT Studio 4. Import the dataset and try to create component using it (either drag and drop metadata or create component and then choose repository value) 5. Component properties are not set
    • All
    • Small

    Description

      Component properties are stored in repository using its relative path (keys) in Dataset/Datastore configuration. This path should be converted to absolute during component creation from metadata. This is required to know to which component property stored value corresponds to.

      This ticket is to make corresponding changes in Tacokit integration according changes done in https://jira.talendforge.org/browse/TCOMP-767 ("configuration" prefix was replaced with Dataset/Datastore name, thus correct handling for both cases should be supported to not break compatibility).

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              igonchar Ivan Gonchar
              Ivan Gonchar
              Ivan Gonchar
              Votes:
              0 Vote for this issue
              Watchers:
              2 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 days, 2 hours
                  3d 2h