December 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3873) Need 8.x Release PDF documentation

by Surendhar T (JIRA)

Surendhar T created TEIID-3873: ---------------------------------- Summary: Need 8.x Release PDF documentation Key: TEIID-3873 URL: https://issues.jboss.org/browse/TEIID-3873 Project: Teiid Issue Type: Task Components: Documentation Reporter: Surendhar T Assignee: Steven Hawkins Priority: Blocker Need 8.x Release PDF documentation Reference Guide Developer's Guide Client Developer's Guide Admin Guide Caching Guide Quick Start Security Guide API Docs -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3872) Oracle Sequence error: Cannot infer EdmType for java type: oracle.sql.ROWID

by Ivan Lucas Vargas (JIRA)

Ivan Lucas Vargas created TEIID-3872: ---------------------------------------- Summary: Oracle Sequence error: Cannot infer EdmType for java type: oracle.sql.ROWID Key: TEIID-3872 URL: https://issues.jboss.org/browse/TEIID-3872 Project: Teiid Issue Type: Bug Environment: MacOS X El Capitan, Teiid 8.12.2, Jbossdev studio, Oracle 11g Reporter: Ivan Lucas Vargas Assignee: Steven Hawkins Forum thread: https://developer.jboss.org/message/947527 When trying to insert a record thru odata2 request when the ID field is mapped as an Oracle Sequence as described in the documentation as *<element name>:SEQUENCE=<sequence name>.<sequence value> *(https://docs.jboss.org/author/display/teiid812final/Oracle+Translator), the following error occurs: TEIID16013 Error occurred producing OData result.: java.lang.IllegalArgumentException: Cannot infer EdmType for java type: oracle.sql.ROWID at org.odata4j.core.OProperties.simple(OProperties.java:40) [odata-core-0.8.10.jar:0.8.10] at org.teiid.odata.ODataSQLBuilder.buildEntityKey(ODataSQLBuilder.java:678) [classes:] at org.teiid.odata.TeiidProducer.createEntity(TeiidProducer.java:232) [classes:] at org.odata4j.producer.resources.EntitiesRequestResource.createEntity(EntitiesRequestResource.java:129) [odata-core-0.8.10.jar:0.8.10] at org.odata4j.producer.resources.EntitiesRequestResource.createEntity(EntitiesRequestResource.java:116) [odata-core-0.8.10.jar:0.8.10] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_45] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_45] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_45] at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_45] at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:168) [resteasy-jaxrs-2.3.9.Final-redhat-7.jar:] at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:269) [resteasy-jaxrs-2.3.9.Final-redhat-7.jar:] at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227) [resteasy-jaxrs-2.3.9.Final-redhat-7.jar:] at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:216) [resteasy-jaxrs-2.3.9.Final-redhat-7.jar:] at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:541) [resteasy-jaxrs-2.3.9.Final-redhat-7.jar:] at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:523) [resteasy-jaxrs-2.3.9.Final-redhat-7.jar:] at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:125) [resteasy-jaxrs-2.3.9.Final-redhat-7.jar:] at org.teiid.odata.ODataServletContainerDispatcher.service(ODataServletContainerDispatcher.java:118) [classes:] at org.teiid.odata.ODataServlet.service(ODataServlet.java:65) [classes:] at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) [resteasy-jaxrs-2.3.9.Final-redhat-7.jar:] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.5.3.Final.jar:7.5.3.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.3.Final.jar:7.5.3.Final] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.5.3.Final.jar:7.5.3.Final] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.5.3.Final.jar:7.5.3.Final] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:512) [jbossweb-7.5.3.Final.jar:7.5.3.Final] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.5.0.Final-redhat-15.jar:7.5.0.Final-redhat-15] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:150) [jbossweb-7.5.3.Final.jar:7.5.3.Final] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.5.3.Final.jar:7.5.3.Final] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.5.3.Final.jar:7.5.3.Final] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:344) [jbossweb-7.5.3.Final.jar:7.5.3.Final] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:854) [jbossweb-7.5.3.Final.jar:7.5.3.Final] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.5.3.Final.jar:7.5.3.Final] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.5.3.Final.jar:7.5.3.Final] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_45] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3871) moving documentation from confluence to gitbook

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-3871?page=com.atlassian.jira.plugin... ] Kylin Soong commented on TEIID-3871: ------------------------------------ GitBook Documentation: https://help.gitbook.com/ > moving documentation from confluence to gitbook > ------------------------------------------------- > > Key: TEIID-3871 > URL: https://issues.jboss.org/browse/TEIID-3871 > Project: Teiid > Issue Type: Task > Components: Documentation > Affects Versions: 9.x > Reporter: Kylin Soong > Assignee: Kylin Soong > Fix For: 9.x > > > From Teiid DV 7 F2F Notes, > " In the Teiid 9.x timeframe we should look toward moving everything to gitbook / markdown. We should start by migrating the documentation and solicit help with the website if possible." > This issue will address this. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3871) moving documentation from confluence to gitbook

