[JBoss JIRA] (TEIID-2786) ModeShape ExecutionFactory.getMetadata fails with java.sql.SQLFeatureNotSupportedException
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2786?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2786.
---------------------------------
> 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, 9 months
[JBoss JIRA] (TEIID-2997) 202 Accepted response for odata batch requests (while sending multiple POST xml requests)
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2997?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2997.
---------------------------------
> 202 Accepted response for odata batch requests (while sending multiple POST xml requests)
> -----------------------------------------------------------------------------------------
>
> Key: TEIID-2997
> URL: https://issues.jboss.org/browse/TEIID-2997
> Project: Teiid
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: OData
> Reporter: K Prashanthi
> Assignee: Steven Hawkins
>
> Hi,
> I am trying to send multiple xml inputs through odata batch in POSTMAN rest client. But i am getting 202 Accepted response and i do not see the data being reflected in the backend.
> URL- http://<host>:<port>/odata/<vdb>/<view>/$batch
> Headers:
> Content-Type:multipart/mixed
> boundary: batch
> Request Body:
> --batch
> POST /$batch HTTP/1.1
> Content-Type: multipart/mixed; boundary=changeset
> --changeset
> Content-Type: application/xml
> Content-Transfer-Encoding: binary
> POST
> Content-Type:application/xml
> Content-Length:1024
>
> XML INPUT-1
>
>
> --changeset
> Content-Type:application/xml
> Content-Transfer-Encoding: binary
> POST
> Content-Type:application/xml
> Content-Length:1024
> XMl Input-2
> --changeset--
> --batch--
> Please suggest.
> Thanks
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (TEIID-2995) procedure with inputs fails to be found when executed via odata
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2995?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2995.
---------------------------------
> procedure with inputs fails to be found when executed via odata
> ---------------------------------------------------------------
>
> Key: TEIID-2995
> URL: https://issues.jboss.org/browse/TEIID-2995
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: OData
> Reporter: Tom Johnston
> Assignee: Steven Hawkins
>
> The following snippet is what is seen in the $metadata call
> {code}
> <ComplexType Name="getNominationbyRange_NewProcedureResult">
> <Property Name="WorkplanID" Type="Edm.String" Nullable="true" MaxLength="4000" FixedLength="false" Unicode="true"/>
> <Property Name="RationaleComments" Type="Edm.String" Nullable="true" MaxLength="4000" FixedLength="false" Unicode="true"/>
> </ComplexType>
> <EntityContainer Name="NominationRationaleVIEW" m:IsDefaultEntityContainer="false">
> <EntitySet Name="toLoadData" EntityType="NominationRationaleVIEW.toLoadData"/>
> <FunctionImport Name="getNominationbyRange" ReturnType="Collection(NominationRationaleVIEW.getNominationbyRange_NewProcedureResult)" m:HttpMethod="GET">
> <Parameter Name="StartNbr" Type="Edm.Int64" Mode="In" Nullable="false"/>
> <Parameter Name="EndNbr" Type="Edm.Int64" Mode="In" Nullable="false"/>
> </FunctionImport>
> </EntityContainer>
> {code}
> the ERROR is:
> {code}
> <error xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata">
> <code>NotFoundException</code>
> <message lang="en-US">
> TEIID16011 EntitySet "NominationRationaleVIEW.getNominationbyRange" is not found; Check the spelling, use modelName.tableName; The table that representing the Entity type must either have a PRIMARY KEY or UNIQUE key(s)
> </message>
> </error>
> {code}
> the sample URL I'm trying is:
> http://127.0.0.1:8180/odata/POC_VDB/NominationRationaleVIEW.getNomination...
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (TEIID-2851) ODATA POST fails if table column is of IDENTITY type (sql server)
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2851?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2851.
---------------------------------
> ODATA POST fails if table column is of IDENTITY type (sql server)
> -----------------------------------------------------------------
>
> Key: TEIID-2851
> URL: https://issues.jboss.org/browse/TEIID-2851
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: OData
> Affects Versions: 8.6
> Reporter: Alex Khvatov
> Assignee: Ramesh Reddy
> Labels: Alpha3
> Fix For: 8.7
>
>
> While INSERT into virtual table created from a table that has IDENTITY (autoincrement) feild (in sql server) works if inserted via JDBC, POST to the same table using ODATA fails.
> I am attaching the stack trace we get.
> {code}
> 09:49:24,010 ERROR [org.teiid.ODATA] (http-localhost/127.0.0.1:8080-5) null TEIID16013 Error occured producing OData result.: java.lang.RuntimeException: No elements match the predicate
> at org.core4j.Enumerable.first(Enumerable.java:125) [core4j-0.5.jar:]
> at org.odata4j.core.OEntities$OEntityImpl.getProperty(OEntities.java:219) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:]
> at org.teiid.odata.ODataSQLBuilder.buildEntityKey(ODataSQLBuilder.java:1005) [classes:]
> at org.teiid.odata.TeiidProducer.createEntity(TeiidProducer.java:172) [classes:]
> at org.odata4j.producer.resources.EntitiesRequestResource.createEntity(EntitiesRequestResource.java:124) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:]
> at org.odata4j.producer.resources.EntitiesRequestResource.createEntity(EntitiesRequestResource.java:111) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:]
> at sun.reflect.GeneratedMethodAccessor150.invoke(Unknown Source) [:1.7.0_17]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) [rt.jar:1.7.0_17]
> at java.lang.reflect.Method.invoke(Unknown Source) [rt.jar:1.7.0_17]
> 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-redhat-1]
> 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.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:481) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_17]
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (TEIID-2985) odbc script reader does not handle extra statement delimiters
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2985?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2985.
---------------------------------
> odbc script reader does not handle extra statement delimiters
> -------------------------------------------------------------
>
> Key: TEIID-2985
> URL: https://issues.jboss.org/browse/TEIID-2985
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: ODBC
> Affects Versions: 7.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.7.1, 8.8
>
>
> If sent the block of statements:
> BEGIN;declare "SQL_CUR0x1e4ba50" cursor with hold for select * from pg_proc;;fetch 1 in "SQL_CUR0x1e4ba50"
> We'll stop processing at the extra ; after the declare.
> In older branches such as 7.7 we'll attempt to process an empty sql statement, which will throw an exception.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (TEIID-2993) Adding source table with quoted name results in wrong generated SQL statement
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2993?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2993.
---------------------------------
> Adding source table with quoted name results in wrong generated SQL statement
> -----------------------------------------------------------------------------
>
> Key: TEIID-2993
> URL: https://issues.jboss.org/browse/TEIID-2993
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Query Engine
> Affects Versions: 6.0.0
> Reporter: Paul Richardson
> Assignee: Steven Hawkins
>
> Cloned from TEIIDDES-2152:
> 1) Created source model with simple table named "My.Quoted.Table" (including quotes
> 2) Created simple virtual table and pasted: SELECT * FROM "My.Quoted.Table"
> 3) Parser returned a command resulting in the SQL: SELECT * FROM My.Quoted."Table"
> Parser should be able to handle quoted names properly. In this case the SQL should have been valid as is.
> Confirmed that this does go right back to the Teiid parser. To confirm, the following test was included in
> src/test/java/org/teiid/query/parser/TestParser.java
> {code}
> @Test
> public void testQuotedSQLString() {
> String sql = "SELECT * FROM \"My.Quoted.Table\""; //$NON-NLS-1$
> String expected = "SELECT * FROM \"MY.QUOTED.TABLE\""; //$NON-NLS-1$
> helpTest(sql, expected, null);
> }
> {code}
> Test fails with a comparison error with the parser returning the SQL in item 3 above.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months