October 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4251) Built in support for Postgres DB as materialization target

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-4251?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4251: --------------------------------------- I'm trying to avoid using the allow-materialization-management construct in order to remove the need for an explicit status table or mvstatus function usage. To do that though requires some code modifications if any of the materialization scripts will still be run even if allow management is turned off. The other approach is to leave teiid out of it as much as possible. With the pg container include a create script: CREATE EXTENSION postgres_fdw; CREATE SERVER teiid_server ...; CREATE USER MAPPING FOR pg_user ...; -- for each schema with a materialized view CREATE SCHEMA remote_schema ...; IMPORT FOREIGN SCHEMA remote_schema (limit to all materializations in the schema) ...; -- for each materialized view in the schema CREATE MATERIALIZED VIEW xxx_mat AS SELECT * FROM remote_schema.xxx OPTION NO CACHE WITH NO DATA; create key / index information on xxx_mat ... By specifying option no cache we avoid having to worry about any load order and can concurrently load all. There would then need to be an initial load set of scripts, REFRESH MATERIALIZED VIEW xxx_mat; And a set of refresh scripts (with the concurrent option only against materialized views that have a unique key): REFRESH MATERIALIZED VIEW CONCURRENTLY xxx_mat; These could be run off of cron jobs, which could also be associated with the pg container image. > Built in support for Postgres DB as materialization target > ---------------------------------------------------------- > > Key: TEIID-4251 > URL: https://issues.jboss.org/browse/TEIID-4251 > Project: Teiid > Issue Type: Sub-task > Components: Server > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 11.2 > > > If Postgres database is available along with install or assumed that it is available, then some of the materialization task can be automated, like > - Creation of a common STATUS table > - Creation of the materilization targets (create views on dbms) > - On load, on undeploy and load scripts for all the materialization views > We need to device a way this to be pluggable, such that based on success of this, we can provide additional support for other sources. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3617) Provide an option to Limit per user based connections

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-3617?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3617. ----------------------------------- Resolution: Done Added logic for a max-sessions-per-user vdb property to limit the number of sessions per user for a given vdb/teiid server. This is enforced by scanning all sessions. If needed tracking per user can be added, but given that sessions are created infrequently and the total number of sessions should be relatively modest this is fine for now. > Provide an option to Limit per user based connections > ----------------------------------------------------- > > Key: TEIID-3617 > URL: https://issues.jboss.org/browse/TEIID-3617 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Xian Liu > Assignee: Steven Hawkins > Priority: Major > Fix For: 11.2 > > > we deploy teiid for users to get data, but some users will create many connections to teiid and they are not necessary, I need to find a good way to limit each user account can only get like 50 connections or so -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5473) Make JDBCMetadataProcessor more extensible with protected methods

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5473?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5473. ----------------------------------- Resolution: Done Marking as resolved for 11.2 as there haven't been additional requests for api changes. Ken, is there a patch release(s) you are looking for this in as well? > Make JDBCMetadataProcessor more extensible with protected methods > ----------------------------------------------------------------- > > Key: TEIID-5473 > URL: https://issues.jboss.org/browse/TEIID-5473 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector > Affects Versions: 11.1 > Reporter: Ken Geis > Assignee: Steven Hawkins > Priority: Major > Fix For: 11.2 > > > I believe I can write a JDBCMetadataProcessor that works faster against my Oracle database. The important part to override is in getIndexes(..). This method is package-private, so I cannot override it. It would be useful to me if the method (and maybe others) were made protected so that they can be overridden. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5503) Create or change ODBC driver to be compatible with Microsoft Power BI

by Andrea Modesto Rossi (Jira)

