January 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5627) Provide MongoDB source support

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIID-5627: ----------------------------------- Summary: Provide MongoDB source support Key: TEIID-5627 URL: https://issues.jboss.org/browse/TEIID-5627 Project: Teiid Issue Type: Feature Request Components: Teiid Spring Boot Reporter: Ramesh Reddy Assignee: Steven Hawkins Provide support for MongoDB source in Teiid Spring Bott using MongoDB Spring Boot starter {code} <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-data-mongodb</artifactId> </dependency> {code} and Teiid MongoDB translator -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5626) Support DDL based VDB

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIID-5626: ----------------------------------- Summary: Support DDL based VDB Key: TEIID-5626 URL: https://issues.jboss.org/browse/TEIID-5626 Project: Teiid Issue Type: Enhancement Components: Teiid Spring Boot Reporter: Ramesh Reddy Assignee: Steven Hawkins Support DDL based VDB for deployment in the Teiid Spring Boot. Consider moving the internal mechanics of building the dynamic VDB on API based schema object rather than Admin based objects. This could be a little messy to weed out. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5625) Move Teiid Spring Boot to use Spring Boot 2.1.x

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIID-5625: ----------------------------------- Summary: Move Teiid Spring Boot to use Spring Boot 2.1.x Key: TEIID-5625 URL: https://issues.jboss.org/browse/TEIID-5625 Project: Teiid Issue Type: Task Components: Teiid Spring Boot Reporter: Ramesh Reddy Assignee: Ramesh Reddy Move current 1.5.x version of the spring boot Teiid to new Spring Boot version 2.1.2. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5620) Provide flattened jmx metrics

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5620?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5620: --------------------------------------- Other events that could be tracked as metrics for the purpose of alerting and dynamic adjustment: * running 3 pass sorts - if there are no other memory / queuing issues it would imply that max active plans should smaller * requests with full output buffers - indicates that the clients are initiating large queries then lagging the server output > Provide flattened jmx metrics > ----------------------------- > > Key: TEIID-5620 > URL: https://issues.jboss.org/browse/TEIID-5620 > Project: Teiid > Issue Type: Quality Risk > Components: Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > Providing JMX metrics via jolokia to Prometheus does not work well with complex types. We are providing several metric sets - engine stats, worker pool stats, requests, etc. as beans which needs to be flattened. Simple parameters are ok to the metrics methods, but simple results are required. > We need to make sure that at least statistics are available on: > * number of plans waiting to be processed - this will be a primary metric for determining horizontal scale out > * amount /%of buffer memory used - this will be a primary metric for determining if pods need to be allocated with more memory/disk > Ideally alerting could be available on percent utilization - but we could also add a metric such as out of disk count to provide a hard count of exceptional conditions. > It's assumed that cpu utilization will be monitored from the pod itself - which will be a primary metric for determining if pods should be allocated with more cpu resources. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5588) Please add support for earlyRequest feature which is for example used in the OpenUI5 library to enhance performance in single page apps

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5588?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-5588: ------------------------------------- Component/s: OData Fix Version/s: Open To Community Assignee: (was: Steven Hawkins) > Please add support for earlyRequest feature which is for example used in the OpenUI5 library to enhance performance in single page apps > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-5588 > URL: https://issues.jboss.org/browse/TEIID-5588 > Project: Teiid > Issue Type: Enhancement > Components: OData > Affects Versions: 11.2.1 > Reporter: Christoph John > Priority: Optional > Fix For: Open To Community > > > As discussed in https://issues.jboss.org/browse/TEIID-5545 OpenUI5 implements a earlyRequest feature to preload metadata information from an odata v4 service. It would be great if support for this could be added to Teiid/Widlfly. > Thomas Chadzelek, who I assume is a lead developer for the odata v4 model at SAP kindly provided the following information and offered his support in case further questions arise: > The "earlyRequests" parameter is pretty simple. It will send GET requests for /$metadata and all annotation XML files (see parameter "annotationURI"). It will also send a HEAD request to with header "X-CSRF-Token" : "Fetch" in order to fetch the security token. If Teiid/Olingo does not implement CSRF protection by requiring such a header, there should be no need to properly answer the HEAD request at all. Else it would be nice to return the right CSRF token value in the response's headers. > Please see Cross-Site Request Forgery Protection and Gateway protection against Cross-Site Request Forgery attacks for some background infos. > For further questions you can contact him directly by joining the discussion at: > https://github.com/SAP/openui5/issues/2288 > Thanks a lot. Let we know if I can support with testing. > Best regards, > Christoph -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2957) MongoDB: Implement transaction handling

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-2957?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2957. ----------------------------------- Resolution: Done Updated the docs, java docs for createDataSource, and release notes to cover adding a mongodb with local transaction support. > MongoDB: Implement transaction handling > --------------------------------------- > > Key: TEIID-2957 > URL: https://issues.jboss.org/browse/TEIID-2957 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.5 > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > With 4.x mongodb running in a replica set the latest client drivers expose methods that allow for the implementation of local transactions in jca. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2957) MongoDB: Implement transaction handling

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-2957?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2957: ---------------------------------- Description: With 4.x mongodb running in a replica set the latest client drivers expose methods that allow for the implementation of local transactions in jca. (was: Based on Narayana transaction manager, which is the TM that JBoss EAP TM based on one can build compensating transactions over MongoDB https://github.com/jbosstm/quickstart/blob/master/compensating-transactio... https://plus.google.com/wm/1/events/cnbaif9aiiaarnjtd047nt1pksc Need to see the version number matches then need to buiild the necessary framework around mongodb translator ) Summary: MongoDB: Implement transaction handling (was: MongoDB: Implement Compensating transactions) > MongoDB: Implement transaction handling > --------------------------------------- > > Key: TEIID-2957 > URL: https://issues.jboss.org/browse/TEIID-2957 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.5 > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > With 4.x mongodb running in a replica set the latest client drivers expose methods that allow for the implementation of local transactions in jca. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5618) clientHostName always reported as localhost via JDBC connection

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5618?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5618. ----------------------------------- Fix Version/s: 12.1 Resolution: Done Added async resolution on the client side. By default we'll only attempt to get the host name for 100 milliseconds, then just use "unknown" - rather than "localhost". ODBC for now will always use unknown. > clientHostName always reported as localhost via JDBC connection > --------------------------------------------------------------- > > Key: TEIID-5618 > URL: https://issues.jboss.org/browse/TEIID-5618 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.12.16.6_4 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > VDB session information in the Management Console and logs shows localhost for Client Host Name with a JDBC connection. > Client Host Name: localhost > Client Hardware Address: 4CBB58502284 > IP Address: > Security Domain: teiid-security > In the server.log with org.teiid set to TRACE it displays below for session: > DEBUG [org.teiid.SECURITY] (New I/O worker #2) Logon successful, created session: sessionid=DW9hzUw5P1ob; userName=teiidUser@teiid-security; vdbName=deb_pg; vdbVersion=2; createdTime=Thu Jan 17 08:15:44 CST 2019; applicationName=JDBC; clientHostName=localhost; clientHardwareAddress=4CBB58502284; IPAddress=192.168.x.x; securityDomain=teiid-security; lastPingTime=Thu Jan 17 08:15:44 CST 2019 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5624) Implement LO function support for pg/ODBC

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5624: ------------------------------------- Summary: Implement LO function support for pg/ODBC Key: TEIID-5624 URL: https://issues.jboss.org/browse/TEIID-5624 Project: Teiid Issue Type: Feature Request Components: ODBC Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 12.x The current logic maps lobs to bytea and text types and caps their length by default to 2MB. We should add actual lob support using the LO functions. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5504) Update pg layer for general fdw use

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5504?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5504: --------------------------------------- Another eventual goal would be to just reuse the pg metadata system. That is via the fdw import all of the teiid constructs then any metadata query would be redirected to the pg instance. We need to valid procedures, function, and other import at a minimum. Beyond that if we want metadata visibility to apply then pg role functions need to be aware of the teiid role information. > Update pg layer for general fdw use > ----------------------------------- > > Key: TEIID-5504 > URL: https://issues.jboss.org/browse/TEIID-5504 > Project: Teiid > Issue Type: Enhancement > Components: ODBC > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.x > > > Building on TEIID-5498 we should allow general use of fdw access. This is much broader in determining what function and type support is expected. At the very least type casting needs to be aware of the pg type names as a literal like 'a' will be pushed as 'a'::text. > At this time since joins and other higher level constructs are not pushed that still keeps the scope somewhat narrow. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2019