June 2020 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5960) Setting connection url property for MYSQL XA Datasource

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5960?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-5960. ----------------------------------- Resolution: Explained > Setting connection url property for MYSQL XA Datasource > ------------------------------------------------------- > > Key: TEIID-5960 > URL: https://issues.redhat.com/browse/TEIID-5960 > Project: Teiid > Issue Type: Bug > Components: AdminApi, JDBC Connector > Affects Versions: 11.1.2 > Reporter: Manoj Majumdar > Assignee: Steven Hawkins > Priority: Minor > Labels: Mysql-connector, teiid, xa-datasource-property > > I am trying to create a mysql xa datasource, but am unable to mention connection url properties in it. I have used property names such as "URL" and "connection-url", but the property is not visible in datasource. > Also when I explicitly make a property tag in datasource for the url, it is working, but not when I am creating it through Admin Api, > I need the connection url for setting mysql connection arguments such as "rewriteBatchedStatements=true" -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-205) Missing dependencies from the dependencyManagement section

by Van Halbert (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-205?page=com.atlassian.jira.plug... ] Work on TEIIDSB-205 stopped by Van Halbert. ------------------------------------------- > Missing dependencies from the dependencyManagement section > ---------------------------------------------------------- > > Key: TEIIDSB-205 > URL: https://issues.redhat.com/browse/TEIIDSB-205 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: core > Affects Versions: 1.5.0 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > > Missing the following dependencies from the dependencyManagement section: > - jakarta.xml.bind:jakarta.xml.bind-api:2.3.3 > - jakarta.persistence:jakarta.persistence-api:2.2.3 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5964) Existing table not found in schema

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5964?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-5964. ----------------------------------- Resolution: Explained If it does not have a unique or primary key, it will not be exposed via odata as an entity set. > Existing table not found in schema > ---------------------------------- > > Key: TEIID-5964 > URL: https://issues.redhat.com/browse/TEIID-5964 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 14.0 > Reporter: Renat Eskenin > Assignee: Steven Hawkins > Priority: Major > Attachments: Снимок экрана от 2020-06-01 18-55-15.png > > > Created simple Teiid project with odata > In VDB we have schema "schpostgresql" with some tables, but Odata give errors > {code} > { > "error": { > "code": null, > "message": "Cannot find EntitySet, Singleton, ActionImport or FunctionImport with name 'dm_vcom_product'." > } > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-205) Missing dependencies from the dependencyManagement section

by Van Halbert (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-205?page=com.atlassian.jira.plug... ] Van Halbert updated TEIIDSB-205: -------------------------------- Git Pull Request: https://github.com/teiid/teiid-spring-boot/pull/236 > Missing dependencies from the dependencyManagement section > ---------------------------------------------------------- > > Key: TEIIDSB-205 > URL: https://issues.redhat.com/browse/TEIIDSB-205 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: core > Affects Versions: 1.5.0 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > > Missing the following dependencies from the dependencyManagement section: > - jakarta.xml.bind:jakarta.xml.bind-api:2.3.3 > - jakarta.persistence:jakarta.persistence-api:2.2.3 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5964) Existing table not found in schema

by Renat Eskenin (Jira)

Renat Eskenin created TEIID-5964: ------------------------------------ Summary: Existing table not found in schema Key: TEIID-5964 URL: https://issues.redhat.com/browse/TEIID-5964 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 14.0 Reporter: Renat Eskenin Assignee: Steven Hawkins Attachments: Снимок экрана от 2020-06-01 18-55-15.png Created simple Teiid project with odata In VDB we have schema "schpostgresql" with some tables, but Odata give errors {code} { "error": { "code": null, "message": "Cannot find EntitySet, Singleton, ActionImport or FunctionImport with name 'dm_vcom_product'." } } {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5963) Teiid imported all schemas from PG

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5963?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on TEIID-5963: --------------------------------------- I can't reproduce this behavior. I'm not sure what the wire level pg message exchange is showing in terms of metadata load. At least with master with the foreign schema name in the import statement it gets passed to the jdbc metadata importer as importer.schemaName=name, which then limits the scope of what is imported. Please try to reproduce this on Teiid 13.1+ Moving forward to 13+ with https://issues.redhat.com/browse/TEIID-5850 A create foreign data wrapper without any options is not necessary, so you would use: CREATE FOREIGN DATA WRAPPER mypostgresql type postgresql OPTIONS (supportsOrderBy true); Not CREATE FOREIGN DATA WRAPPER postgresql; Also even in 12.x the only properties used on create server are related to the source, not the translator. With: CREATE SERVER pgserver FOREIGN DATA WRAPPER postgresql OPTIONS (supportsOrderBy true); The supportsOrderBy is effectively ignored. > Teiid imported all schemas from PG > ---------------------------------- > > Key: TEIID-5963 > URL: https://issues.redhat.com/browse/TEIID-5963 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 14.0 > Reporter: Renat Eskenin > Assignee: Steven Hawkins > Priority: Major > > When we started teiid spring boot app, we have long start time. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5963) Teiid imported all schemas from PG