[ https://issues.jboss.org/browse/TEIID-5503?page=com.atlassian.jira.plugin... ] Andrea Modesto Rossi edited comment on TEIID-5503 at 10/12/18 11:46 PM: ------------------------------------------------------------------------ PowerBI supports both ODBC and Odata connection method (as per [1] )meaning that there is a basic integration that already works out of the box. Regardless the Driver, PowerBI supports 2 connection methods [2]: # Import # DirectQuery Both ODBC and Odata are 100% compliant with method 1), but neither ODBC nor Odata works in DirectQuery mode [3]. One Option, and this is the RFE goal, is to extend the capability of the existing ODBC driver according to Microsoft GuideLine: * https://docs.microsoft.com/en-us/power-query/odbc * https://github.com/Microsoft/DataConnectors * https://github.com/Microsoft/DataConnectors/blob/master/docs/m-extensions.md Moreover, it will be really usefull to turn Custom ODBC Driver into a certified Driver that will appear in PowerBI Menu:: Get Data :: DataBase. *Having a CustomDriver [4] is not a solution for Enterprise * Hope this can help. --- [1] https://docs.microsoft.com/en-us/power-bi/desktop-data-sources [2] https://docs.microsoft.com/en-us/power-bi/desktop-directquery-about [3] https://docs.microsoft.com/en-us/power-bi/desktop-directquery-data-sources [4] https://docs.microsoft.com/en-us/power-query/startingtodevelopcustomconne... (Restricted to jira-users group) was (Author: amrossi): PowerBI supports both ODBC and Odata connection method (as per [1] )meaning that there is a basic integration that already works out of the box. Regardless the Driver, PowerBI supports 2 connection methods [2]: # Import # DirectQuery Both ODBC and Odata are 100% compliant with method 1), both neither ODBC nor Odata works in DirectQuery mode [3]. One Option, and this is the RFE goal, is to extend the capability of the existing ODBC driver according to Microsoft GuideLine: * https://docs.microsoft.com/en-us/power-query/odbc * https://github.com/Microsoft/DataConnectors * https://github.com/Microsoft/DataConnectors/blob/master/docs/m-extensions.md Moreover, it will be really usefull to turn Custom ODBC Driver into a certified Driver that will appear in PowerBI Menu:: Get Data :: DataBase. *Having a CustomDriver [4] is not a solution for Enterprise * Hope this can help. --- [1] https://docs.microsoft.com/en-us/power-bi/desktop-data-sources [2] https://docs.microsoft.com/en-us/power-bi/desktop-directquery-about [3] https://docs.microsoft.com/en-us/power-bi/desktop-directquery-data-sources [4] https://docs.microsoft.com/en-us/power-query/startingtodevelopcustomconne... (Restricted to jira-users group) > Create or change ODBC driver to be compatible with Microsoft Power BI > --------------------------------------------------------------------- > > Key: TEIID-5503 > URL: https://issues.jboss.org/browse/TEIID-5503 > Project: Teiid > Issue Type: Feature Request > Components: ODBC > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Priority: Major > Attachments: qs-connect-data_02.png, qs-connect-data_03.png > > > Customer request to customise the ODBC driver, adding extra feature as reported here: https://docs.microsoft.com/en-us/power-query/odbc -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3907) Support compensating transactions for updatable non-XA sources

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-3907?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3907: ---------------------------------- Fix Version/s: 11.x (was: 11.2) > Support compensating transactions for updatable non-XA sources > -------------------------------------------------------------- > > Key: TEIID-3907 > URL: https://issues.jboss.org/browse/TEIID-3907 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Major > Fix For: 11.x > > > The transaction manager will fully support xa with all xa sources and a single local transaction resource. Beyond that however there is no built-in support for compensating transactions with non-XA sources. There has been work in Narayana on compensating transactions though that could be used by custom web apps consuming Teiid. We would like to eventually offer compensating options for some of our updatable non-XA sources, but it hasn't had sufficient priority yet. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5506) Remove the option of using qualified logins entirely

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5506?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5506. ----------------------------------- Fix Version/s: 11.2 Resolution: Done Removed the backwards compatibility flag. > Remove the option of using qualified logins entirely > ---------------------------------------------------- > > Key: TEIID-5506 > URL: https://issues.jboss.org/browse/TEIID-5506 > Project: Teiid > Issue Type: Quality Risk > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 11.2 > > > The backwards compatibility flag from TEIID-4442 should be removed as the feature has not been operational for some time. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5344) Fully manage the creation of materialization status tables

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5344?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5344: ---------------------------------- Fix Version/s: 11.x (was: 11.2) Given the potential prioritization of the built-in pg materialization approach, we can put off developing a general solution here. > Fully manage the creation of materialization status tables > ---------------------------------------------------------- > > Key: TEIID-5344 > URL: https://issues.jboss.org/browse/TEIID-5344 > Project: Teiid > Issue Type: Sub-task > Components: Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 11.x > > > Status tables should be created if needed on the deployment of a vdb. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3617) Provide an option to Limit per user based connections

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-3617?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3617: ---------------------------------- Fix Version/s: 11.2 (was: Open To Community) (was: 11.x) > Provide an option to Limit per user based connections > ----------------------------------------------------- > > Key: TEIID-3617 > URL: https://issues.jboss.org/browse/TEIID-3617 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Xian Liu > Assignee: Steven Hawkins > Priority: Major > Fix For: 11.2 > > > we deploy teiid for users to get data, but some users will create many connections to teiid and they are not necessary, I need to find a good way to limit each user account can only get like 50 connections or so -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5503) Create or change ODBC driver to be compatible with Microsoft Power BI

by Andrea Modesto Rossi (Jira)

[ https://issues.jboss.org/browse/TEIID-5503?page=com.atlassian.jira.plugin... ] Andrea Modesto Rossi updated TEIID-5503: ---------------------------------------- Attachment: qs-connect-data_03.png > Create or change ODBC driver to be compatible with Microsoft Power BI > --------------------------------------------------------------------- > > Key: TEIID-5503 > URL: https://issues.jboss.org/browse/TEIID-5503 > Project: Teiid > Issue Type: Feature Request > Components: ODBC > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Priority: Major > Attachments: qs-connect-data_02.png, qs-connect-data_03.png > > > Customer request to customise the ODBC driver, adding extra feature as reported here: https://docs.microsoft.com/en-us/power-query/odbc -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5503) Create or change ODBC driver to be compatible with Microsoft Power BI

by Andrea Modesto Rossi (Jira)

[ https://issues.jboss.org/browse/TEIID-5503?page=com.atlassian.jira.plugin... ] Andrea Modesto Rossi updated TEIID-5503: ---------------------------------------- Attachment: qs-connect-data_02.png > Create or change ODBC driver to be compatible with Microsoft Power BI > --------------------------------------------------------------------- > > Key: TEIID-5503 > URL: https://issues.jboss.org/browse/TEIID-5503 > Project: Teiid > Issue Type: Feature Request > Components: ODBC > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Priority: Major > Attachments: qs-connect-data_02.png, qs-connect-data_03.png > > > Customer request to customise the ODBC driver, adding extra feature as reported here: https://docs.microsoft.com/en-us/power-query/odbc -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2018