[
https://issues.jboss.org/browse/TEIIDDES-1164?page=com.atlassian.jira.plu...
]
Steven Hawkins commented on TEIIDDES-1164:
------------------------------------------
You are defaulting table cardinality to 0 to mean unknown, when 0 is actually a valid
value. So if you change the model default to -1, then you would also change the
RuntimeAdapter index version to the next number, which I believe should be 10 to let the
engine know that prior versions with the 0 value should still be treated as unknown.
CLONE - Index metadata should not treat cardinality 0 as unknown
----------------------------------------------------------------
Key: TEIIDDES-1164
URL:
https://issues.jboss.org/browse/TEIIDDES-1164
Project: Teiid Designer
Issue Type: Quality Risk
Components: Teiid Integration
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Assignee: Paul Richardson
Fix For: 8.1
The default cardinality is currently 0, which is treated as unknown, however it would be
better if the default were something like -1 instead. This will require introducing a new
index file version (so that older vdbs with a value of 0 can be understood as meaning
unknown) and updating the teiid/designer metadata defaults for cardinality as -1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira