August 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4210) Allow limits to apply to the final sort pass

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4210?page=com.atlassian.jira.plugin... ] Steven Hawkins reopened TEIID-4210: ----------------------------------- There is an issue when only the offset is specified. > Allow limits to apply to the final sort pass > -------------------------------------------- > > Key: TEIID-4210 > URL: https://issues.jboss.org/browse/TEIID-4210 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > A left over todo was to support allowing the affect of limiting to short circuit the last sort phase. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4374) Procedure missing for an OData metadata request to a Swagger VDB

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4374?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4374: ------------------------------------- > are you saying I should create a wrapper that includes the parameters and the body? What are the semantics for this? No, with simple parameters Teiid will do necessary conversions to call the Swagger service. As a user you need focus on the executing with SQL interface exposed. Only in the case where BODY parameter is projected as CLOB, then you would need to build the target input document according to the Swagger schema defined then pass through the SQL interface. > How would you distinguish between path and query parameters? You don't, Teiid is providing a abstraction layer to swagger service in relational database terms, in this case as a stored procedure. > Is it then the responsibility of your code (the Swagger translator) Yes, it is swagger translator which converts to final form. >the Teiid OData interface code to unwrap this? OData interface is built on top of the SQL interface exposed by Teiid. If the procedure is exposed as "Action", then it is ALWAYS a POST call. Then you need to follow the metadata of the OData interface to execute that call. With the POST the only way to send parameters is in BODY. But do not confuse this with Swagger service definition, you need to follow the OData metadata here. If this is exposed as "Function" then it is GET call. > Procedure missing for an OData metadata request to a Swagger VDB > ---------------------------------------------------------------- > > Key: TEIID-4374 > URL: https://issues.jboss.org/browse/TEIID-4374 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 9.0, 9.0.1, 9.0.2 > Environment: Windows 10 Pro x64 > Java 8 > Reporter: Van Dillon > Assignee: Ramesh Reddy > Labels: Beta1 > Fix For: 9.1 > > Attachments: resource-adapter-rhq.xml, rhq-metadata.xml, rhq-vdb.xml, swagger.json > > > When a REST PUT path defined in Swagger has a path parameter and a body it does not appear in OData metadata. > See the attached swagger.json for an example. The operation 'executeOperation' does not appear in OData metadata. > The code that determines if a procedure is allowed is in: > org.teiid.olingo.service.ODataSchemaBuilder.allowedProcedure() > The comment seems to indicate that as long as there is only a single LOB, multiple 'in' parameters are allowed. But the actual code does not allow any other 'in' parameters if there is a LOB parameter. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4374) Procedure missing for an OData metadata request to a Swagger VDB

by Van Dillon (JIRA)

