Destination Improvement: Burst file name collition
Answered
Sometimes we read from one source table and writes to multiple target tables by renaming table names with TableProperties actions. When we use burst table in this setup HVR will create one burst table per target table. The burst table name is based on the source table name and will create only one common burst table for all the target tables. Then we have a situation where the target tables are fighting over the same burst table when they should have there own separate burst table. A possible solution could be to inspire the burst table name by the target table catalog, schema and name.
-
Hi Erlend,
Thank you for your suggestion.
The burst table name has always been based on the table name in HVR. The main reason is that we add at least three but up to four characters to the table name (when we need burst external tables) to the table name. Adding characters can result in the table name exceeding limits. Our naming strategy takes this into account.
In HVR 6.2 we introduced the option to assign a burst schema name (https://fivetran.com/docs/hvr6/action-reference/dbobjectgeneration#bursttableschema). Please use this option to avoid burst table name clashes.
Hope this helps.
Mark.
Please sign in to leave a comment.
Comments
1 comment