January 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3927) Teiid Analytical Capabilities enhancement

by Kylin Soong (JIRA)

Kylin Soong created TEIID-3927: ---------------------------------- Summary: Teiid Analytical Capabilities enhancement Key: TEIID-3927 URL: https://issues.jboss.org/browse/TEIID-3927 Project: Teiid Issue Type: Feature Request Affects Versions: 9.x Reporter: Kylin Soong Assignee: Kylin Soong Fix For: 9.x >From DV 7 F2F notes, Analytical Capabilities be referred in 2 approach: h3. Do our own * Support for row counts beyond 2 billion (done) * Increased parallism within the plan, which includes parallelization of source queries via partitioning beyond multi-source * Increased windowing function support h3. Alignment with a larger platform Sub-Task -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3926) update teiid website doc page to linked with gitbook adoc content.

by Kylin Soong (JIRA)

Kylin Soong created TEIID-3926: ---------------------------------- Summary: update teiid website doc page to linked with gitbook adoc content. Key: TEIID-3926 URL: https://issues.jboss.org/browse/TEIID-3926 Project: Teiid Issue Type: Sub-task Reporter: Kylin Soong Assignee: Steven Hawkins Teiid 9.x version's document should add to http://teiid.jboss.org/docs/, this also base on "DV 7 Face To Face Notes" in mojo page -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3900) OData - malformed URL causes NPE

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-3900?page=com.atlassian.jira.plugin... ] Juraj Duráni closed TEIID-3900. ------------------------------- > 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)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3840) teiid-outh-util.bat - typo in name

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-3840?page=com.atlassian.jira.plugin... ] Juraj Duráni closed TEIID-3840. ------------------------------- > teiid-outh-util.bat - typo in name > ---------------------------------- > > Key: TEIID-3840 > URL: https://issues.jboss.org/browse/TEIID-3840 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.10.1 > Reporter: Juraj Duráni > Assignee: Juraj Duráni > Priority: Trivial > Fix For: 8.12.3, 8.13 > > > File name 'teiid-outh-util.bat' contains typo. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3895) OData - metadata returns primary key with attribute "Nullable=true"

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-3895?page=com.atlassian.jira.plugin... ] Juraj Duráni closed TEIID-3895. ------------------------------- > 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)

8 years, 11 months

1
0
0 / 0

[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 updated TEIID-3725: ------------------------------- Git Pull Request: https://github.com/teiid/teiid/pull/588 > 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 > Fix For: 8.12.x, 63-8.12.x > > > 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)

8 years, 11 months

1
0
0 / 0

[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 updated TEIID-3725: ------------------------------- Fix Version/s: 63-8.12.x 8.12.x > 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 > Fix For: 8.12.x, 63-8.12.x > > > 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)

8 years, 11 months

1
0
0 / 0

[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... ] Work on TEIID-3725 stopped by Van Halbert. ------------------------------------------ > 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 > Fix For: 8.12.x, 63-8.12.x > > > 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)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3559) Refactor Object and Infinispan translator / connectors

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3559?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3559: ------------------------------------ completed refactoring to be based on common translator-object translator for reads/writes/materialization. > Refactor Object and Infinispan translator / connectors > ------------------------------------------------------ > > Key: TEIID-3559 > URL: https://issues.jboss.org/browse/TEIID-3559 > Project: Teiid > Issue Type: Task > Components: Misc. Connectors > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Optional > > Now that JDG has reworked its remote-cache and changed (reduced) what dependencies its exposed, there's now more common code between the object/infinispan-cache translator/connector and the infinispan-cache-dsl translator/connector. I think refactoring can eliminate issues with support and ensure common behavior across all the code. > Where is common code seen: > - searching (i.e., DSLSearch) > - updates (InfinispanUpdateExecution) > - ClassRegistry > (for starters) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3559) Refactor Object and Infinispan translator / connectors

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3559?page=com.atlassian.jira.plugin... ] Work on TEIID-3559 stopped by Van Halbert. ------------------------------------------ > Refactor Object and Infinispan translator / connectors > ------------------------------------------------------ > > Key: TEIID-3559 > URL: https://issues.jboss.org/browse/TEIID-3559 > Project: Teiid > Issue Type: Task > Components: Misc. Connectors > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Optional > > Now that JDG has reworked its remote-cache and changed (reduced) what dependencies its exposed, there's now more common code between the object/infinispan-cache translator/connector and the infinispan-cache-dsl translator/connector. I think refactoring can eliminate issues with support and ensure common behavior across all the code. > Where is common code seen: > - searching (i.e., DSLSearch) > - updates (InfinispanUpdateExecution) > - ClassRegistry > (for starters) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2016