June 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3560) support common table expression with insert/update/delete

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3560?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3560: ---------------------------------- Fix Version/s: 11.1 (was: 11.0) > support common table expression with insert/update/delete > --------------------------------------------------------- > > Key: TEIID-3560 > URL: https://issues.jboss.org/browse/TEIID-3560 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Fix For: 11.1 > > > We currently have limited our cte support to just query expressions. This should be generalized to more statement types. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5343) Enable absolute URI on context definition of EntitySets when using ODATA

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-5343?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5343: ------------------------------------- This does require a change in Olingo library. Added https://issues.apache.org/jira/browse/OLINGO-1271 > Enable absolute URI on context definition of EntitySets when using ODATA > ------------------------------------------------------------------------ > > Key: TEIID-5343 > URL: https://issues.jboss.org/browse/TEIID-5343 > Project: Teiid > Issue Type: Enhancement > Components: OData > Affects Versions: 10.2.1 > Reporter: Rafael Sampaio > Assignee: Ramesh Reddy > Fix For: 11.0 > > > Hi all you TEIID guys. > As reported on [OLINGO-1025|https://issues.apache.org/jira/browse/OLINGO-1025], integrating to MS OData consumers (ie. PowerBI/PowerQuery) gives the "should be an absolute Uri" error. > The proposed solution in the JIRA is implementing a Processor for any given EntityType. Browsing through the code i see TEIID uses the ServiceHandler approach, instead of processor and it also has a Custom JSON Odata Serializer. > I see that the Default JSON serializer, when serializing entity collections uses the ContextURL to generate the context metadata for the EntityCollection, but by default it does not contain the service root, since it comes from static DataRequest.buildEntitySetContextURL(olingo) method. > Would be nice if we could choose this behavior through a init param in the odata deployment. > Thanks in advance. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5390) Concurrent repeated add attempts create orphaned blocks

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-5390: ------------------------------------- Summary: Concurrent repeated add attempts create orphaned blocks Key: TEIID-5390 URL: https://issues.jboss.org/browse/TEIID-5390 Project: Teiid Issue Type: Bug Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Critical Fix For: 11.0, 10.3.2, 10.2.3 If both a user thread and the buffer cleaner are evicting the same batch/page at the same time - and multiple attempts are made by one of the threads it will result in duplicate inode / data block entries being created, which then cannot be cleaned. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5389) JDV 6.4 Quickstart examples not working with certain passwords

by Alpa Jain (JIRA)

Alpa Jain created TEIID-5389: -------------------------------- Summary: JDV 6.4 Quickstart examples not working with certain passwords Key: TEIID-5389 URL: https://issues.jboss.org/browse/TEIID-5389 Project: Teiid Issue Type: Bug Components: Quick Starts Environment: JDV 6.4 installer JDV 6.4 Maven repository Apache Maven 3.5.0 JRE - OpenJDK Runtime Environment (build 1.8.0_161-b14) JDK - jdk1.8.0_112 RHEL Workstation 7.4 Reporter: Alpa Jain Assignee: Van Halbert When executing the quickstart examples - dynamicvdb-dataroles and dynamicvdb-datafederation, certain application user's passwords were not working and constantly gave exception for any username (eg teiidUser, user, admin etc) and password =pa$$w0rd, always got below error [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.3.2:java (default-cli) on project simpleclient: An exception occured while executing the Java class. null: InvocationTargetException: TEIID50072 The username "teiidUser" and/or password and/or payload token could not be authenticated by security domain teiid-security. -> [Help 1] When using any username (eg teiidUser, user, admin etc) and password =redhat1!, always got below error at bash level bash: !": event not found Only when I changed the password to redhat*23, I was able to execute the quickstart examples. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5388) Deprecate no longer used teiid dashboard builder

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-5388?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-5388: ------------------------------------ remove this from the teiid.io about page. > Deprecate no longer used teiid dashboard builder > ------------------------------------------------ > > Key: TEIID-5388 > URL: https://issues.jboss.org/browse/TEIID-5388 > Project: Teiid > Issue Type: Task > Components: Documentation, Tools > Affects Versions: 10.3 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Minor > > The Teiid Dashboard Builder, which is only a relabel of the dashboard builder [project|http://dashbuilder.org/]. There isn't any benefit for Teiid to continue this project. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5388) Deprecate no longer used teiid dashboard builder

by Van Halbert (JIRA)