by Renat Eskenin (Jira)

[ https://issues.redhat.com/browse/TEIID-5963?page=com.atlassian.jira.plugi... ] Renat Eskenin updated TEIID-5963: --------------------------------- Affects Version/s: 14.0 (was: 12.3.1) > Teiid imported all schemas from PG > ---------------------------------- > > Key: TEIID-5963 > URL: https://issues.redhat.com/browse/TEIID-5963 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 14.0 > Reporter: Renat Eskenin > Assignee: Steven Hawkins > Priority: Major > > When we started teiid spring boot app, we have long start time. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5963) Teiid imported all schemas from PG

by Renat Eskenin (Jira)

[ https://issues.redhat.com/browse/TEIID-5963?page=com.atlassian.jira.plugi... ] Renat Eskenin updated TEIID-5963: --------------------------------- Steps to Reproduce: We have teiid spring boot app with jdbc connection. DDL file {code:sql} CREATE DATABASE db; USE DATABASE db; --use translator CREATE FOREIGN DATA WRAPPER postgresql; --CREATE FOREIGN DATA WRAPPER mypostgresql type postgresql OPTIONS (supportsOrderBy true); --create teiid server CREATE SERVER pgserver FOREIGN DATA WRAPPER postgresql OPTIONS (supportsOrderBy true); -- create source schema CREATE SCHEMA schpostgresql SERVER pgserver; -- schema manual_loads IMPORT FOREIGN SCHEMA manual_loads FROM SERVER pgserver INTO schpostgresql OPTIONS("importer.useFullSchemaName" 'false', "importer.tableTypes" 'TABLE,VIEW'); {code} Properties {code} spring.datasource.platform=pgserver spring.datasource.driver-class-name=org.postgresql.Driver spring.datasource.jdbcUrl=jdbc:postgresql://test.com:5432/dwh?SearchPath=manual_loads,currentSchema=manual_loads spring.datasource.password= spring.datasource.username= spring.jpa.properties.hibernate.default_schema=manual_loads spring.datasource.hikari.schema=manual_loads hibernate.temp.use_jdbc_metadata_defaults=false spring.jpa.properties.hibernate.temp.use_jdbc_metadata_defaults=false logging.level.org=TRACE spring.jpa.hibernate.ddl-auto=none spring.main.allow-bean-definition-overriding=true spring.main.banner-mode=off spring.profiles.active=dev teiid.vdb-file=dwh.ddl {code} In logs we saw that Teeiid load all metadata from DB not only concrete schema {code} FE=> Sync <=BE BindComplete [unnamed] <=BE DataRow(len=2) <=BE CommandStatus(SELECT 1) <=BE ReadyForQuery(I) simple execute, handler=org.postgresql.jdbc.PgStatement$StatementResultHandler@8301268, maxRows=0, fetchSize=0, flags=16 FE=> Bind(stmt=S_1,portal=null,$1=<'_xuotedocument'>,type=VARCHAR) FE=> Execute(portal=null,limit=0) FE=> Sync <=BE BindComplete [unnamed] <=BE DataRow(len=2) <=BE CommandStatus(SELECT 1) <=BE ReadyForQuery(I) simple execute, handler=org.postgresql.jdbc.PgStatement$StatementResultHandler@3bbb53f6, maxRows=0, fetchSize=0, flags=16 FE=> Bind(stmt=S_1,portal=null,$1=<'_xuotelineitem'>,type=VARCHAR) FE=> Execute(portal=null,limit=0) FE=> Sync <=BE BindComplete [unnamed] <=BE DataRow(len=2) <=BE CommandStatus(SELECT 1) <=BE ReadyForQuery(I) {code} And we used {code:xml} <dependency> <groupId>org.teiid</groupId> <artifactId>teiid-spring-boot-starter</artifactId> <version>1.5.0</version> </dependency> <dependency> <groupId>org.teiid</groupId> <artifactId>spring-odata</artifactId> <version>1.5.0</version> </dependency> {code} So, we have loooong start time of app :) was: We have teiid spring boot app with jdbc connection. DDL file {code:sql} CREATE DATABASE db; USE DATABASE db; --use translator CREATE FOREIGN DATA WRAPPER postgresql; --CREATE FOREIGN DATA WRAPPER mypostgresql type postgresql OPTIONS (supportsOrderBy true); --create teiid server CREATE SERVER pgserver FOREIGN DATA WRAPPER postgresql OPTIONS (supportsOrderBy true); -- create source schema CREATE SCHEMA schpostgresql SERVER pgserver; -- schema manual_loads IMPORT FOREIGN SCHEMA manual_loads FROM SERVER pgserver INTO schpostgresql OPTIONS("importer.useFullSchemaName" 'false', "importer.tableTypes" 'TABLE,VIEW'); {code} Properties {code} spring.datasource.platform=pgserver spring.datasource.driver-class-name=org.postgresql.Driver spring.datasource.jdbcUrl=jdbc:postgresql://test.com:5432/dwh?SearchPath=manual_loads,currentSchema=manual_loads spring.datasource.password= spring.datasource.username= spring.jpa.properties.hibernate.default_schema=manual_loads spring.datasource.hikari.schema=manual_loads hibernate.temp.use_jdbc_metadata_defaults=false spring.jpa.properties.hibernate.temp.use_jdbc_metadata_defaults=false logging.level.org=TRACE spring.jpa.hibernate.ddl-auto=none spring.main.allow-bean-definition-overriding=true spring.main.banner-mode=off spring.profiles.active=dev teiid.vdb-file=dwh.ddl {code} In logs we saw that Teeiid load all metadata from DB not only concrete schema {code} FE=> Sync <=BE BindComplete [unnamed] <=BE DataRow(len=2) <=BE CommandStatus(SELECT 1) <=BE ReadyForQuery(I) simple execute, handler=org.postgresql.jdbc.PgStatement$StatementResultHandler@8301268, maxRows=0, fetchSize=0, flags=16 FE=> Bind(stmt=S_1,portal=null,$1=<'_xuotedocument'>,type=VARCHAR) FE=> Execute(portal=null,limit=0) FE=> Sync <=BE BindComplete [unnamed] <=BE DataRow(len=2) <=BE CommandStatus(SELECT 1) <=BE ReadyForQuery(I) simple execute, handler=org.postgresql.jdbc.PgStatement$StatementResultHandler@3bbb53f6, maxRows=0, fetchSize=0, flags=16 FE=> Bind(stmt=S_1,portal=null,$1=<'_xuotelineitem'>,type=VARCHAR) FE=> Execute(portal=null,limit=0) FE=> Sync <=BE BindComplete [unnamed] <=BE DataRow(len=2) <=BE CommandStatus(SELECT 1) <=BE ReadyForQuery(I) {code} So, we have loooong start time of app :) > Teiid imported all schemas from PG > ---------------------------------- > > Key: TEIID-5963 > URL: https://issues.redhat.com/browse/TEIID-5963 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 14.0 > Reporter: Renat Eskenin > Assignee: Steven Hawkins > Priority: Major > > When we started teiid spring boot app, we have long start time. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-205) Missing dependencies from the dependencyManagement section

by Van Halbert (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-205?page=com.atlassian.jira.plug... ] Van Halbert updated TEIIDSB-205: -------------------------------- Description: Missing the following dependencies from the dependencyManagement section: - jakarta.xml.bind:jakarta.xml.bind-api:2.3.3 - jakarta.persistence:jakarta.persistence-api:2.2.3 was: Missing the following dependencies from the dependencyManagement section: - jakarta.xml.bind:jakarta.xml.bind-api:2.3.3 - jakarta.persistence:jakarta.persistence-api:2.2.3 - org.ow2.asm:asm:5.0.4 > Missing dependencies from the dependencyManagement section > ---------------------------------------------------------- > > Key: TEIIDSB-205 > URL: https://issues.redhat.com/browse/TEIIDSB-205 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: core > Affects Versions: 1.5.0 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > > Missing the following dependencies from the dependencyManagement section: > - jakarta.xml.bind:jakarta.xml.bind-api:2.3.3 > - jakarta.persistence:jakarta.persistence-api:2.2.3 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5848) views in vertica not found by teiid

by Renat Eskenin (Jira)

[ https://issues.redhat.com/browse/TEIID-5848?page=com.atlassian.jira.plugi... ] Renat Eskenin commented on TEIID-5848: -------------------------------------- I found method to connect to jdbc vdb in teiid. teiid.jdbc-enable=true AND {code:java} @Bean public UserDetailsService userDetailsService() { InMemoryUserDetailsManager manager = new InMemoryUserDetailsManager(); PasswordEncoder encoder = PasswordEncoderFactories.createDelegatingPasswordEncoder(); manager.createUser( User.withUsername("user") .password(encoder.encode("user")) .roles(ROLE_USER) .build()); return manager; } {code} If we used spring security in project, Teiid will use credentials from spring security. > views in vertica not found by teiid > ----------------------------------- > > Key: TEIID-5848 > URL: https://issues.redhat.com/browse/TEIID-5848 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Reporter: Renat Eskenin > Assignee: Steven Hawkins > Priority: Major > > We created view in vertica DB > Example project with vertica translator+odata not found this view > {code} > src 1 Varchar 4 [NULL] true false false [NULL] false [NULL] > src_id 2 Varchar 18 [NULL] true false false [NULL] false [NULL] > src_name 3 Varchar 363 [NULL] true false false [NULL] false [NULL] > account_id 4 Varchar 18 [NULL] true false false [NULL] false [NULL] > name 5 Varchar 765 [NULL] true false false [NULL] false [NULL] > billing_country 6 Varchar 240 [NULL] true false false [NULL] false [NULL] > root_domain 7 Varchar 192 [NULL] true false false [NULL] false [NULL] > sales_team 8 Varchar 240 [NULL] true false false [NULL] false [NULL] > {code} > { > "error": { > "code": null, > "message": "Cannot find EntitySet, Singleton, ActionImport or FunctionImport with name 'funnel_leads'." > } > } > But regular tables works properly -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2020