Bug 1009460
| Summary: | Keys are not imported by default when using dynamic VDB | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Data Virtualization 6 | Reporter: | Filip Elias <felias> |
| Component: | Teiid | Assignee: | Van Halbert <vhalbert> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.0.0 | CC: | ldimaggi, vhalbert |
| Target Milestone: | ER3 | ||
| Target Release: | 6.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-02-06 15:37:12 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Filip Elias
2013-09-18 13:50:36 UTC
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 |