- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-13-2016 11:57 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-14-2016 02:57 AM
Hi Komal,
Import set Table is not deleted automatically, admin needs to delete it manually if its not required.
Thanks,
Devi
PS: Hit like, Helpful or Correct depending on the impact of the response.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-02-2019 12:55 PM
This is not functional. Import data needs to be cleared before the next import, or import needs to coalesce just like a transform. I can not find options for either of these, so my import table becomes an absolute bloated mess with questionable results and degrading performance. How can this be corrected?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-07-2019 02:07 PM
Hi Yadin, I am also learning how import data set works with sys_data_source. Here is what I think how it works.
There are two tables keep track of the import data set. sys_import_set and your defined table for imported data (let's name it u_import_data_table). For each data import job, a unique entry is created in the sys_import_set table; a bunch of data rows are inserted/updated in u_import_data_table. Each row in the u_import_data_table refers to the entry in sys_import_set table. So the system will be able to apply the correct portion of data based on this lookup by only apply the data rows with the desired sys_import_set number.
I think the data in the u_import_data_table is not useful after they are processed(mapped) to the target table. You can truncate it using script after each import job. But without truncating, the whole thing should still work.