[JBoss JIRA] (TEIID-1944) After changing model to replace primary key with a unique key, the deployment of the vdb errors saying PrimaryKey does not exist
4:50 p.m.
Van Halbert created TEIID-1944:
----------------------------------
Summary: After changing model to replace primary key with a unique key, the
deployment of the vdb errors saying PrimaryKey does not exist
Key: TEIID-1944
URL: https://issues.jboss.org/browse/TEIID-1944
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 7.4.1
Reporter: Van Halbert
Assignee: Steven Hawkins
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
4:50 p.m.
[
https://issues.jboss.org/browse/TEIID-1944?page=com.atlassian.jira.plugin...
]
Van Halbert updated TEIID-1944:
-------------------------------
Attachment: server.log
dummy-ds.xml
Trade.vdb
After changing model to replace primary key with a unique key, the
deployment of the vdb errors saying PrimaryKey does not exist
--------------------------------------------------------------------------------------------------------------------------------
Key: TEIID-1944
URL: https://issues.jboss.org/browse/TEIID-1944
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 7.4.1
Reporter: Van Halbert
Assignee: Steven Hawkins
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
9:38 a.m.
New subject: [JBoss JIRA] (TEIID-1946) After changing model to replace primary key with a unique key, the deployment of the vdb errors saying PrimaryKey does not exist
[
https://issues.jboss.org/browse/TEIID-1946?page=com.atlassian.jira.plugin...
]
Steven Hawkins moved TEIIDDES-1246 to TEIID-1946:
-------------------------------------------------
Project: Teiid (was: Teiid Designer)
Key: TEIID-1946 (was: TEIIDDES-1246)
Affects Version/s: 7.4
(was: 7.4)
Component/s: Query Engine
(was: Modeling)
After changing model to replace primary key with a unique key, the
deployment of the vdb errors saying PrimaryKey does not exist
--------------------------------------------------------------------------------------------------------------------------------
Key: TEIID-1946
URL: https://issues.jboss.org/browse/TEIID-1946
Project: Teiid
Issue Type: Bug
Components: Query Engine
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
9:40 a.m.
New subject: [JBoss JIRA] (TEIID-1946) After changing model to replace primary key with a unique key, the deployment of the vdb errors saying PrimaryKey does not exist
[
https://issues.jboss.org/browse/TEIID-1946?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1946:
---------------------------------------
From a quick scan of the mmx logic I believe that we did allow this
and it has been part of the SQL spec for quite a while, so we should support it on the
server side as well.
After changing model to replace primary key with a unique key, the
deployment of the vdb errors saying PrimaryKey does not exist
--------------------------------------------------------------------------------------------------------------------------------
Key: TEIID-1946
URL: https://issues.jboss.org/browse/TEIID-1946
Project: Teiid
Issue Type: Bug
Components: Query Engine
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
12:47 p.m.
New subject: [JBoss JIRA] (TEIID-1946) After changing model to replace primary key with a unique key, the deployment of the vdb errors saying PrimaryKey does not exist
[
https://issues.jboss.org/browse/TEIID-1946?page=com.atlassian.jira.plugin...
]
Steven Hawkins reassigned TEIID-1946:
-------------------------------------
Assignee: Steven Hawkins
After changing model to replace primary key with a unique key, the
deployment of the vdb errors saying PrimaryKey does not exist
--------------------------------------------------------------------------------------------------------------------------------
Key: TEIID-1946
URL: https://issues.jboss.org/browse/TEIID-1946
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.4
Reporter: Van Halbert
Assignee: Steven Hawkins
Fix For: 7.7
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
12:47 p.m.
New subject: [JBoss JIRA] (TEIID-1946) After changing model to replace primary key with a unique key, the deployment of the vdb errors saying PrimaryKey does not exist
[
https://issues.jboss.org/browse/TEIID-1946?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-1946.
-----------------------------------
Fix Version/s: 7.7
Resolution: Done
Updated the index and dynamic vdb logic to allow unique constraints to be referenced by
foreign keys.
Also updated the dynamic JDBC logic to use unique indexes if they exist and to optionally
(enabled by default) to create a unique constraint if the foreign key references columns
that do not match the fk. This is needed since getting unique constraint information
through JDBC is spotty - such is the case with Teiid itself. Teiid is not very well
defined in differentiating between unique indexes and unique constraints. As such we don
not report unique constraints through our DatabaseMetadata for getIndexInfo.
Also corrected the index/key logic that was retrieving multiple copies, since the table
map contained two entries for each table.
After changing model to replace primary key with a unique key, the
deployment of the vdb errors saying PrimaryKey does not exist
--------------------------------------------------------------------------------------------------------------------------------
Key: TEIID-1946
URL: https://issues.jboss.org/browse/TEIID-1946
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.4
Reporter: Van Halbert
Fix For: 7.7
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
7:15 a.m.
New subject: [JBoss JIRA] (TEIID-1946) After changing model to replace primary key with a unique key, the deployment of the vdb errors saying PrimaryKey does not exist
[
https://issues.jboss.org/browse/TEIID-1946?page=com.atlassian.jira.plugin...
]
Steven Hawkins closed TEIID-1946.
---------------------------------
After changing model to replace primary key with a unique key, the
deployment of the vdb errors saying PrimaryKey does not exist
--------------------------------------------------------------------------------------------------------------------------------
Key: TEIID-1946
URL: https://issues.jboss.org/browse/TEIID-1946
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.4
Reporter: Van Halbert
Assignee: Steven Hawkins
Fix For: 7.7
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
4514
days inactive
4700
days old
6 comments
2 participants
participants (2)
-
Steven Hawkins (JIRA) -
Van Halbert (JIRA)