[
https://issues.jboss.org/browse/TEIIDDES-1164?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-1164:
----------------------------------------
Steve, can you be more specific about what object in Designer needs default to -1? and
what/where is the "index version"?
Assuming it's versioning the Index Files?
I see a method in our RuntimeAdapter...
protected static void appendIndexVersion( final int indexVersion,
final StringBuffer sb ) {
// The range of index versions is [0,99]
CoreArgCheck.isTrue(indexVersion > -1 && indexVersion < 100,
"Index version " + indexVersion + " out of range. (0 - 99)");
//$NON-NLS-1$ //$NON-NLS-2$
sb.append(IndexConstants.RECORD_STRING.INDEX_VERSION_MARKER);
if (indexVersion < 10) {
sb.append(Integer.toString(0));
sb.append(Integer.toString(indexVersion));
} else {
sb.append(Integer.toString(indexVersion));
}
}
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