Steven Hawkins <shawkins> made a comment on jira 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.

Steven Hawkins <shawkins> updated the status of jira TEIID-2667 to Resolved

Steven Hawkins <shawkins> made a comment on jira TEIID-2667

Resolved for 8.6.  Let me know when it can be committed to 8.4.x

Verified on DV6 ER3

Steven Hawkins <shawkins> updated the status of jira TEIID-2667 to Closed