[ https://issues.jboss.org/browse/TEIID-4374?page=com.atlassian.jira.plugin... ] Van Dillon edited comment on TEIID-4374 at 8/13/16 12:47 PM: ------------------------------------------------------------- Thanks for the help on this Ramesh. I suspected this wasn't a really bug. But I thought someone probably had a workaround. I'm not sure I fully understand the workaround you mention. If I'm trying to use an existing REST service (like RHQ) that has PUT operations with both input parameters (path, query, a mix) and a body (like the executeOperation operation); are you saying I should create a wrapper that includes the parameters and the body? What are the semantics for this? Do you just include the parameters as: [parameter name]=value How would you distinguish between path and query parameters? Is it then the responsibility of your code (the Swagger translator) or the Teiid OData interface code to unwrap this? Or does the OData implementation know how to unwrap it? The new dependency on apache.common.io comes from SwaggerParser. If you call read(String), it uses Swagger20Parser to load the file with org.apache.commons.io.FileUtils. was (Author: evdillon): Thanks for the help on this Ramesh. I suspected this wasn't a really bug. But I thought someone probably had a workaround. If we pass parameters in the body, is there any way to distinguish between path and query types? The new dependency on apache.common.io comes from SwaggerParser. If you call read(String), it uses Swagger20Parser to load the file with org.apache.commons.io.FileUtils. > Procedure missing for an OData metadata request to a Swagger VDB > ---------------------------------------------------------------- > > Key: TEIID-4374 > URL: https://issues.jboss.org/browse/TEIID-4374 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 9.0, 9.0.1, 9.0.2 > Environment: Windows 10 Pro x64 > Java 8 > Reporter: Van Dillon > Assignee: Ramesh Reddy > Labels: Beta1 > Fix For: 9.1 > > Attachments: resource-adapter-rhq.xml, rhq-metadata.xml, rhq-vdb.xml, swagger.json > > > When a REST PUT path defined in Swagger has a path parameter and a body it does not appear in OData metadata. > See the attached swagger.json for an example. The operation 'executeOperation' does not appear in OData metadata. > The code that determines if a procedure is allowed is in: > org.teiid.olingo.service.ODataSchemaBuilder.allowedProcedure() > The comment seems to indicate that as long as there is only a single LOB, multiple 'in' parameters are allowed. But the actual code does not allow any other 'in' parameters if there is a LOB parameter. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4382) array_agg does not properly handle array values

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4382?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4382. ----------------------------------- Resolution: Done Unwrapped the array value. > array_agg does not properly handle array values > ----------------------------------------------- > > Key: TEIID-4382 > URL: https://issues.jboss.org/browse/TEIID-4382 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.12 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1 > > > array_agg(array value) - will fail to create the expected multi-dimensional array value as the ArrayAgg logic does not properly unnest the ArrayImpl values. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4374) Procedure missing for an OData metadata request to a Swagger VDB

by Van Dillon (JIRA)

[ https://issues.jboss.org/browse/TEIID-4374?page=com.atlassian.jira.plugin... ] Van Dillon commented on TEIID-4374: ----------------------------------- Thanks for the help on this Ramesh. I suspected this wasn't a really bug. But I thought someone probably had a workaround. If we pass parameters in the body, is there any way to distinguish between path and query types? The new dependency on apache.common.io comes from SwaggerParser. If you call read(String), it uses Swagger20Parser to load the file with org.apache.commons.io.FileUtils. > Procedure missing for an OData metadata request to a Swagger VDB > ---------------------------------------------------------------- > > Key: TEIID-4374 > URL: https://issues.jboss.org/browse/TEIID-4374 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 9.0, 9.0.1, 9.0.2 > Environment: Windows 10 Pro x64 > Java 8 > Reporter: Van Dillon > Assignee: Ramesh Reddy > Labels: Beta1 > Fix For: 9.1 > > Attachments: resource-adapter-rhq.xml, rhq-metadata.xml, rhq-vdb.xml, swagger.json > > > When a REST PUT path defined in Swagger has a path parameter and a body it does not appear in OData metadata. > See the attached swagger.json for an example. The operation 'executeOperation' does not appear in OData metadata. > The code that determines if a procedure is allowed is in: > org.teiid.olingo.service.ODataSchemaBuilder.allowedProcedure() > The comment seems to indicate that as long as there is only a single LOB, multiple 'in' parameters are allowed. But the actual code does not allow any other 'in' parameters if there is a LOB parameter. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2578) add/remove schema elements

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2578?page=com.atlassian.jira.plugin... ] Ramesh Reddy edited comment on TEIID-2578 at 8/13/16 11:05 AM: --------------------------------------------------------------- The revised syntax would be {code} #create a data role CREATE ROLE <data-role> [WITH JAAS ROLE <string>(,<string>)*] #assign grants to data role GRANT ( SELECT | INSERT | UPDATE | DELETE | EXECUTE | LANGUAGE | ALTER | DROP | ALL PRIVILEGES | TEMPORARY TABLES ) ON ( DATABASE TABLE <schema-name>.<table-name> PROCEDURE <schema-name>.<proc-name> SCHEMA <schema-name> COLUMN <schema-name>.<table-name>.<col-name> [MASK [ORDER \d] <string-val> ] [CONDITION [CONSTRAINT] <string-val>] ) TO <data-role-name> {code} was (Author: rareddy): The revised syntax would be {code} #create a data role CREATE ROLE <data-role> [WITH JAAS ROLE <string>(,<string>)*] #assign grants to data role GRANT ( SELECT | INSERT | UPDATE | DELETE | EXECUTE | LANGUAGE | ALTER | DROP | ALL PRIVILEGES | TEMP TABLES ) ON ( DATABASE TABLE <schema-name>.<table-name> PROCEDURE <schema-name>.<proc-name> SCHEMA <schema-name> COLUMN <schema-name>.<table-name>.<col-name> [MASK [ORDER \d] <string-val> ] [CONDITION [CONSTRAINT] <string-val>] ) TO <data-role-name> {code} > add/remove schema elements > -------------------------- > > Key: TEIID-2578 > URL: https://issues.jboss.org/browse/TEIID-2578 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 9.1 > > > Schemas are currently static after load. Modifications can only happen with restarts or new versions. We should allow add/drop at runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2578) add/remove schema elements

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2578?page=com.atlassian.jira.plugin... ] Ramesh Reddy edited comment on TEIID-2578 at 8/13/16 10:12 AM: --------------------------------------------------------------- The revised syntax would be {code} #create a data role CREATE ROLE <data-role> [WITH JAAS ROLE <string>(,<string>)*] #assign grants to data role GRANT ( SELECT | INSERT | UPDATE | DELETE | EXECUTE | LANGUAGE | ALTER | DROP | ALL PRIVILEGES | TEMP TABLES ) ON ( DATABASE TABLE <schema-name>.<table-name> PROCEDURE <schema-name>.<proc-name> SCHEMA <schema-name> COLUMN <schema-name>.<table-name>.<col-name> [MASK [ORDER \d] <string-val> ] [CONDITION [CONSTRAINT] <string-val>] ) TO <data-role-name> {code} was (Author: rareddy): The revised syntax would be {code} #create a data role CREATE DATA ROLE <data-role> [WITH JAAS ROLE <string>(,<string>)*] #assign grants to data role GRANT ( SELECT | INSERT | UPDATE | DELETE | EXECUTE | LANGUAGE | ALTER | DROP | ALL PRIVILEGES | TEMP TABLES ) ON ( DATABASE TABLE <schema-name>.<table-name> PROCEDURE <schema-name>.<proc-name> SCHEMA <schema-name> COLUMN <schema-name>.<table-name>.<col-name> [MASK [ORDER \d] <string-val> ] [CONDITION [CONSTRAINT] <string-val>] ) TO <data-role-name> {code} > add/remove schema elements > -------------------------- > > Key: TEIID-2578 > URL: https://issues.jboss.org/browse/TEIID-2578 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 9.1 > > > Schemas are currently static after load. Modifications can only happen with restarts or new versions. We should allow add/drop at runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4383) Add teiid javadocs and supplemental api documentation

