[ https://issues.jboss.org/browse/TEIID-2667?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2667: --------------------------------------- It looks like several of the documented properties do not match the defaults: importIndexes, importKeys, importProcedures and autoCreateUniqueConstraints is also missing from the doc page (added with TEIID-1946 and roughly corresponds to the designer option to import incomplete foreign keys). I believe we at one point were trying to mimic Designer's defaults as much as it made sense. At least having importProcedures/importIndexes defaulted as false is fine, so the doc should be changed for those. Since we don't split importKeys into primary/unique vs. foreign, having it defaulted to false doesn't make much sense. As long as autoCreateUniqueConstraints is true (the default) and given that we automatically ignore foreign keys to non-imported tables, then there's no chance that having importKeys set to true should result in invalid metadata. We would just want to document the switch in the actual default as a compatibility change if for whatever reason someone was relying on the current behavior. -- 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