Van Halbert created TEIID-5388: ---------------------------------- Summary: Deprecate no longer used teiid dashboard builder Key: TEIID-5388 URL: https://issues.jboss.org/browse/TEIID-5388 Project: Teiid Issue Type: Task Components: Documentation, Tools Affects Versions: 10.3 Reporter: Van Halbert Assignee: Steven Hawkins Priority: Minor The Teiid Dashboard Builder, which is only a relabel of the dashboard builder [project|http://dashbuilder.org/]. There isn't any benefit for Teiid to continue this project. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5386) Wrong procedure import from MS SQL Server

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5386?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5386: --------------------------------------- > not sure why the ;1 That is really a bug with the driver. SQL Server has a deprecated convention that allow the same procedure with different signatures to be grouped together for the purpose of being dropped - https://docs.microsoft.com/en-us/sql/t-sql/statements/create-procedure-tr... The driver is reporting that as the name, when it should be the specific name instead. What driver version is this? > Wrong procedure import from MS SQL Server > ----------------------------------------- > > Key: TEIID-5386 > URL: https://issues.jboss.org/browse/TEIID-5386 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.13.6_4 > Reporter: Jan Martiska > Assignee: Steven Hawkins > > When using automatic procedure import from SQL Server (I used 2016) with a model like this: > {noformat} > <model name="mymodel"> > <property name="importer.useFullSchemaName" value="false"/> > <property name="importer.UseQualifiedName" value="false" /> > <property name="importer.procedureNamePattern" value="echo%"/> > <property name="importer.importProcedures" value="true" /> > <source connection-jndi-name="java:/mssql2016" > name="mySource" translator-name="sqlserver" /> > </model> > {noformat} > There is a procedure named {{echo}} in SQL server. It is imported into the VDB as {{"mymodel"."echo;1"}} (not sure why the ;1). When I afterwards try to execute it using > {noformat} > EXEC "mymodel"."echo;1"(); > {noformat}, I will get this exception from SQL server which suggests that Teiid mapped the procedure to the wrong name in the source database: > {noformat} > com.microsoft.sqlserver.jdbc.SQLServerException: Could not find stored procedure 'echo;1'. > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5372) Enhance docker support

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-5372?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5372: ------------------------------------- [~shawkins] Go ahead create the JIRAs for both, we can take look what it takes to implement those. > Enhance docker support > ---------------------- > > Key: TEIID-5372 > URL: https://issues.jboss.org/browse/TEIID-5372 > Project: Teiid > Issue Type: Enhancement > Reporter: Rafal Korytkowski > Assignee: Rafal Korytkowski > Priority: Optional > > Currently there's limited support for docker in Teiid, which can be enabled by adding -Ddocker=true to the build command. The generated image is based on CentOS and running standalone on the Wildfly server. Latest builds are pushed to https://hub.docker.com/r/jboss/teiid/, but versions are not tagged automatically with releases. Development with Docker is not supported. > Proposed changes: > 1. Produce docker image based on Alpine, which is better suited for microservices, in addition to CentOS. > 2. Automatically tag versions in Docker when doing releases. > 3. Support development by providing a docker-compose file with the possibility to start server in a debug mode and enabled auto-redeployment of code changes. > 4. Optionally provide a Docker image for building code using maven in Docker. Having Docker as the only prerequisite is convenient for CI environments and makes the build environment agnostic. > [~shawkins], [~rareddy], thoughts? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5382) rename wildfly-swarm-teiid-examples to thorntail-teiid examples

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-5382?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5382: ------------------------------------- In new Thorntail based deployments use of main classes is deprecated, so these examples need to be completely rewritten. The RDBMS one is one got converted, and salesforce one. But not others. I see there is very less value in examples just showcasing different data sources IMO. I was thinking in the lines of - Example to show relational database as source - Example to show file/CSV as source - Example to show web/json as source - Example with Keycloak - Example with Keycloak and 3Scale - Example with OData - Example for Materialization - more.. Then there are two different flavors of these examples that can be done * Standalone Thorntail (aka replacement for WildFly) * OpenShift based deployment. here we can choose to keep the examples together (which I prefer) or we can have two separate repositories. That also brings up a question if we want to combine "teiid-examples" too, but we can wait and see how this new platform shapes up to be. > rename wildfly-swarm-teiid-examples to thorntail-teiid examples > --------------------------------------------------------------- > > Key: TEIID-5382 > URL: https://issues.jboss.org/browse/TEIID-5382 > Project: Teiid > Issue Type: Task > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > We need to update the repository wildfly-swarm-teiid-examples to reflect the new project name. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5379) LIMIT a OFFSET b

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5379?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5379. ----------------------------------- Resolution: Done Updated the grammar and docs to support this syntax. It maps in the parser or the rewriter to existing sql support. > LIMIT a OFFSET b > ---------------- > > Key: TEIID-5379 > URL: https://issues.jboss.org/browse/TEIID-5379 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Lukáš Svačina > Assignee: Steven Hawkins > Priority: Minor > Fix For: 11.0 > > > Tradition syntax for limiting result set in teiid sql dialect is not supported. > *select * from X limit A offset B;* > It is a problem for SQL builders like JOOQ to work properly with TEIID syntax. I need to build SQL queries by some builder, but i didn't find anything suitable for TEIID SQL syntax. > JOOQ works quite good with DEFAULT dialect except for limit/offset syntax. > Are there any other ways how to build syntax correct TEIID SQL queries? > Please add this syntax support. More info here: https://groups.google.com/forum/#!topic/jooq-user/M1X6_I2JLpg -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2018