July 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3038) Add spatial query support to the Teiid MongoDB translator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3038?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3038: --------------------------------------- Since we don't much in the way of spatial support in Teiid, what are you proposing the support for mongodb would look like? > Add spatial query support to the Teiid MongoDB translator > --------------------------------------------------------- > > Key: TEIID-3038 > URL: https://issues.jboss.org/browse/TEIID-3038 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.8 > Reporter: Michael Farwell > Assignee: Steven Hawkins > Fix For: 8.8 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3037) Incorrect odata4j jar name

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3037?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3037. ----------------------------------- Fix Version/s: 8.7.1 8.9 Resolution: Done Posted a new odata4j jar to the repository without the -redhat classifier and updated the poms in master/8.8.x/8.7.x We'll replace the temporarily modified 8.8 final kit with a full rebuild once more issue accrue against 8.8. > Incorrect odata4j jar name > -------------------------- > > Key: TEIID-3037 > URL: https://issues.jboss.org/browse/TEIID-3037 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.8 > Reporter: Cristiano Nicolai > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 8.7.1, 8.9 > > > When deploying Teiid 8.8.0.Final, odata4j fails to initialize due to the wrong jar name. > MSC000001: Failed to start service jboss.module.service."deployment.teiid-odata-8.8.0.Final.war".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.teiid-odata-8.8.0.Final.war".main: JBAS018759: Failed to load module: deployment.teiid-odata-8.8.0.Final.war:main > Module declaration is set as: > <resource-root path="odata4j-core-0.8.0-SNAPSHOT-redhat.jar" /> > But the provided jar name is: > odata4j-core-0.8.0-SNAPSHOT-redhat-redhat.jar > There is an extra "-redhat" in the jar name. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3030) Update Saxon to current release (9.5.x)

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3030?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3030. ----------------------------------- Fix Version/s: 8.9 Resolution: Done Upgraded to 9.5.1-6. There is quite a bit of movement with the saxon apis, so we may need to do this on a more regular basis. It looks like we can also update our logic to support document projection/streaming for passing variables and not just the context item. > Update Saxon to current release (9.5.x) > --------------------------------------- > > Key: TEIID-3030 > URL: https://issues.jboss.org/browse/TEIID-3030 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 8.7 > Environment: Apache Maven 3.2.2 (45f7c06d68e745d05611f7fd14efb6594181933e; 2014-06-17T09:51:42-04:00) > Maven home: C:\Java\apache-maven-3.2.2 > Java version: 1.7.0_60, vendor: Oracle Corporation > Java home: C:\Program Files\Java\jdk1.7.0_60\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows" > Reporter: Gary Gregory > Assignee: Steven Hawkins > Fix For: 8.9 > > > Our product embeds a Teiid server and provides its own set of 3rd party jar files, one of which clashes with Teiid: we provide Saxon-HE 9.4.0.6 and Teiid provides 9.2.1.5. These two versions are NOT binary compatible. > This shows up using the web services connector as a class not found error because some classes have been repackaged between Saxon 9.2.x and 9.4.x. > If Teiid updates to the latest version (9.5), so can we, and avoid backporting our Saxon dependencies. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3038) Add spatial query support to the Teiid MongoDB translator

by Michael Farwell (JIRA)

