January 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2834) Use FunctionMethod metadata internally for built-in aggregates

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2834: ------------------------------------- Summary: Use FunctionMethod metadata internally for built-in aggregates Key: TEIID-2834 URL: https://issues.jboss.org/browse/TEIID-2834 Project: Teiid Issue Type: Task Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins With TEIID-2815 we added aggregate function definitions for consumption by designer, but it would be good to have them consistently handled internally. The metadata needs to accommodate count\(*) and textagg. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2815) Need to add the aggregate functions to list of supported functions, for Designer to expose for the user

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2815?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2815: --------------------------------------- Barry let me know if you get a chance to look at this in alpha2 or later. > Need to add the aggregate functions to list of supported functions, for Designer to expose for the user > ------------------------------------------------------------------------------------------------------- > > Key: TEIID-2815 > URL: https://issues.jboss.org/browse/TEIID-2815 > Project: Teiid > Issue Type: Enhancement > Components: Server > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > > Need to add to the list, of known supported functions, what are all the aggregate functions that are supported. This list is what Teiid Designer would expose to the user for modeling purposes. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2833) While importing from Deployed BQT2 VDB, JDBC type of 0 and type name NULL was returned for column with design-time type varbinary

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2833?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2833: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1060335 > 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-2833 > URL: https://issues.jboss.org/browse/TEIID-2833 > Project: Teiid > Issue Type: Bug > Reporter: Barry LaFond > Fix For: 8.7 > > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2833) While importing from Deployed BQT2 VDB, JDBC type of 0 and type name NULL was returned for column with design-time type varbinary

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2833?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2833. ----------------------------------- Fix Version/s: 8.7 Resolution: Done switched to using the same uuid as designer > 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-2833 > URL: https://issues.jboss.org/browse/TEIID-2833 > Project: Teiid > Issue Type: Bug > Reporter: Barry LaFond > Fix For: 8.7 > > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2833) While importing from Deployed BQT2 VDB, JDBC type of 0 and type name NULL was returned for column with design-time type varbinary

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2833?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2833: --------------------------------------- Moved back to Teiid to use a different uuid. I think the reason we are not throwing an exception in the first place when we can't find the type has to do with old user defined scenarios in which it seemed like the referenced datatype was not known. > 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-2833 > URL: https://issues.jboss.org/browse/TEIID-2833 > Project: Teiid > Issue Type: Bug > Reporter: Barry LaFond > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2833) While importing from Deployed BQT2 VDB, JDBC type of 0 and type name NULL was returned for column with design-time type varbinary

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2833?page=com.atlassian.jira.plugin... ] Steven Hawkins moved TEIIDDES-2038 to TEIID-2833: ------------------------------------------------- Project: Teiid (was: Teiid Designer) Key: TEIID-2833 (was: TEIIDDES-2038) > 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-2833 > URL: https://issues.jboss.org/browse/TEIID-2833 > Project: Teiid > Issue Type: Bug > Reporter: Barry LaFond > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2825) Add module packaging to each of the translator

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2825?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-2825: ------------------------------- Git Pull Request: https://github.com/teiid/teiid/pull/185 > Add module packaging to each of the translator > ---------------------------------------------- > > Key: TEIID-2825 > URL: https://issues.jboss.org/browse/TEIID-2825 > Project: Teiid > Issue Type: Sub-task > Components: Build/Kits > Affects Versions: 8.7 > Reporter: Van Halbert > Assignee: Van Halbert > > Add zip module packaging to each of the translators -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2832) Lower level denials still enforced with multiple roles

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2832?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2832. ----------------------------------- Resolution: Done Corrected the logic to look past the first denial in case access is granted by another role. > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2828) ResteasyEnabler fails with OTHER model types

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2828?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2828: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1059917 > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2832) Lower level denials still enforced with multiple roles

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2832?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2832: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1059908 > 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, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2014