October 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2720) Update Infinispan connector/translator to support JDG 6.2

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2720?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2720: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1022609 > Update Infinispan connector/translator to support JDG 6.2 > --------------------------------------------------------- > > Key: TEIID-2720 > URL: https://issues.jboss.org/browse/TEIID-2720 > Project: Teiid > Issue Type: Component Upgrade > Components: Misc. Connectors > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Blocker > Fix For: 8.4.1 > > > Update Infinispan connector/translator to support JDG 6.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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2720) Update Infinispan connector/translator to support JDG 6.2

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2720?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2720: ---------------------------------- Issue Type: Component Upgrade (was: Feature Request) If the changes don't break with EAP community, then this can also be targeted at 8.6. Even 8.7 will still be targeted at the EAP community version. > Update Infinispan connector/translator to support JDG 6.2 > --------------------------------------------------------- > > Key: TEIID-2720 > URL: https://issues.jboss.org/browse/TEIID-2720 > Project: Teiid > Issue Type: Component Upgrade > Components: Misc. Connectors > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Blocker > Fix For: 8.4.1 > > > Update Infinispan connector/translator to support JDG 6.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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2720) Update Infinispan connector/translator to support JDG 6.2

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2720?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2720: ---------------------------------- Fix Version/s: (was: 8.7) > Update Infinispan connector/translator to support JDG 6.2 > --------------------------------------------------------- > > Key: TEIID-2720 > URL: https://issues.jboss.org/browse/TEIID-2720 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Blocker > Fix For: 8.4.1 > > > Update Infinispan connector/translator to support JDG 6.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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2720) Update Infinispan connector/translator to support JDG 6.2

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2720?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2720: ------------------------------------ The initial testing indicated that the 8.4.x version of the connector would not work with the JDG 6.2 version of Infinispan. It seems there's been some class heirarchy changes that breaks it. Also, classes have been rearranged between inifinispan-commons and infinispan-core between the releases. So that infinispan-core is needed by the client in the version in EAP 6.1, and infinispan-commons is needed for JDG 6.2. > Update Infinispan connector/translator to support JDG 6.2 > --------------------------------------------------------- > > Key: TEIID-2720 > URL: https://issues.jboss.org/browse/TEIID-2720 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Blocker > Fix For: 8.4.1, 8.7 > > > Update Infinispan connector/translator to support JDG 6.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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2720) Update Infinispan connector/translator to support JDG 6.2

by Van Halbert (JIRA)

