June 2020 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4163) Swagger: Add support for File and Map based proeprties

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-4163?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-4163: ---------------------------------- Fix Version/s: Backlog Open To Community > Swagger: Add support for File and Map based proeprties > ------------------------------------------------------ > > Key: TEIID-4163 > URL: https://issues.redhat.com/browse/TEIID-4163 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 9.0 > Reporter: Ramesh Reddy > Priority: Major > Fix For: Backlog, Open To Community > > > The support for File and Map properties is not currently supported, thus it does not support any multi-part payloads. > IMO, Teiid can handle the File types as Blobs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4559) Support for SAP Variables to enable accessing multi-cubes

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-4559?page=com.atlassian.jira.plugi... ] Steven Hawkins reassigned TEIID-4559: ------------------------------------- Fix Version/s: Backlog Open To Community Assignee: (was: Edwin Jones) > Support for SAP Variables to enable accessing multi-cubes > --------------------------------------------------------- > > Key: TEIID-4559 > URL: https://issues.redhat.com/browse/TEIID-4559 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 9.2 > Reporter: Van Halbert > Priority: Major > Fix For: Backlog, Open To Community > > > When there is OLAP with multi-cubes, we can't currently handle the data stream back.. Because we are currently using olap4j for our MDX support, we run into issues since SAP has proprietery extensions to the MDX language called SAP Variables that we need to support. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4219) Support variable and Parameters in HANA Translator

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-4219?page=com.atlassian.jira.plugi... ] Steven Hawkins reassigned TEIID-4219: ------------------------------------- Fix Version/s: Backlog Open To Community Assignee: (was: Edwin Jones) > Support variable and Parameters in HANA Translator > -------------------------------------------------- > > Key: TEIID-4219 > URL: https://issues.redhat.com/browse/TEIID-4219 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.13.4 > Reporter: Edwin Jones > Priority: Major > Fix For: Backlog, Open To Community > > > •Variables: > > A Variable can be specified before executing a query on the view. Usually variable values are entered manually by the user on a UI (variable popup). A variable defines a filter on an attribute of the view. Therefore it always has to be assigned to an attribute. The variable values are passed to the engine via the WHERE clause of the SQL statement. Variables are not known by the engine, but only by the clients like Datapreview, MDX, Advanced Analysis for Office or BO Explorer. It is the task of the client to convert the user input into the WHERE clause when accessing the data. > > •Parameters or Input Parameters: > > A parameter (like a variable) can be specified before executing a query on the view. Usually parameter values are entered manually by the user on a UI (variable popup). A Parameter defines an internal parameterization of the view. This means the engine needs to know it and uses the parameter value during the execution (e.g. to calculate a formula for a calculated measure). The parameter value is passed to the engine via the PLACEHOLDER clause of the SQL statement. A parameter can only have single values. For the end user there is no distinction between variables and parameters. Both appear as input fields on the variable popup. > > ------------------ > > There are 4 system tables under the schema _SYS_BI which contains information about Variables. > · BIMC_VARIABLE > · BIMC_VARIABLE_ASSIGNMENT > · BIMC_VARIABLE_VIEW > · BIMC_VARIABLE_VALUE > > SAP HANA documentation on Input parameters: http://help.sap.com/saphelp_hanaplatform/helpdata/en/d5/c8230abb571014acc... > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2139) Factor out common table expressions

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-2139?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-2139. ----------------------------------- Resolution: Deferred Marking as deferred as this has been open too long. > Factor out common table expressions > ----------------------------------- > > Key: TEIID-2139 > URL: https://issues.redhat.com/browse/TEIID-2139 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Mark Addleman > Assignee: Steven Hawkins > Priority: Major > > Query planner should factor out common table expressions within queries so they are only executed once. See https://community.jboss.org/message/742355 for more context. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5211) Allow ability to forward-engineer into underlying data stores

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5211?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5211: ---------------------------------- Fix Version/s: Backlog > Allow ability to forward-engineer into underlying data stores > ------------------------------------------------------------- > > Key: TEIID-5211 > URL: https://issues.redhat.com/browse/TEIID-5211 > Project: Teiid > Issue Type: Enhancement > Components: Connector API > Reporter: Don Krapohl > Assignee: Steven Hawkins > Priority: Major > Fix For: Backlog > > > As a platform I am better able to better engineer my underlying data stores starting with a virtual model. > Please add the ability to create, alter, and drop schema objects and relationahips (DDL) in underlying data sources. Example, if I design a source in Teiid Designer I may wish to have Teiid do the DDL against the underlying data source(s). This allows better abstraction an portability of the data model. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4647) Add Kerberos support to the MongoDB

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-4647?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-4647. ----------------------------------- Resolution: Deferred Marking as deferred. We can revisit this if we circle back to kerberos support in teiid spring boot. > Add Kerberos support to the MongoDB > ------------------------------------ > > Key: TEIID-4647 > URL: https://issues.redhat.com/browse/TEIID-4647 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 9.2 > Reporter: Van Halbert > Priority: Major > > Add support for kerberos in MongoDB resource adapter. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5951) Required Cloud Database list supported by Teiid Wildfly 11.1.2

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5951?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-5951. ----------------------------------- Resolution: Explained See the data sources list: http://teiid.github.io/teiid-documents/11.1.x/content/reference/Data_Sour... Anything that isn't specifically listed may be supported if it the same as a standard db, just in a cloud environment - like amazon rds. And almost anything will have basic support via a jdbc driver with either the jdbc-ansi or jdbc-simple support. > Required Cloud Database list supported by Teiid Wildfly 11.1.2 > -------------------------------------------------------------- > > Key: TEIID-5951 > URL: https://issues.redhat.com/browse/TEIID-5951 > Project: Teiid > Issue Type: Feature Request > Reporter: Geetika Kolli > Assignee: Steven Hawkins > Priority: Major > > Hi Team, > Could you please provide the list of Cloud Database supported by Teiid Wildfly 11.1.2 version. > Also, can you please share the documents/reference link to integrate those database. > Thanks, > Geetika -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5958) Need support Owner and Parent constructions

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5958?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5958: ---------------------------------- Fix Version/s: Backlog > Need support Owner and Parent constructions > -------------------------------------------- > > Key: TEIID-5958 > URL: https://issues.redhat.com/browse/TEIID-5958 > Project: Teiid > Issue Type: Task > Components: Salesforce Connector > Reporter: Renat Eskenin > Assignee: Steven Hawkins > Priority: Major > Fix For: Backlog > > > We have salesforce requests as: > select > vlic_Contract__r.Account.*Owner*.Email, > vlic_Contract__r.Account.*Parent*.Email > from > Product_License__c > Need to support Owner and Parent SOQL keys in teiid sql or another method to call this requests -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5902) Support reading from AVRO, Paraquet file formats

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5902?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5902: ---------------------------------- Fix Version/s: 15.0 > Support reading from AVRO, Paraquet file formats > ------------------------------------------------ > > Key: TEIID-5902 > URL: https://issues.redhat.com/browse/TEIID-5902 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Ramesh Reddy > Priority: Major > Fix For: 15.0 > > > The idea of this issue is to extend the support for Apache AVRO, Apache Parquet files on HDFS or in any other store. > The Serializers and deserializers for these are already defined https://docs.aws.amazon.com/athena/latest/ug/avro.html and https://docs.aws.amazon.com/athena/latest/ug/parquet.html > Teiid has a concept called a Translator, one needs to write a new translator(s) for above where they need to use these SerDes from these links and convert the data. > Knowledge prerequisite: Java, Spring Boot > Github repo: https://github.com/teiid > Skill level: Intermediate -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5965) Allow variables to be used as TextTable delimeters, row delimeters, quote, header, skip rows, and escape characters

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5965?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5965: ---------------------------------- Fix Version/s: 15.0 Original Estimate: 5 hours Remaining Estimate: 5 hours Story Points: 1 In total you are requesting delimiter, header and skip be parameterizable. That is possible. I think the initial rationale for static values was for easier usage / analysis in Teiid Designer. > Allow variables to be used as TextTable delimeters, row delimeters, quote, header, skip rows, and escape characters > ------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-5965 > URL: https://issues.redhat.com/browse/TEIID-5965 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 13.1 > Reporter: Dmitrii Pogorelov > Assignee: Steven Hawkins > Priority: Major > Fix For: 15.0 > > Original Estimate: 5 hours > Remaining Estimate: 5 hours > > In the specified example, the delimiter is TAB. Many web APIs allow customization of the delimiter character, and in order to provide a generic parser, sometimes it is way easier to define a delimiter as a variable, and not need to create a long nested structure with IF-THEN-ELSE-IF-ELSE constructs: > {code:sql} > Select * From TextTable ( > 'c1 c2 > 1 2' > Columns > c1 integer, > c2 integer > Delimiter E'\t' > Header 1 > )x; > {code} > Imagine that based on setup on API side (out of our control) the content can be delivered via tab or semicolon, e.g. > {code} > c1;c2 > 1;2 > {code} > or > {code} > c1 c2 > 1 2 > {code} > Let's save this response into a variable and see the code, which we will need to write depending on the setup: > {code:sql} > Begin > ... > If (delimiter = 'tab') > Begin > Select * From TextTable ( > apiResponse > Columns > c1 integer, > c2 integer > Delimiter E'\t' > Header 1 > )x; > End > Else If (delimiter = 'tab') > Begin > Select * From TextTable ( > apiResponse > Columns > c1 integer, > c2 integer > Delimiter ';' > Header 1 > )x; > End > End > {code} > The if-else block is constantly growing, especially if we want to customize quote, escape, delimiter, and row delimiter. > Thus it would be great if we could make these values configurable. In this case, we could end up with this expected code, which is more readable and more easily customizable: > {code:sql} > Begin > ... > Declare string delimiter = E'\t'; > Select * From TextTable ( > apiResponse > Columns > c1 integer, > c2 integer > Delimiter delimiter > Header 1 > )x; > End > {code} > With a bit of tweaking and certain assumptions, leading in the trust level, we can even read the first line and try to auto-detect the delimiter automatically (e.g. by counting tabs, commas, and semicolons in the first line). > Please, could you be so kind as to make HEADER and SKIP values customizable (rather than hardcoded numbers)? -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2020