[JBoss JIRA] (TEIID-3725) In the JDG translators, enable named cache swapping so that materialization can be supported
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3725?page=com.atlassian.jira.plugin... ]
Van Halbert edited comment on TEIID-3725 at 1/12/16 1:00 PM:
-------------------------------------------------------------
The native queries are currently looking like:
Before native query format:
{code}
truncate cache
{code}
After native query format:
{code}
swap cache names
{code}
changed to remove the cache names on the native query as the resource adapter will have this configured.
was (Author: van.halbert):
The native queries are currently looking like:
Before native query format:
{code}
truncate cache {stageCacheName} {aliasCacheName}
{code}
After native query format:
{code}
swap cache names {primaryCacheName} {stageCacheName} {aliasCacheName}
{code}
where:
primaryCacheName - is the cache that could already be available
stageCacheName - is the second cache to be used in materialization
aliasCacheName - is the cache to persist the cache alias names key<String> --> value<String>
> In the JDG translators, enable named cache swapping so that materialization can be supported
> --------------------------------------------------------------------------------------------
>
> Key: TEIID-3725
> URL: https://issues.jboss.org/browse/TEIID-3725
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Affects Versions: 8.12
> Reporter: Van Halbert
> Assignee: Van Halbert
>
> The JDG translators, that in order to support materialization, will need to enable the named cache that's referenced by the connection, to be swapped. This is due to JDG doesn't currently support renaming a cache (i.e., like table rename in JDBC). And because of that, it limits how the cache can be refreshed (don't want to clear it before re-loading).
> Ideas are:
> 1. configure translator with the 2 cache names to use (a) initial cache to read from and (b) the staging cache to use
> perform materialize load
> call SYSADMIN.setProperty to trigger the swapping of the cache names
> 2 ???
> Note: because there's no persistence in Teiid so that any cache name changes will outlive a server restart, when a restart occurs, the translator will read from the cache identified as the initial cache to read from.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years
[JBoss JIRA] (TEIID-3899) Allow Web Services translator to retrieve metadata without source connection
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3899?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3899:
-------------------------------------
Modified as you suggested.
> Allow Web Services translator to retrieve metadata without source connection
> ----------------------------------------------------------------------------
>
> Key: TEIID-3899
> URL: https://issues.jboss.org/browse/TEIID-3899
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Affects Versions: 8.11
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Labels: 8.12.4
> Fix For: 8.13, 8.12.4
>
>
> The "ws" translator, is set to "isSourceRequiredForMetadata" to true. However, there are two issues
> 1) There is no way to turn this flag to false
> 2) If the "ws" translator is secured through "security-domain", then authentication failure message by passes the "isSourceRequiredForMetadata" flag and returns as error, thus leaving the VDB in "metadata load failed" state.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years
[JBoss JIRA] (TEIID-3890) Add a redshift translator
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3890?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3890.
-----------------------------------
Resolution: Done
Added the translator to resolve various issues with redshift and the standard postgres translator. The 9.0 docs have been updated, and I'll roll the changes back from there.
> Add a redshift translator
> -------------------------
>
> Key: TEIID-3890
> URL: https://issues.jboss.org/browse/TEIID-3890
> Project: Teiid
> Issue Type: Feature Request
> Components: JDBC Connector
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.13, 8.12.4
>
>
> To account for differences between Redshift and Postgres, a new translator should be added.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years
[JBoss JIRA] (TEIID-3900) OData - malformed URL causes NPE
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3900?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-3900.
---------------------------------
Fix Version/s: 8.13
8.12.4
Resolution: Done
Thanks Juraj.
> OData - malformed URL causes NPE
> --------------------------------
>
> Key: TEIID-3900
> URL: https://issues.jboss.org/browse/TEIID-3900
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.12.3
> Reporter: Juraj Duráni
> Assignee: Juraj Duráni
> Fix For: 8.13, 8.12.4
>
>
> Malformed URL \[1\] causes NPE in Teiid \[2\].
> \[1\] http://localhost:8080/odata/test$metadata (missing '/' after VDB name)
> \[2\]
> {code:text}
> [org.teiid.ODATA] (http-/127.0.0.1:8080-1) TEIID16013 Error occurred producing OData result.: java.lang.NullPointerException
> at org.teiid.odbc.ODBCServerRemoteImpl.setConnectionProperties(ODBCServerRemoteImpl.java:304) [teiid-runtime-8.12.3.redhat-1.jar:8.12.3.redhat-1]
> at org.teiid.odata.LocalClient.getConnection(LocalClient.java:167) [classes:]
> at org.teiid.odata.LocalClient.getVDB(LocalClient.java:139) [classes:]
> at org.teiid.odata.LocalClient.getMetadata(LocalClient.java:484) [classes:]
> at org.teiid.odata.TeiidProducer.getMetadata(TeiidProducer.java:83) [classes:]
> at org.odata4j.producer.resources.ServiceDocumentResource.getServiceDocument(ServiceDocumentResource.java:35) [odata-core-0.8.10.jar:0.8.10]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_40]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_40]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_40]
> at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_40]
> at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:168) [resteasy-jaxrs-2.3.12.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:269) [resteasy-jaxrs-2.3.12.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227) [resteasy-jaxrs-2.3.12.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:216) [resteasy-jaxrs-2.3.12.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:561) [resteasy-jaxrs-2.3.12.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:543) [resteasy-jaxrs-2.3.12.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:128) [resteasy-jaxrs-2.3.12.Final-redhat-1.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.12.Final-redhat-1.jar:]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-2.jar:1.0.2.Final-redhat-2]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:512) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.5.4.Final-redhat-4.jar:7.5.4.Final-redhat-4]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:150) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:344) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:854) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_40]
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years
[JBoss JIRA] (TEIID-3895) OData - metadata returns primary key with attribute "Nullable=true"
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3895?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3895.
-----------------------------------
Fix Version/s: 8.13
8.12.4
Resolution: Done
Merged the pull request. Thanks Juraj.
> OData - metadata returns primary key with attribute "Nullable=true"
> -------------------------------------------------------------------
>
> Key: TEIID-3895
> URL: https://issues.jboss.org/browse/TEIID-3895
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.12.3
> Reporter: Juraj Duráni
> Assignee: Juraj Duráni
> Fix For: 8.13, 8.12.4
>
>
> If column's name in source (PHYSICAL) model has different name than one in the source (case sensitive) then attribute "Nullable" is set to true.
> {code:xml}
> <vdb name="test" version="1">
> <model name="Source" type="PHYSICAL">
> <source name="rs" connection-jndi-name="java:/Redshift" translator-name="postgresql"/>
> <metadata type="DDL">
> <![CDATA[create foreign table SmallB (
> IntKey integer PRIMARY KEY OPTIONS(NAMEINSOURCE 'intkey', NATIVE_TYPE 'int4')) OPTIONS(NAMEINSOURCE 'smalla');
> ]]>
> </metadata>
> </model>
> </vdb>
> {code}
> result:
> {code:xml}
> <edmx:Edmx xmlns:edmx="http://schemas.microsoft.com/ado/2007/06/edmx" Version="1.0">
> <edmx:DataServices xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata" m:DataServiceVersion="2.0">
> <Schema xmlns="http://schemas.microsoft.com/ado/2008/09/edm" Namespace="Source">
> <EntityType Name="SmallB">
> <Key>
> <PropertyRef Name="IntKey"/>
> </Key>
> <Property Name="IntKey" Type="Edm.Int32" Nullable="true"/>
> </EntityType>
> <EntityContainer Name="Source" m:IsDefaultEntityContainer="false">
> <EntitySet Name="SmallB" EntityType="Source.SmallB"/>
> </EntityContainer>
> </Schema>
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years
[JBoss JIRA] (TEIID-3898) Add OrientDB translator
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3898?page=com.atlassian.jira.plugin... ]
Steven Hawkins reassigned TEIID-3898:
-------------------------------------
Fix Version/s: Open To Community
Assignee: (was: Steven Hawkins)
Adding into the open to community bucket. The earliest a core dev could pick this up would be for 9.1. Any additional design considerations or goals (for example what is most pressing to support beyond having the generic ansi translator) will help.
> Add OrientDB translator
> -----------------------
>
> Key: TEIID-3898
> URL: https://issues.jboss.org/browse/TEIID-3898
> Project: Teiid
> Issue Type: Feature Request
> Components: JDBC Connector
> Reporter: Don Krapohl
> Fix For: Open To Community
>
>
> My organization has high-performance analytics on OrientDB graph databases. We use Teiid for centralized governance, access, etc. It would be beneficial to us if Teiid could translate to the SQL-like OrientDb syntax. Because there are many SQL-like syntax components of OrientDB's REST endpoints this should be fairly straightforward.
> The OrientDB site is http://orientdb.com/. It's Apache 2 licensed, has a stable and mature community, has multiple releases, and provides multiple access methods (jdbc, odbc, REST). Work on the translator should not be wasted effort.
> I can assist with testing if it would be helpful and if the translator is started I can assist in dev.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years