Van Halbert created TEIID-2720: ---------------------------------- Summary: Update Infinispan connector/translator to support JDG 6.2 Key: TEIID-2720 URL: https://issues.jboss.org/browse/TEIID-2720 Project: Teiid Issue Type: Feature Request Components: Misc. Connectors Affects Versions: 8.4.1 Reporter: Van Halbert Assignee: Van Halbert Priority: Blocker Fix For: 8.4.1, 8.7 Update Infinispan connector/translator to support JDG 6.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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2719) IllegalAccessError When OData URL is invoked

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2719: ----------------------------------- Summary: IllegalAccessError When OData URL is invoked Key: TEIID-2719 URL: https://issues.jboss.org/browse/TEIID-2719 Project: Teiid Issue Type: Bug Affects Versions: 8.6 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.6 Any OData access invoked throws exception {code} Caused by: java.lang.IllegalAccessError: tried to access class org.teiid.jdbc.SocketProfile from class org.teiid.jdbc.TeiidDriver at org.teiid.jdbc.TeiidDriver.<init>(TeiidDriver.java:72) [teiid-admin-8.6.0.Alpha3-SNAPSHOT.jar:8.6.0.Alpha3-SNAPSHOT] at org.teiid.jdbc.TeiidDriver.<clinit>(TeiidDriver.java:60) [teiid-admin-8.6.0.Alpha3-SNAPSHOT.jar:8.6.0.Alpha3-SNAPSHOT] at org.teiid.odata.LocalClient.<init>(LocalClient.java:89) [classes:] at org.teiid.odata.TeiidProducerProvider.getContext(TeiidProducerProvider.java:78) [classes:] at org.teiid.odata.TeiidProducerProvider.getContext(TeiidProducerProvider.java:37) [classes:] at org.odata4j.producer.resources.BaseResource.getODataProducer(BaseResource.java:119) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:] at org.odata4j.producer.resources.EntitiesRequestResource.getEntities(EntitiesRequestResource.java:264) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_35] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_35] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_35] at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_35] at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:167) [resteasy-jaxrs-2.3.7.Final.jar:] at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:269) [resteasy-jaxrs-2.3.7.Final.jar:] at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227) [resteasy-jaxrs-2.3.7.Final.jar:] at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:216) [resteasy-jaxrs-2.3.7.Final.jar:] at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:542) [resteasy-jaxrs-2.3.7.Final.jar:] ... 20 more {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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2715) Created and registered MXD, extra metadata is not visible when queried.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2715?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2715: --------------------------------------- > as Primary Key information on Properties seem to be missing and there needs to be FK relation between these both tables to use OData navigation feature to join between these two tables. A proper unique/fk relationship does not exist between properties and tables as the properties table is for all objects. You can of course always add any denomalized view that you want to your vdb to handle the extension metadata access - the question here would be more of what do you want to do with the extension metadata? > Created and registered MXD, extra metadata is not visible when queried. > ----------------------------------------------------------------------- > > Key: TEIID-2715 > URL: https://issues.jboss.org/browse/TEIID-2715 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.6 > Environment: Windows 7 > Reporter: Alex Khvatov > Assignee: Steven Hawkins > > x`Hi, > I used Teiid Designer and just plain XML editor (because Teiid Designer would constantly complain) I created Model Extension Definition file which I was able to successfully register. My definition was showing up in Model Extension Registry view. I deployed my virtual database and tried accessing columns and tables via Odata: > http://localhost:8080/odata/MCR_VDB/Tables?$format=json > http://localhost:8080/odata/MCR_VDB/Columns?$format=json > Both documents returned did not contain any extra metadata I defined. > HELP! > Thanks. > Alex -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2718) NPE During OData Access

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2718: ----------------------------------- Summary: NPE During OData Access Key: TEIID-2718 URL: https://issues.jboss.org/browse/TEIID-2718 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.3 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.6 While issuing a query like {code} http://localhost:8080/odata/{vdb-name}.1/SYS.Properties {code} it resulted in {code} 12:07:38,308 ERROR [org.teiid.ODATA] (http-/127.0.0.1:8080-2) null TEIID16013 Error occured producing OData result.: java.lang.NullPointerException at org.teiid.odata.ODataSQLBuilder.selectString(ODataSQLBuilder.java:210) [classes:] at org.teiid.odata.TeiidProducer.getNavProperty(TeiidProducer.java:86) [classes:] at org.teiid.odata.TeiidProducer.getEntities(TeiidProducer.java:79) [classes:] at org.odata4j.producer.resources.EntitiesRequestResource.getEntitiesImpl(EntitiesRequestResource.java:371) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:] at org.odata4j.producer.resources.EntitiesRequestResource.getEntities(EntitiesRequestResource.java:266) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_35] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_35] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_35] at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_35] at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:167) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1] at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:269) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1] at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1] at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:216) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1] at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:542) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1] at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:524) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1] at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:126) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1] at org.teiid.odata.ODataServletContainerDispatcher.service(ODataServletContainerDispatcher.java:97) [classes:] at org.teiid.odata.ODataServlet.service(ODataServlet.java:61) [classes:] at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-red {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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2715) Created and registered MXD, extra metadata is not visible when queried.

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2715?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2715: ------------------------------------- Yes, the extended properties are only defined on the "Properties" table. Steve mentioned this on the forum thread. The above REST call you are making is not on the Properties. You need to join both using UID column. One caveat I see you may not be able to use OData for this, as Primary Key information on Properties seem to be missing and there needs to be FK relation between these both tables to use OData navigation feature to join between these two tables. May be we can re-purpose this JIRA for it? > Created and registered MXD, extra metadata is not visible when queried. > ----------------------------------------------------------------------- > > Key: TEIID-2715 > URL: https://issues.jboss.org/browse/TEIID-2715 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.6 > Environment: Windows 7 > Reporter: Alex Khvatov > Assignee: Steven Hawkins > > x`Hi, > I used Teiid Designer and just plain XML editor (because Teiid Designer would constantly complain) I created Model Extension Definition file which I was able to successfully register. My definition was showing up in Model Extension Registry view. I deployed my virtual database and tried accessing columns and tables via Odata: > http://localhost:8080/odata/MCR_VDB/Tables?$format=json > http://localhost:8080/odata/MCR_VDB/Columns?$format=json > Both documents returned did not contain any extra metadata I defined. > HELP! > Thanks. > Alex -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2715) Created and registered MXD, extra metadata is not visible when queried.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2715?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2715: --------------------------------------- Correct me if I'm wrong Ramesh, but I don't think that there is any expectation that extension metadata will be present on the Tables system table. This would require a join between Tables and Properties. > Created and registered MXD, extra metadata is not visible when queried. > ----------------------------------------------------------------------- > > Key: TEIID-2715 > URL: https://issues.jboss.org/browse/TEIID-2715 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.6 > Environment: Windows 7 > Reporter: Alex Khvatov > Assignee: Steven Hawkins > > x`Hi, > I used Teiid Designer and just plain XML editor (because Teiid Designer would constantly complain) I created Model Extension Definition file which I was able to successfully register. My definition was showing up in Model Extension Registry view. I deployed my virtual database and tried accessing columns and tables via Odata: > http://localhost:8080/odata/MCR_VDB/Tables?$format=json > http://localhost:8080/odata/MCR_VDB/Columns?$format=json > Both documents returned did not contain any extra metadata I defined. > HELP! > Thanks. > Alex -- 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

11 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2013