Dashboard Improvement: Increase the characters length for Channel Names
Now, HVR allows only 12 characters to define a channel. Our organization has high standards for naming conventions. 12 characters is not enough to explain the source of the channel, the target of the channel and something about the channel itself.
For example, we process files through HVR
Source-three characters
Target-two characters
Seperator - two characters
Identify first channel or second channel -one character
Remaining four characters is not sufficient enough to explain about the file itself.
We have to rely on the channel description to get details about the files now.
Expanding the characters in channel name will be helpful.
Thanks!
-
Hi Blessy,
Historically channel names have been quite short. The reason is because we use the channel name as part of the state tables in the destination database (or source in case of trigger-based capture).
Customers commonly consolidate data from multiple sources we have to be careful state table names are unique.
And we want HVR to be as generic as possible across many source and destination technologies. Some databases (historically) support table names of only up to 30 characters.
The state table name consists of:
- hvr_ prefix (4 characters)
- ib, is, ic or rr depending on the type of table (see https://fivetran.com/docs/hvr6/internal-objects/objects-inside-database-locations) (2 characters)
- channel name (up to 12 characters)
- location name (up to 12 characters)
With the "imposed" limit of 30 characters total we cannot really widen the channel name. If we shorten the prefix we increase the likelihood of name clashes with user tables (and anyway there is not much to gain). And we don't want to shorten location names either.
Hope this clarifies. Please do note we provide a channel description. Can you use that for a longer channel name and/or description in free format?
Thank you,
Mark.
Please sign in to leave a comment.
Comments
1 comment