October 2018 - teiid-issues - Jboss List Archives

[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... ] Work on TEIID-3617 started by Steven Hawkins. --------------------------------------------- > 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.x, Open To Community > > > 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 commented on TEIID-5503: --------------------------------------------- Here a good link that describe what DirectQuet is: * https://docs.microsoft.com/en-us/power-bi/desktop-use-directquery and: * https://docs.microsoft.com/en-us/power-bi/desktop-directquery-about * https://docs.microsoft.com/en-us/power-bi/desktop-use-directquery * https://docs.microsoft.com/en-us/power-bi/desktop-directquery-data-sources Regarding Custom ODBC Driver, From Microsoft Official Documentation, PowerBI fully support Custom ODBC Driver according to the following link: * 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 > 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 > > 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-4534) Querying 1-to-many relationship in JDG data source may return the wrong results

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-4534?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4534: --------------------------------------- @vhalbert Can this be marked as resolved, or does it still effect the infinispan translator? > Querying 1-to-many relationship in JDG data source may return the wrong results > ------------------------------------------------------------------------------- > > Key: TEIID-4534 > URL: https://issues.jboss.org/browse/TEIID-4534 > Project: Teiid > Issue Type: Bug > Components: JDG Connector > Affects Versions: 8.12.x, 9.2 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Critical > > When there is a 1-to-many relationship defined in a JDG schema, the results from querying the "many" relationship may return the wrong results. > Example: > Person --> Phone Numbers > INSERT INTO Person(id,name,email) VALUES (1,'name1','email1') > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234567'); > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234568'); > SELECT p.name, p.id, pn.number FROM Person p, PhoneNumber pn WHERE p.id=pn.id AND p.id=1 and number = '001234568' > or > Select * from PhoneNumber where number = '001234568' > return 2 rows, 1 for each phonenumber. > Why? Because JDG returns the Person object that meets those conditions. It doesn't filter the internal data to the Person object. Therefore, all phonenumbers are returned for the same person, generating a row for each. > This doesn't happen with 1-to-1 relationships because there's only ever 1 child object. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3927) Teiid Analytical Capabilities

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-3927?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3927. ----------------------------------- Fix Version/s: 11.2 (was: 11.x) Resolution: Done Marking as resolved with the outstanding subtask to make greater use of analytical platforms. No issue was captured for further improvements to our continuous query feature. > Teiid Analytical Capabilities > ----------------------------- > > Key: TEIID-3927 > URL: https://issues.jboss.org/browse/TEIID-3927 > Project: Teiid > Issue Type: Feature Request > Affects Versions: 9.x > Reporter: Kylin Soong > Assignee: Steven Hawkins > Priority: Major > Fix For: 11.2 > > > For the 9.x series goals include: > * Support for row counts beyond 2 billion TEIID-3601 > * Increased parallelism within the plan TEIID-4208 > * Increased windowing function support TEIID-5461 and related > * Improvements to the micro-batching / continuous query model -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3927) Teiid Analytical Capabilities

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-3927?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3927: ---------------------------------- Description: For the 9.x series goals include: * Support for row counts beyond 2 billion TEIID-3601 * Increased parallelism within the plan TEIID-4208 * Increased windowing function support TEIID-5461 and related * Improvements to the micro-batching / continuous query model was: For the 9.x series goals include: * Support for row counts beyond 2 billion TEIID-3601 * Increased parallelism within the plan TEIID-4208 * Increased windowing function support * Improvements to the micro-batching / continuous query model > Teiid Analytical Capabilities > ----------------------------- > > Key: TEIID-3927 > URL: https://issues.jboss.org/browse/TEIID-3927 > Project: Teiid > Issue Type: Feature Request > Affects Versions: 9.x > Reporter: Kylin Soong > Assignee: Steven Hawkins > Priority: Major > Fix For: 11.x > > > For the 9.x series goals include: > * Support for row counts beyond 2 billion TEIID-3601 > * Increased parallelism within the plan TEIID-4208 > * Increased windowing function support TEIID-5461 and related > * Improvements to the micro-batching / continuous query model -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2947) Implement ODBC cancel

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-2947?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2947: ---------------------------------- Fix Version/s: 11.2 (was: Open To Community) > Implement ODBC cancel > --------------------- > > Key: TEIID-2947 > URL: https://issues.jboss.org/browse/TEIID-2947 > Project: Teiid > Issue Type: Enhancement > Components: ODBC > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 11.2 > > > The ODBC cancel logic would take sending a different set of backend key data and recognizing a different set of initial message flow (as the cancel is issued in a separate connection). -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2947) Implement ODBC cancel

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-2947?page=com.atlassian.jira.plugin... ] Work on TEIID-2947 started by Steven Hawkins. --------------------------------------------- > Implement ODBC cancel > --------------------- > > Key: TEIID-2947 > URL: https://issues.jboss.org/browse/TEIID-2947 > Project: Teiid > Issue Type: Enhancement > Components: ODBC > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 11.2 > > > The ODBC cancel logic would take sending a different set of backend key data and recognizing a different set of initial message flow (as the cancel is issued in a separate connection). -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4155) Explore the possibility to use JBeret as materialization schedular

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-4155?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4155. ----------------------------------- Resolution: Won't Do Marking as won't do. I don't see a path forward jberet as we are actively trying to minimize our JEE integration. While it does support standalone integration, that doesn't seem to buy us much unless we want to promote seeing materialization or other work as full blown scheduled jobs. jberet is also not cluster aware. > Explore the possibility to use JBeret as materialization schedular > ------------------------------------------------------------------ > > Key: TEIID-4155 > URL: https://issues.jboss.org/browse/TEIID-4155 > Project: Teiid > Issue Type: Sub-task > Components: Server > Reporter: Ramesh Reddy > Priority: Major > > Right now the managed external materialization uses the our own very basic job scheduler, it would be nice if we can use JBeret batch processing system to automatically create jobs based on the materialization extension properties. > JBeret is JSR-352, looks simple enough to integrate. The advantages for us would be > - a standard scheduler, which will also work in "embedded" as this supposed to work in Java SE > - Gives CLI based management > - may be better metrics on time taken and error management -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3590) Provide $search extension to the OData V4 in Teiid

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-3590?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3590: ---------------------------------- Fix Version/s: 11.x > Provide $search extension to the OData V4 in Teiid > -------------------------------------------------- > > Key: TEIID-3590 > URL: https://issues.jboss.org/browse/TEIID-3590 > Project: Teiid > Issue Type: Feature Request > Components: OData > Affects Versions: 8.11 > Reporter: Tom Johnston > Assignee: Ramesh Reddy > Priority: Major > Fix For: 11.x > > > http://www.odata.org/getting-started/basic-tutorial/#select > > I am trying the following > > http://127.0.0.1:8080/odata/VDB1/Client1010_026V.Client_Check_History/?$s... > > It seems to return ALL data and disregard the ?$search= (which in this case I'd expect none) > > are there only portions of the odata protocol implemented?... or am I misunderstanding the odata.org link information -- 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 Debbie Steigner (Jira)

[ https://issues.jboss.org/browse/TEIID-5503?page=com.atlassian.jira.plugin... ] Debbie Steigner commented on TEIID-5503: ---------------------------------------- [~shawkins] Below is the customer's reply to your question: PostgreSQL ODBC native driver do not support DirectQuery, which a fundamental feature of PowerBI. ODBC extensions can optionally enable Direct Query mode, allowing Power BI to dynamically generate queries at runtime without pre-caching the user's data model. > 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 > > 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