[JBoss JIRA] (TEIID-3608) Add a translator for memcached
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3608?page=com.atlassian.jira.plugin... ]
Ramesh Reddy reassigned TEIID-3608:
-----------------------------------
Assignee: (was: Ramesh Reddy)
> Add a translator for memcached
> ------------------------------
>
> Key: TEIID-3608
> URL: https://issues.jboss.org/browse/TEIID-3608
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Affects Versions: 8.12
> Reporter: Kylin Soong
> Fix For: 9.x
>
>
> memcached can be thought as a standard in Cache area, there are lots of product support memcached, like:
> * Infinispan/JBoss Data Grid
> * Redis
> * Oracle Coherence
> * Cassandra
> * ...
> If we have a memcached translator, it will more flexible in intergrate/transfer data from cache product.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (TEIID-57) Criteria ordering
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-57?page=com.atlassian.jira.plugin.s... ]
Ramesh Reddy commented on TEIID-57:
-----------------------------------
Is this still applicable?
> Criteria ordering
> -----------------
>
> Key: TEIID-57
> URL: https://issues.jboss.org/browse/TEIID-57
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 9.x
> Reporter: Steven Hawkins
>
> Defect Tracker #24194: The order in which criteria is evaluated in MetaMatrix (and at the source) can have a large impact on performance. We should utilize costing information to order our evaluation of criteria nodes so that the cheapest most limiting criteria is evaluated first.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (TEIID-3872) Error with odata entity create with generated keys
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3872?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3872.
-----------------------------------
Fix Version/s: 9.0
8.12.5
8.13.2
(was: 8.13)
(was: 8.12.4)
Resolution: Done
The initial commit was incomplete. This one corrects:
that oracle should be marked as needing to use the column names to get the generated keys
ensured that generated keys were retrieved for both prepared and non prepared queries
ensured that generated keys were retrieved for preparedstatement.execute
> Error with odata entity create with generated keys
> --------------------------------------------------
>
> Key: TEIID-3872
> URL: https://issues.jboss.org/browse/TEIID-3872
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector, Query Engine
> Environment: MacOS X El Capitan, Teiid 8.12.2, Jbossdev studio, Oracle 11g
> Reporter: Ivan Lucas Vargas
> Assignee: Steven Hawkins
> Fix For: 9.0, 8.12.5, 8.13.2
>
>
> Forum thread: https://developer.jboss.org/message/947527
> When trying to insert a record thru odata2 request when the ID field is mapped as an Oracle Sequence as described in the documentation as *<element name>:SEQUENCE=<sequence name>.<sequence value> *(https://docs.jboss.org/author/display/teiid812final/Oracle+Translator), the following error occurs:
> TEIID16013 Error occurred producing OData result.: java.lang.IllegalArgumentException: Cannot infer EdmType for java type: oracle.sql.ROWID
> at org.odata4j.core.OProperties.simple(OProperties.java:40) [odata-core-0.8.10.jar:0.8.10]
> at org.teiid.odata.ODataSQLBuilder.buildEntityKey(ODataSQLBuilder.java:678) [classes:]
> at org.teiid.odata.TeiidProducer.createEntity(TeiidProducer.java:232) [classes:]
> at org.odata4j.producer.resources.EntitiesRequestResource.createEntity(EntitiesRequestResource.java:129) [odata-core-0.8.10.jar:0.8.10]
> at org.odata4j.producer.resources.EntitiesRequestResource.createEntity(EntitiesRequestResource.java:116) [odata-core-0.8.10.jar:0.8.10]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_45]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_45]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_45]
> at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_45]
> at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:168) [resteasy-jaxrs-2.3.9.Final-redhat-7.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:269) [resteasy-jaxrs-2.3.9.Final-redhat-7.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227) [resteasy-jaxrs-2.3.9.Final-redhat-7.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:216) [resteasy-jaxrs-2.3.9.Final-redhat-7.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:541) [resteasy-jaxrs-2.3.9.Final-redhat-7.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:523) [resteasy-jaxrs-2.3.9.Final-redhat-7.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:125) [resteasy-jaxrs-2.3.9.Final-redhat-7.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.9.Final-redhat-7.jar:]
> 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.5.3.Final.jar:7.5.3.Final]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:512) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.5.0.Final-redhat-15.jar:7.5.0.Final-redhat-15]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:150) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:344) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:854) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_45]
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (TEIID-3837) AS400 deployVDB
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3837?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-3837.
---------------------------------
Resolution: Rejected
No new information is presented as to why it takes long. Typically by adjusting the "import" properties on the model you can filter out what are needed.
> AS400 deployVDB
> ---------------
>
> Key: TEIID-3837
> URL: https://issues.jboss.org/browse/TEIID-3837
> Project: Teiid
> Issue Type: Feature Request
> Reporter: Mark Tawk
> Assignee: Steven Hawkins
>
> I'm using Teiid 8.11.3 and db2i translator,
> I'm connecting to an AS400 DB containing around 1000 tables, the deployvdb remained running for 2 hours and it did not finish.
> Is there a way to speed up the deployvdb treatment? or to know more details on the vdb deployment progress?
> I'm able to fetch the DB information schema via a jdbc connection and it is not taking that much time.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (TEIID-3005) Support Kerberos pass-thru to the data source
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3005?page=com.atlassian.jira.plugin... ]
Ramesh Reddy reassigned TEIID-3005:
-----------------------------------
Assignee: Van Halbert
> Support Kerberos pass-thru to the data source
> ---------------------------------------------
>
> Key: TEIID-3005
> URL: https://issues.jboss.org/browse/TEIID-3005
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 8.7.1
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Critical
>
> Need to add support for Kerberos authentication pass-thru all the way to the data source, for data sources that support Kerberos, of course. Besides relational data sources, could it also support Cloudera Hadoop Distribution.
> This maybe a duplicate of other pass-thru related jira's, but wasn't sure, so I logged this to at least get confirmation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (TEIID-3968) OData 4 array type handling
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3968?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3968:
-------------------------------------
The above upstream JIRAs are fixed in 4.2.0 version. I am going to make this a sub-ask of TEIID-3932
> OData 4 array type handling
> ---------------------------
>
> Key: TEIID-3968
> URL: https://issues.jboss.org/browse/TEIID-3968
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
>
> To ensure we are appropriate returning the correct error messages, creating the right upstream changes, etc. we have several paths to validate wrt array handling. There are:
> In the translator - ODataProcedureExecution.getQueryParameters, ODataFilterVisitor.visit(Function) and ODataFilterVisitor.visit(ColumnReference), ODataExpressionToSQLVisitor.visitAlias, ODataUpdateVisitor.visit(Update)
> In the OData service - ODataExpressionToSQLVisitor.visit(Alias)
> From the spec it appears that a uri should be able to specify arrays, but olingo and other frameworks may have limitations. For example it should be possible to have an array argument to a function, but the olingo framework will complain that arrays are not allowed in the resource part of the uri.
> At the very least we'll capture what won't work with this issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (TEIID-3968) OData 4 array type handling
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3968?page=com.atlassian.jira.plugin... ]
Ramesh Reddy updated TEIID-3968:
--------------------------------
Parent: TEIID-3932
Issue Type: Sub-task (was: Bug)
> OData 4 array type handling
> ---------------------------
>
> Key: TEIID-3968
> URL: https://issues.jboss.org/browse/TEIID-3968
> Project: Teiid
> Issue Type: Sub-task
> Components: OData
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
>
> To ensure we are appropriate returning the correct error messages, creating the right upstream changes, etc. we have several paths to validate wrt array handling. There are:
> In the translator - ODataProcedureExecution.getQueryParameters, ODataFilterVisitor.visit(Function) and ODataFilterVisitor.visit(ColumnReference), ODataExpressionToSQLVisitor.visitAlias, ODataUpdateVisitor.visit(Update)
> In the OData service - ODataExpressionToSQLVisitor.visit(Alias)
> From the spec it appears that a uri should be able to specify arrays, but olingo and other frameworks may have limitations. For example it should be possible to have an array argument to a function, but the olingo framework will complain that arrays are not allowed in the resource part of the uri.
> At the very least we'll capture what won't work with this issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month