Michael Farwell created TEIID-3038: -------------------------------------- Summary: Add spatial query support to the Teiid MongoDB translator Key: TEIID-3038 URL: https://issues.jboss.org/browse/TEIID-3038 Project: Teiid Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Misc. Connectors Affects Versions: 8.8 Reporter: Michael Farwell Assignee: Steven Hawkins Fix For: 8.8 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3037) Incorrect odata4j jar name

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3037?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3037: --------------------------------------- Temporarily I've updated the download kit with a new module xml name. More than likely we'll look to do an 8.8.1 with some other fixes, and we'll update the repository to contain the -redhat version odata4j jar without the redhat classifier. > Incorrect odata4j jar name > -------------------------- > > Key: TEIID-3037 > URL: https://issues.jboss.org/browse/TEIID-3037 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.8 > Reporter: Cristiano Nicolai > Assignee: Steven Hawkins > Priority: Blocker > > When deploying Teiid 8.8.0.Final, odata4j fails to initialize due to the wrong jar name. > MSC000001: Failed to start service jboss.module.service."deployment.teiid-odata-8.8.0.Final.war".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.teiid-odata-8.8.0.Final.war".main: JBAS018759: Failed to load module: deployment.teiid-odata-8.8.0.Final.war:main > Module declaration is set as: > <resource-root path="odata4j-core-0.8.0-SNAPSHOT-redhat.jar" /> > But the provided jar name is: > odata4j-core-0.8.0-SNAPSHOT-redhat-redhat.jar > There is an extra "-redhat" in the jar name. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2786) ModeShape ExecutionFactory.getMetadata fails with java.sql.SQLFeatureNotSupportedException

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2786?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2786: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1048948|https://bugzilla.redhat.com/show_bug.cgi?id=1048948] from MODIFIED to ASSIGNED > ModeShape ExecutionFactory.getMetadata fails with java.sql.SQLFeatureNotSupportedException > ------------------------------------------------------------------------------------------ > > Key: TEIID-2786 > URL: https://issues.jboss.org/browse/TEIID-2786 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 7.7 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.7 > > Attachments: mode.patch > > > When trying to use the Teiid Designer feature of importing using a Teiid Connection fails when the connection is to ModeShape. The following exception: > 08:33:44,914 ERROR [stderr] (teiid-async-threads - 2) java.sql.SQLFeatureNotSupportedException > 08:33:44,915 ERROR [stderr] (teiid-async-threads - 2) at org.modeshape.jdbc.JcrMetaData.getTypeInfo(JcrMetaData.java:1656) > 08:33:44,915 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:107) > 08:33:44,915 INFO [org.jboss.as.server] (management-handler-thread - 4) JBAS018559: Deployed "importVDB-vdb.xml" (runtime-name : "importVDB-vdb.xml") > 08:33:44,916 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.translator.jdbc.modeshape.ModeShapeExecutionFactory.getMetadata(ModeShapeExecutionFactory.java:280) > 08:33:44,916 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.translator.jdbc.modeshape.ModeShapeExecutionFactory.getMetadata(ModeShapeExecutionFactory.java:62) > 08:33:44,916 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:61) > 08:33:44,917 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) > 08:33:44,917 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.jboss.VDBService$6.run(VDBService.java:397) > 08:33:44,917 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.jboss.VDBService$7.run(VDBService.java:444) > 08:33:44,918 ERROR [stderr] (teiid-async-threads - 2) at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33) > My guess is the local modeshape jdbc driver hasn't been fully vetted in this area, as the remote JDBC version has been the one used when using the Modeshape eclipse plugin for importing the metadata. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3033) Importing metadata thru Designer versus using dynamic VDB is different

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3033?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3033: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1048948|https://bugzilla.redhat.com/show_bug.cgi?id=1048948] from MODIFIED to ASSIGNED > Importing metadata thru Designer versus using dynamic VDB is different > ---------------------------------------------------------------------- > > Key: TEIID-3033 > URL: https://issues.jboss.org/browse/TEIID-3033 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.7.1, 8.9 > Reporter: Van Halbert > Assignee: Van Halbert > > The columns names and NIS, imported via Designer, show that the column name is set as the NIS, and then converted (replace colon with underscore) to be used as the column name. However, in the mode shape translator, this logic isn't being applied -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3033) Importing metadata thru Designer versus using dynamic VDB is different

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3033?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3033: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1048948 > Importing metadata thru Designer versus using dynamic VDB is different > ---------------------------------------------------------------------- > > Key: TEIID-3033 > URL: https://issues.jboss.org/browse/TEIID-3033 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.7.1, 8.9 > Reporter: Van Halbert > Assignee: Van Halbert > > The columns names and NIS, imported via Designer, show that the column name is set as the NIS, and then converted (replace colon with underscore) to be used as the column name. However, in the mode shape translator, this logic isn't being applied -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3037) Incorrect odata4j jar name

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3037?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3037: --------------------------------------- Yes, we applied https://github.com/teiid/teiid/commit/f2c566e1224254c723f2603b42247ebfdf8... from our build group, which removed the extra -redhat, but didn't see that they had not corrected the repository. So yes the build still picked up the -redhat-redhat jar. The workarounds are to change the module.xml or the jar name. We'll likely post a rekitting with that addressed. > Incorrect odata4j jar name > -------------------------- > > Key: TEIID-3037 > URL: https://issues.jboss.org/browse/TEIID-3037 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.8 > Reporter: Cristiano Nicolai > Assignee: Steven Hawkins > Priority: Blocker > > When deploying Teiid 8.8.0.Final, odata4j fails to initialize due to the wrong jar name. > MSC000001: Failed to start service jboss.module.service."deployment.teiid-odata-8.8.0.Final.war".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.teiid-odata-8.8.0.Final.war".main: JBAS018759: Failed to load module: deployment.teiid-odata-8.8.0.Final.war:main > Module declaration is set as: > <resource-root path="odata4j-core-0.8.0-SNAPSHOT-redhat.jar" /> > But the provided jar name is: > odata4j-core-0.8.0-SNAPSHOT-redhat-redhat.jar > There is an extra "-redhat" in the jar name. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3037) Incorrect odata4j jar name

by Cristiano Nicolai (JIRA)

Cristiano Nicolai created TEIID-3037: ---------------------------------------- Summary: Incorrect odata4j jar name Key: TEIID-3037 URL: https://issues.jboss.org/browse/TEIID-3037 Project: Teiid Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 8.8 Reporter: Cristiano Nicolai Assignee: Steven Hawkins Priority: Blocker When deploying Teiid 8.8.0.Final, odata4j fails to initialize due to the wrong jar name. MSC000001: Failed to start service jboss.module.service."deployment.teiid-odata-8.8.0.Final.war".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.teiid-odata-8.8.0.Final.war".main: JBAS018759: Failed to load module: deployment.teiid-odata-8.8.0.Final.war:main Module declaration is set as: <resource-root path="odata4j-core-0.8.0-SNAPSHOT-redhat.jar" /> But the provided jar name is: odata4j-core-0.8.0-SNAPSHOT-redhat-redhat.jar There is an extra "-redhat" in the jar name. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 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 July 2014