by Kylin Soong (JIRA)

Kylin Soong created TEIID-3871: ---------------------------------- Summary: moving documentation from confluence to gitbook Key: TEIID-3871 URL: https://issues.jboss.org/browse/TEIID-3871 Project: Teiid Issue Type: Task Components: Documentation Affects Versions: 9.x Reporter: Kylin Soong Assignee: Kylin Soong Fix For: 9.x >From Teiid DV 7 F2F Notes, " In the Teiid 9.x timeframe we should look toward moving everything to gitbook / markdown. We should start by migrating the documentation and solicit help with the website if possible." This issue will address this. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3870) Add ability to properly qualify package objects

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3870?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3870: ---------------------------------- Description: Even if the catalog name pattern matches package names, there is no option or recognition that contained procedures should be qualified as <package / catalog>.<name>. We need this because at least in Oracle, procedures may be encapsulated in Oracle Packages that are used as catalog names in the DatabaseMetaData. When trying to import these into Teiid, the "Name in Source" field does not allow me to specify the Package name, so I can't call those procedures. was: Add ability to fully qualify a database object's (tables/views/procedures/etc) "Name in Source" field with its package/catalog name. We need this because at least in Oracle, procedures may be encapsulated in Oracle Packages. When trying to import these into Teiid, the "Name in Source" field does not allow me to specify the Package name, so I can't call those procedures. Summary: Add ability to properly qualify package objects (was: Add ability to fully qualify an object with its package/catalog name) > Add ability to properly qualify package objects > ----------------------------------------------- > > Key: TEIID-3870 > URL: https://issues.jboss.org/browse/TEIID-3870 > Project: Teiid > Issue Type: Feature Request > Affects Versions: 8.7.1.6_2 > Environment: Red Hat JBoss Data Virtualization 6.2 on EAP6.4.0 patched to version 6.4.3, > JBoss Developer Studio 8.1.0GA with Teiid Designer plugin 9.0.3.Final.v20150810-1438-B1157 > 64-bit Windows 7 environment > Reporter: Steve Tran > Assignee: Steven Hawkins > Fix For: 8.12.4 > > > Even if the catalog name pattern matches package names, there is no option or recognition that contained procedures should be qualified as <package / catalog>.<name>. > We need this because at least in Oracle, procedures may be encapsulated in Oracle Packages that are used as catalog names in the DatabaseMetaData. When trying to import these into Teiid, the "Name in Source" field does not allow me to specify the Package name, so I can't call those procedures. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3870) Add ability to properly qualify package objects

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3870?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3870: ---------------------------------- Fix Version/s: 8.12.4 > Add ability to properly qualify package objects > ----------------------------------------------- > > Key: TEIID-3870 > URL: https://issues.jboss.org/browse/TEIID-3870 > Project: Teiid > Issue Type: Feature Request > Affects Versions: 8.7.1.6_2 > Environment: Red Hat JBoss Data Virtualization 6.2 on EAP6.4.0 patched to version 6.4.3, > JBoss Developer Studio 8.1.0GA with Teiid Designer plugin 9.0.3.Final.v20150810-1438-B1157 > 64-bit Windows 7 environment > Reporter: Steve Tran > Assignee: Steven Hawkins > Fix For: 8.12.4 > > > Even if the catalog name pattern matches package names, there is no option or recognition that contained procedures should be qualified as <package / catalog>.<name>. > We need this because at least in Oracle, procedures may be encapsulated in Oracle Packages that are used as catalog names in the DatabaseMetaData. When trying to import these into Teiid, the "Name in Source" field does not allow me to specify the Package name, so I can't call those procedures. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3870) Add ability to fully qualify an object with its package/catalog name

