[JBoss JIRA] (TEIIDDES-1246) After changing model to replace primary key with a unique key, the deployment of the vdb errors saying PrimaryKey does not exist
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1246?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1246:
----------------------------------------
1) I believe Designer has allowed FK references to UC's for as long as I remember, way back in MM days
2) Is this a new(er) limitation in the Server?
3) If not, and it's been allowed for 10 years, then to date, there hasn't been a customer who squawked back enough to log a Bug.
> After changing model to replace primary key with a unique key, the deployment of the vdb errors saying PrimaryKey does not exist
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1246
> URL: https://issues.jboss.org/browse/TEIIDDES-1246
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 7.4
> Reporter: Van Halbert
> Attachments: dummy-ds.xml, server.log, Trade.vdb
>
>
> In designer, I removed a primary key and replaced it with a unique key, and changed the foreign key to now reference the unique key, and all built with no errors. When deploying vdb to server, you see this exception (partial, see attachment for full log):
> Caused by: mmuuid:15f67b60-e387-4092-bbc5-0b7726585f52 PrimaryKey does not exist.
> at org.teiid.metadata.index.IndexMetadataFactory.getPrimaryKey(IndexMetadataFactory.java:353)
> at org.teiid.metadata.index.IndexMetadataFactory.getTables(IndexMetadataFactory.java:295)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] (TEIIDDES-1246) After changing model to replace primary key with a unique key, the deployment of the vdb errors saying PrimaryKey does not exist
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1246?page=com.atlassian.jira.plu... ]
Van Halbert commented on TEIIDDES-1246:
---------------------------------------
So this is a Teiid requirement (limitation) to only allow fks to reference a primary key. There are databases that support the referencing pks or unique keys. I would like to see the support for any unique key (IMO).
> After changing model to replace primary key with a unique key, the deployment of the vdb errors saying PrimaryKey does not exist
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1246
> URL: https://issues.jboss.org/browse/TEIIDDES-1246
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 7.4
> Reporter: Van Halbert
> Attachments: dummy-ds.xml, server.log, Trade.vdb
>
>
> In designer, I removed a primary key and replaced it with a unique key, and changed the foreign key to now reference the unique key, and all built with no errors. When deploying vdb to server, you see this exception (partial, see attachment for full log):
> Caused by: mmuuid:15f67b60-e387-4092-bbc5-0b7726585f52 PrimaryKey does not exist.
> at org.teiid.metadata.index.IndexMetadataFactory.getPrimaryKey(IndexMetadataFactory.java:353)
> at org.teiid.metadata.index.IndexMetadataFactory.getTables(IndexMetadataFactory.java:295)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] (TEIIDDES-1246) After changing model to replace primary key with a unique key, the deployment of the vdb errors saying PrimaryKey does not exist
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1246?page=com.atlassian.jira.plu... ]
Steven Hawkins commented on TEIIDDES-1246:
------------------------------------------
So then this is the second case, a unique constraint is standing-in for a primary key. That should not be allowed. fks can only reference primary keys.
> After changing model to replace primary key with a unique key, the deployment of the vdb errors saying PrimaryKey does not exist
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1246
> URL: https://issues.jboss.org/browse/TEIIDDES-1246
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 7.4
> Reporter: Van Halbert
> Attachments: dummy-ds.xml, server.log, Trade.vdb
>
>
> In designer, I removed a primary key and replaced it with a unique key, and changed the foreign key to now reference the unique key, and all built with no errors. When deploying vdb to server, you see this exception (partial, see attachment for full log):
> Caused by: mmuuid:15f67b60-e387-4092-bbc5-0b7726585f52 PrimaryKey does not exist.
> at org.teiid.metadata.index.IndexMetadataFactory.getPrimaryKey(IndexMetadataFactory.java:353)
> at org.teiid.metadata.index.IndexMetadataFactory.getTables(IndexMetadataFactory.java:295)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] (TEIIDDES-1246) After changing model to replace primary key with a unique key, the deployment of the vdb errors saying PrimaryKey does not exist
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1246?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1246:
----------------------------------------
Steve, I walked through the runtime adapter in debug and verified that the appropriate index code is being assigned to the keys:
PK = "K"
UC = "I"
FK = "J"
Also verified in my model that the UUID shown in the stack trace is the UUID ref from the Unique Constraint I set on the FK. It's NOT a reference to the PK that was deleted.
> After changing model to replace primary key with a unique key, the deployment of the vdb errors saying PrimaryKey does not exist
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1246
> URL: https://issues.jboss.org/browse/TEIIDDES-1246
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 7.4
> Reporter: Van Halbert
> Attachments: dummy-ds.xml, server.log, Trade.vdb
>
>
> In designer, I removed a primary key and replaced it with a unique key, and changed the foreign key to now reference the unique key, and all built with no errors. When deploying vdb to server, you see this exception (partial, see attachment for full log):
> Caused by: mmuuid:15f67b60-e387-4092-bbc5-0b7726585f52 PrimaryKey does not exist.
> at org.teiid.metadata.index.IndexMetadataFactory.getPrimaryKey(IndexMetadataFactory.java:353)
> at org.teiid.metadata.index.IndexMetadataFactory.getTables(IndexMetadataFactory.java:295)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] (TEIIDDES-1246) After changing model to replace primary key with a unique key, the deployment of the vdb errors saying PrimaryKey does not exist
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1246?page=com.atlassian.jira.plu... ]
Van Halbert commented on TEIIDDES-1246:
---------------------------------------
Barry verified the problem in his own modeling and looked at the model and said it looked ok (key type looked right). Hm, where to go from here?
> After changing model to replace primary key with a unique key, the deployment of the vdb errors saying PrimaryKey does not exist
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1246
> URL: https://issues.jboss.org/browse/TEIIDDES-1246
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 7.4
> Reporter: Van Halbert
> Attachments: dummy-ds.xml, server.log, Trade.vdb
>
>
> In designer, I removed a primary key and replaced it with a unique key, and changed the foreign key to now reference the unique key, and all built with no errors. When deploying vdb to server, you see this exception (partial, see attachment for full log):
> Caused by: mmuuid:15f67b60-e387-4092-bbc5-0b7726585f52 PrimaryKey does not exist.
> at org.teiid.metadata.index.IndexMetadataFactory.getPrimaryKey(IndexMetadataFactory.java:353)
> at org.teiid.metadata.index.IndexMetadataFactory.getTables(IndexMetadataFactory.java:295)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months