[JBoss JIRA] (TEIID-2832) Lower level denials still enforced with multiple roles
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2832:
-------------------------------------
Summary: Lower level denials still enforced with multiple roles
Key: TEIID-2832
URL: https://issues.jboss.org/browse/TEIID-2832
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.7
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Critical
Fix For: 8.7
If a role grants read all to schema A and another role also grants read all to schema A, but denies access to A.tbl, then the combination of these roles currently still denies access to A.tbl. It should result in granting access.
--
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
10 years, 3 months
[JBoss JIRA] (TEIID-2830) One-2-One mappiing in MongoDB should not require PK on child table
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2830?page=com.atlassian.jira.plugin... ]
Ramesh Reddy updated TEIID-2830:
--------------------------------
Fix Version/s: 8.7
> One-2-One mappiing in MongoDB should not require PK on child table
> ------------------------------------------------------------------
>
> Key: TEIID-2830
> URL: https://issues.jboss.org/browse/TEIID-2830
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.4
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 8.7
>
>
> A schema like
> {code}
> CREATE FOREIGN TABLE Customer (
> CustomerId integer PRIMARY KEY,
> FirstName varchar(25),
> LastName varchar(25),
> ) OPTIONS(UPDATABLE 'TRUE');
>
> CREATE FOREIGN TABLE Address (
> CustomerId integer,
> Street varchar(50),
> City varchar(25),
> State varchar(25),
> Zipcode varchar(6),
> FOREIGN KEY (CustomerId) REFERENCES Customer (CustomerId),
> ) OPTIONS(UPDATABLE 'TRUE', teiid_mongo:MERGE 'Customer');
> {code}
> will fail on second insert with NPE for lack of PK on the Address table
> {code}
> insert into Customer (customer_id ,first_name,last_name) values ('1002','Syed','Iqbal');
> insert into Address (customer_id,street,city,state,zipcode) values ('1002','123 Main St','Chicago','IL','60659');
> {code}
> the Exception is
> {code}
> 09:38:53,250 ERROR [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue11) 70p5084MEtHx Connector worker process failed for atomic-request=70p5084MEtHx.0.0.3: java.lang.NullPointerException
> at org.teiid.translator.mongodb.MongoDocument.buildMergeKey(MongoDocument.java:252)
> at org.teiid.translator.mongodb.MongoDocument.build(MongoDocument.java:143)
> at org.teiid.translator.mongodb.MongoDocument.<init>(MongoDocument.java:64)
> at org.teiid.translator.mongodb.MongoDBSelectVisitor.visit(MongoDBSelectVisitor.java:400)
> at org.teiid.language.NamedTable.acceptVisitor(NamedTable.java:66) [teiid-api-8.7.0.Alpha2-SNAPSHOT.jar:8.7.0.Alpha2-SNAPSHOT]
> at org.teiid.language.visitor.AbstractLanguageVisitor.visitNode(AbstractLanguageVisitor.java:51) [teiid-api-8.7.0.Alpha2-SNAPSHOT.jar:8.7.0.Alpha2-SNAPSHOT]
> at org.teiid.translator.mongodb.MongoDBSelectVisitor.append(MongoDBSelectVisitor.java:95)
> at org.teiid.translator.mongodb.MongoDBUpdateVisitor.visit(MongoDBUpdateVisitor.java:59)
> at org.teiid.language.Insert.acceptVisitor(Insert.java:57) [teiid-api-8.7.0.Alpha2-SNAPSHOT.jar:8.7.0.Alpha2-SNAPSHOT]
> {code}
--
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
10 years, 3 months
[JBoss JIRA] (TEIID-2830) One-2-One mappiing in MongoDB should not require PK on child table
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-2830:
-----------------------------------
Summary: One-2-One mappiing in MongoDB should not require PK on child table
Key: TEIID-2830
URL: https://issues.jboss.org/browse/TEIID-2830
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 8.4
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
A schema like
{code}
CREATE FOREIGN TABLE Customer (
CustomerId integer PRIMARY KEY,
FirstName varchar(25),
LastName varchar(25),
) OPTIONS(UPDATABLE 'TRUE');
CREATE FOREIGN TABLE Address (
CustomerId integer,
Street varchar(50),
City varchar(25),
State varchar(25),
Zipcode varchar(6),
FOREIGN KEY (CustomerId) REFERENCES Customer (CustomerId),
) OPTIONS(UPDATABLE 'TRUE', teiid_mongo:MERGE 'Customer');
{code}
will fail on second insert with NPE for lack of PK on the Address table
{code}
insert into Customer (customer_id ,first_name,last_name) values ('1002','Syed','Iqbal');
insert into Address (customer_id,street,city,state,zipcode) values ('1002','123 Main St','Chicago','IL','60659');
{code}
the Exception is
{code}
09:38:53,250 ERROR [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue11) 70p5084MEtHx Connector worker process failed for atomic-request=70p5084MEtHx.0.0.3: java.lang.NullPointerException
at org.teiid.translator.mongodb.MongoDocument.buildMergeKey(MongoDocument.java:252)
at org.teiid.translator.mongodb.MongoDocument.build(MongoDocument.java:143)
at org.teiid.translator.mongodb.MongoDocument.<init>(MongoDocument.java:64)
at org.teiid.translator.mongodb.MongoDBSelectVisitor.visit(MongoDBSelectVisitor.java:400)
at org.teiid.language.NamedTable.acceptVisitor(NamedTable.java:66) [teiid-api-8.7.0.Alpha2-SNAPSHOT.jar:8.7.0.Alpha2-SNAPSHOT]
at org.teiid.language.visitor.AbstractLanguageVisitor.visitNode(AbstractLanguageVisitor.java:51) [teiid-api-8.7.0.Alpha2-SNAPSHOT.jar:8.7.0.Alpha2-SNAPSHOT]
at org.teiid.translator.mongodb.MongoDBSelectVisitor.append(MongoDBSelectVisitor.java:95)
at org.teiid.translator.mongodb.MongoDBUpdateVisitor.visit(MongoDBUpdateVisitor.java:59)
at org.teiid.language.Insert.acceptVisitor(Insert.java:57) [teiid-api-8.7.0.Alpha2-SNAPSHOT.jar:8.7.0.Alpha2-SNAPSHOT]
{code}
--
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
10 years, 3 months
[JBoss JIRA] (TEIID-2828) ResteasyEnabler fails with OTHER model types
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2828?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2828.
-----------------------------------
Resolution: Done
updated the handling to account for model entries without a corresponding schema.
> ResteasyEnabler fails with OTHER model types
> --------------------------------------------
>
> Key: TEIID-2828
> URL: https://issues.jboss.org/browse/TEIID-2828
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.4
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.7
>
>
> If a vdb contains OTHER type models (typically used for .xsd), then the schema lookup will produce a null and result in an NPE:
> java.lang.NullPointerException
> at org.teiid.jboss.rest.ResteasyEnabler.hasRestMetadata(ResteasyEnabler.java:146) [teiid-jboss-integration-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at org.teiid.jboss.rest.ResteasyEnabler.finishedDeployment(ResteasyEnabler.java:81) [teiid-jboss-integration-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at org.teiid.deployers.VDBRepository.notifyFinished(VDBRepository.java:351) [teiid-runtime-8.4.1-redhat-2.jar:8.4.1-redhat-2]
>
--
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
10 years, 3 months
[JBoss JIRA] (TEIID-2829) While importing from Deployed BQT2 VDB, JDBC type of 0 and type name NULL was returned for column with design-time type varbinary
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIID-2829?page=com.atlassian.jira.plugin... ]
Barry LaFond updated TEIID-2829:
--------------------------------
Description:
1) Open attached project in Designer
2) Deploy the BQT2.vdb
3) Create another project
4) Import the VDB metadata via JDBC Importer into your second project (will end up being a read-only VDB source model)
5) On *finish* you'll get an exception when processing the type_varbinary column because the type returned is "0" and type name of "null"
{code}
java.lang.IllegalArgumentException: Expected argument to be non-null but got null
at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:142)
at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:128)
at org.teiid.designer.sdt.types.BuiltInTypesManager.getBuiltInDatatype(BuiltInTypesManager.java:477)
at org.teiid.designer.sdt.types.WorkspaceDatatypeManager.getBuiltInDatatype(WorkspaceDatatypeManager.java:94)
at org.teiid.designer.jdbc.relational.impl.RelationalModelProcessorImpl.findType(RelationalModelProcessorImpl.java:1450)
at org.teiid.designer.jdbc.relational.impl.RelationalModelProcessorImpl.setColumnInfo(RelationalModelProcessorImpl.java:1321)
{code}
was:
1) Open attached project in Designer
2) Deploy the BQT2.vdb
3) Import the VDB metadata via JDBC Importer
4) On finish you'll get an exception when processing the type_varbinary column because the type returned is "0" and type name of "null"
{code}
java.lang.IllegalArgumentException: Expected argument to be non-null but got null
at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:142)
at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:128)
at org.teiid.designer.sdt.types.BuiltInTypesManager.getBuiltInDatatype(BuiltInTypesManager.java:477)
at org.teiid.designer.sdt.types.WorkspaceDatatypeManager.getBuiltInDatatype(WorkspaceDatatypeManager.java:94)
at org.teiid.designer.jdbc.relational.impl.RelationalModelProcessorImpl.findType(RelationalModelProcessorImpl.java:1450)
at org.teiid.designer.jdbc.relational.impl.RelationalModelProcessorImpl.setColumnInfo(RelationalModelProcessorImpl.java:1321)
{code}
> While importing from Deployed BQT2 VDB, JDBC type of 0 and type name NULL was returned for column with design-time type varbinary
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIID-2829
> URL: https://issues.jboss.org/browse/TEIID-2829
> Project: Teiid
> Issue Type: Bug
> Reporter: Barry LaFond
> Assignee: Steven Hawkins
> Attachments: TEIID_2829_project.zip
>
>
> 1) Open attached project in Designer
> 2) Deploy the BQT2.vdb
> 3) Create another project
> 4) Import the VDB metadata via JDBC Importer into your second project (will end up being a read-only VDB source model)
> 5) On *finish* you'll get an exception when processing the type_varbinary column because the type returned is "0" and type name of "null"
> {code}
> java.lang.IllegalArgumentException: Expected argument to be non-null but got null
> at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:142)
> at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:128)
> at org.teiid.designer.sdt.types.BuiltInTypesManager.getBuiltInDatatype(BuiltInTypesManager.java:477)
> at org.teiid.designer.sdt.types.WorkspaceDatatypeManager.getBuiltInDatatype(WorkspaceDatatypeManager.java:94)
> at org.teiid.designer.jdbc.relational.impl.RelationalModelProcessorImpl.findType(RelationalModelProcessorImpl.java:1450)
> at org.teiid.designer.jdbc.relational.impl.RelationalModelProcessorImpl.setColumnInfo(RelationalModelProcessorImpl.java:1321)
> {code}
--
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
10 years, 3 months
[JBoss JIRA] (TEIID-2829) While importing from Deployed BQT2 VDB, JDBC type of 0 and type name NULL was returned for column with design-time type varbinary
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIID-2829?page=com.atlassian.jira.plugin... ]
Barry LaFond updated TEIID-2829:
--------------------------------
Attachment: TEIID_2829_project.zip
> While importing from Deployed BQT2 VDB, JDBC type of 0 and type name NULL was returned for column with design-time type varbinary
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIID-2829
> URL: https://issues.jboss.org/browse/TEIID-2829
> Project: Teiid
> Issue Type: Bug
> Reporter: Barry LaFond
> Assignee: Steven Hawkins
> Attachments: TEIID_2829_project.zip
>
>
> 1) Open attached project in Designer
> 2) Deploy the BQT2.vdb
> 3) Import the VDB metadata via JDBC Importer
> 4) On finish you'll get an exception when processing the type_varbinary column because the type returned is "0" and type name of "null"
> {code}
> java.lang.IllegalArgumentException: Expected argument to be non-null but got null
> at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:142)
> at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:128)
> at org.teiid.designer.sdt.types.BuiltInTypesManager.getBuiltInDatatype(BuiltInTypesManager.java:477)
> at org.teiid.designer.sdt.types.WorkspaceDatatypeManager.getBuiltInDatatype(WorkspaceDatatypeManager.java:94)
> at org.teiid.designer.jdbc.relational.impl.RelationalModelProcessorImpl.findType(RelationalModelProcessorImpl.java:1450)
> at org.teiid.designer.jdbc.relational.impl.RelationalModelProcessorImpl.setColumnInfo(RelationalModelProcessorImpl.java:1321)
> {code}
--
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
10 years, 3 months
[JBoss JIRA] (TEIID-2829) While importing from Deployed BQT2 VDB, JDBC type of 0 and type name NULL was returned for column with design-time type varbinary
by Barry LaFond (JIRA)
Barry LaFond created TEIID-2829:
-----------------------------------
Summary: While importing from Deployed BQT2 VDB, JDBC type of 0 and type name NULL was returned for column with design-time type varbinary
Key: TEIID-2829
URL: https://issues.jboss.org/browse/TEIID-2829
Project: Teiid
Issue Type: Bug
Reporter: Barry LaFond
Assignee: Steven Hawkins
1) Open attached project in Designer
2) Deploy the BQT2.vdb
3) Import the VDB metadata via JDBC Importer
4) On finish you'll get an exception when processing the type_varbinary column because the type returned is "0" and type name of "null"
{code}
java.lang.IllegalArgumentException: Expected argument to be non-null but got null
at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:142)
at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:128)
at org.teiid.designer.sdt.types.BuiltInTypesManager.getBuiltInDatatype(BuiltInTypesManager.java:477)
at org.teiid.designer.sdt.types.WorkspaceDatatypeManager.getBuiltInDatatype(WorkspaceDatatypeManager.java:94)
at org.teiid.designer.jdbc.relational.impl.RelationalModelProcessorImpl.findType(RelationalModelProcessorImpl.java:1450)
at org.teiid.designer.jdbc.relational.impl.RelationalModelProcessorImpl.setColumnInfo(RelationalModelProcessorImpl.java:1321)
{code}
--
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
10 years, 3 months
[JBoss JIRA] (TEIID-2827) Can the teiid object associated with where the problem is found be added to the error message
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2827?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2827.
-----------------------------------
Fix Version/s: 8.7
Resolution: Done
The processing of validation errors was not adding the object to the message, so that has been corrected. Also corrected the message string which always said view even for procedures.
I did not attempt to add too much other context just yet though.
> Can the teiid object associated with where the problem is found be added to the error message
> ---------------------------------------------------------------------------------------------
>
> Key: TEIID-2827
> URL: https://issues.jboss.org/browse/TEIID-2827
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.4.1
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Fix For: 8.7
>
> Attachments: createdb.sql, perf-vdb-postgres.xml
>
>
> Using the attached dynamic vdb, against the database that was created using the attached DDL, produces the following errors:
> ERROR: Element Perf.HISTORY."TIME" of history is neither nullable nor has a default value. A value must be specified in the insert.
> ERROR: Element Perf.HISTORY.FILL of history is neither nullable nor has a default value. A value must be specified in the insert.
> Because of these errors, the VDB isn't deployed.
> Not sure why these are not just WARNINGS.
--
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
10 years, 3 months