Fixes: eod storage in hdb of tables not having sym column fails with
length error
#59
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
rdb
expects the column'sym
to be available in every table (this is also a constraint of thetickHF
so usually is not a problem).When using the
dist
component instead oftickHF
to publish to therdb
, tables without'sym
column break the eod write to thehdb
with a'length error
.The
.stor
library was prepared for that case and looks for a column'attrCol
for customisation of the column the table gets partitioned by.The rdb does not provide that column by default, so every table automatically defaults back to
'sym
.This PR fixes that issue and just enables you to pass the definition of the table, the
hdb
should partition by on eod indataflow.cfg