by Steve Tran (JIRA)

Steve Tran created TEIID-3870: --------------------------------- Summary: Add ability to fully qualify an object with its package/catalog name Key: TEIID-3870 URL: https://issues.jboss.org/browse/TEIID-3870 Project: Teiid Issue Type: Feature Request Affects Versions: 8.7.1.6_2 Environment: Red Hat JBoss Data Virtualization 6.2 on EAP6.4.0 patched to version 6.4.3, JBoss Developer Studio 8.1.0GA with Teiid Designer plugin 9.0.3.Final.v20150810-1438-B1157 64-bit Windows 7 environment Reporter: Steve Tran Assignee: Steven Hawkins Add ability to fully qualify a database object's (tables/views/procedures/etc) "Name in Source" field with its package/catalog name. We need this because at least in Oracle, procedures may be encapsulated in Oracle Packages. When trying to import these into Teiid, the "Name in Source" field does not allow me to specify the Package name, so I can't call those procedures. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3298) invokeHttp procedure should support returning HTTP Response Code

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3298?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-3298: ------------------------------------- Assignee: (was: Steven Hawkins) > invokeHttp procedure should support returning HTTP Response Code > ---------------------------------------------------------------- > > Key: TEIID-3298 > URL: https://issues.jboss.org/browse/TEIID-3298 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.4 > Reporter: Ramesh Reddy > Fix For: 9.1 > > > Currently WS Translator supplied "invokeHttp" procedure only returns the result and as well as the content-type. It should also return response code. > It may be useful to check if there is any other return parameters can be useful too. Like cookie etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3298) invokeHttp procedure should support returning HTTP Response Code

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3298?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3298: ---------------------------------- Fix Version/s: 9.1 Adding into 9.1 since there isn't a direct driver for 9.0. > invokeHttp procedure should support returning HTTP Response Code > ---------------------------------------------------------------- > > Key: TEIID-3298 > URL: https://issues.jboss.org/browse/TEIID-3298 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.4 > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 9.1 > > > Currently WS Translator supplied "invokeHttp" procedure only returns the result and as well as the content-type. It should also return response code. > It may be useful to check if there is any other return parameters can be useful too. Like cookie etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3861) re-done embedded examples in terms of their build

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3861?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3861: --------------------------------------- Fantastic work. With the kit being removed, do we want to just have a link to the maven based examples on http://teiid.jboss.org/downloads/ > re-done embedded examples in terms of their build > ------------------------------------------------- > > Key: TEIID-3861 > URL: https://issues.jboss.org/browse/TEIID-3861 > Project: Teiid > Issue Type: Task > Reporter: Kylin Soong > Assignee: Kylin Soong > > The embedded examples needs to be re-done in terms of their build. I will be removing the embedded kit in next release of Teiid 8.13. That means all the examples you have just need to depend upon maven pom files and their dependencies for building them. IMO you do not need to provide any run.sh kind of scripts, just provide the code that can compiled with right dependencies. Each example MUST be independent, i.e no parent POM brings a bucket of dependencies. Have example documented clearly what dependencies it takes to compile and execute. Then have the parent readme.md file documented with all different types of translators, and their maven dependency xml code fragment. See this as example https://github.com/wildfly-swarm/wildfly-swarm-examples/tree/master/datas... this is the format we need to follow. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 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 December 2015