[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)
10 years, 2 months
[JBoss JIRA] (TEIID-3897) dimensional check for ewkb is incorrect
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3897?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3897.
-----------------------------------
Resolution: Done
Updated to check for a z coordinate value.
> dimensional check for ewkb is incorrect
> ---------------------------------------
>
> Key: TEIID-3897
> URL: https://issues.jboss.org/browse/TEIID-3897
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.11
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.13, 8.12.4
>
>
> The geometry logic to prevent ewkb from being used is looking for the number of dimensions to be greater than 2 - this will never be the case with jts. We should be looking instead at the coorinates for the z value. A similar check is needed when just wkt is expected and not ewkt.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (TEIID-3899) Allow Web Services translator to retrieve metadata without source connection
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3899?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3899:
---------------------------------------
The way things are set up, the translator has no knowledge of the wsdl other than the connection.
> 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)
10 years, 2 months
[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 updated TEIID-3900:
--------------------------------
Git Pull Request: https://github.com/teiid/teiid/pull/576
> 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
>
> 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)
10 years, 2 months
[JBoss JIRA] (TEIID-3900) OData - malformed URL causes NPE
by Juraj Duráni (JIRA)
Juraj Duráni created TEIID-3900:
-----------------------------------
Summary: 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
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)
10 years, 2 months
[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:
-------------------------------------
That sounds good. Why not just check if "wsdl" url if not null, make the connection required for metadata.
> 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)
10 years, 2 months
[JBoss JIRA] (TEIID-3899) Allow Web Services translator to retrieve metadata without source connection
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3899?page=com.atlassian.jira.plugin... ]
Steven Hawkins edited comment on TEIID-3899 at 1/11/16 5:30 PM:
----------------------------------------------------------------
Yes the change to true was made initially for wsdl support, but as you are noting here does not account for case where you just want the generic web procedures and have a connection factory that is initially unusable.
Rather than opening up a general property, I'd rather see something specific to the ws tranlator - this would look keeping the native metadatarepository change, having the required flag as false, and a specific importer.useWSDL (default true, if true and no connection then throw an exception). So in this specific case you would set importer.useWSDL=false and then this and all other cases would work as expected.
was (Author: shawkins):
Yes the change to true was made initially for wsdl support, but as you are noting here does not account for case where you just want the generic web procedures and have a connection factory that is initially unusable.
Rather than opening up a general property, I'd rather see something specific to the ws tranlator - this would look keeping the native metadatarepository change, having the required flag as false, and a specific importer.requireWSDL (default true, if true and no connection/wsdl then throw an exception). So in this specific case you would set importer.requireWSDL=false and then this and all other cases would work as expected.
> 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)
10 years, 2 months
[JBoss JIRA] (TEIID-3899) Allow Web Services translator to retrieve metadata without source connection
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3899?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3899:
---------------------------------------
Yes the change to true was made initially for wsdl support, but as you are noting here does not account for case where you just want the generic web procedures and have a connection factory that is initially unusable.
Rather than opening up a general property, I'd rather see something specific to the ws tranlator - this would look keeping the native metadatarepository change, having the required flag as false, and a specific importer.requireWSDL (default true, if true and no connection/wsdl then throw an exception). So in this specific case you would set importer.requireWSDL=false and then this and all other cases would work as expected.
> 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)
10 years, 2 months
[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 resolved TEIID-3899.
---------------------------------
Fix Version/s: 8.12.4
(was: 8.12.x)
Resolution: Done
Labels: 8.12.4 (was: )
> 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)
10 years, 2 months