by Kylin Soong (JIRA)

Kylin Soong created TEIID-4383: ---------------------------------- Summary: Add teiid javadocs and supplemental api documentation Key: TEIID-4383 URL: https://issues.jboss.org/browse/TEIID-4383 Project: Teiid Issue Type: Sub-task Components: Embedded Reporter: Kylin Soong Assignee: Kylin Soong We can use maven-javadoc-plugin to generate javadoc, [1] can be a example, reference code repo [2] [1] https://wildfly-swarm.github.io/wildfly-swarm-javadocs/2016.7-SNAPSHOT/ap... [2] https://github.com/wildfly-swarm/wildfly-swarm/blob/master/public-javadoc... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4353) Create a teiid feature pack

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-4353?page=com.atlassian.jira.plugin... ] Kylin Soong commented on TEIID-4353: ------------------------------------ [1] is wildly-teiid-feature-pack, which expand the teiid-parent, add some of teiid dependencies which not referred in teiid-parent pom, and other transitive dependencies which assembly plugin can solved but wildfly-feature-pack-build-maven-plugin can not. wildfly-feature-pack-build-maven-plugin is the plugin used to build the feature pack zip. [1] https://github.com/kylinsoong/wildfly-swarm-teiid/tree/master/feature-pack > Create a teiid feature pack > --------------------------- > > Key: TEIID-4353 > URL: https://issues.jboss.org/browse/TEIID-4353 > Project: Teiid > Issue Type: Sub-task > Components: Embedded > Affects Versions: 9.x > Reporter: Kylin Soong > Assignee: Kylin Soong > Fix For: 9.2 > > > Seems feature pack are necessary to build swarm jar, as below > * wildfly-feature-pack - https://github.com/wildfly/wildfly/tree/master/feature-pack > * wildfly-servlet-feature-pack - https://github.com/wildfly/wildfly/tree/master/servlet-feature-pack > * wildfly-core-feature-pack - https://github.com/wildfly/wildfly-core/tree/master/core-feature-pack > * wildfly-camel-feature-pack - https://mvnrepository.com/artifact/org.wildfly.camel/wildfly-camel-featur... > The feature pack contain the module structures, be used in swarm to build modules in swarm jar, above feature packs are frequently used in wildfly swarm, so far, base on my investigate, it seems a teiid feature pack are necessary to develop wildfly-swarm-teiid. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4185) Add more documentation about Embedded

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-4185?page=com.atlassian.jira.plugin... ] Kylin Soong commented on TEIID-4185: ------------------------------------ First version of swarm teiid now completed 90%, a simple portfolio example can wrok fine. > Add more documentation about Embedded > ------------------------------------- > > Key: TEIID-4185 > URL: https://issues.jboss.org/browse/TEIID-4185 > Project: Teiid > Issue Type: Task > Components: Documentation, Embedded > Affects Versions: 9.x > Reporter: Kylin Soong > Assignee: Kylin Soong > Fix For: 9.x > > > [1] is some document related with Teiid embedded, but we need more or enhance to make the Embedded production ready. > [1] https://teiid.gitbooks.io/documents/content/embedded/Embedded_Guide.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2016