November 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5846) Support "order by" by default in the salesforce translator

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5846?page=com.atlassian.jira.plugin... ] Steven Hawkins edited comment on TEIID-5846 at 11/20/19 8:31 AM: ----------------------------------------------------------------- Renat, there is an underlying bug in the ddl handling that is preventing the property from being set. Please see TEIID-5850. The workaround is to do something like: {code} CREATE FOREIGN DATA WRAPPER salesforce; CREATE FOREIGN DATA WRAPPER mysalesforce type salesforce OPTIONS (supportsOrderBy true); CREATE SERVER salesforce FOREIGN DATA WRAPPER mysalesforce OPTIONS ("resource-name" 'salesforce'); {code} So that there is explicitly an "override" translator that sets the property. was (Author: shawkins): Renat, there is an underlying bug in the ddl handling that is preventing the property from being set. Please see TEIID-5850. The workaround is to do something like: {code} CREATE FOREIGN DATA WRAPPER salesforce; CREATE FOREIGN DATA WRAPPER mysalesforce type salesforce OPTIONS (supportsOrderBy false); CREATE SERVER salesforce FOREIGN DATA WRAPPER mysalesforce OPTIONS ("resource-name" 'salesforce'); {code} So that there is explicitly an "override" translator that sets the property. > Support "order by" by default in the salesforce translator > ---------------------------------------------------------- > > Key: TEIID-5846 > URL: https://issues.jboss.org/browse/TEIID-5846 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Environment: teiid-spring-boot+spring-odata teiid+spring-data-salesforce > Reporter: Renat Eskenin > Priority: Major > Fix For: 13.1 > > > When we call simple request as > salesforce-odata-facade/odata/salesforce/Product_License__c?$top=1&$select=Id > request processing time is 1min. But this request processing by simple SOAP SOQL request is ~150ms. > I think this do because teiid select all objects by ignoring top in request. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5849) Merge the admin and api sub-modules

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5849?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5849. ----------------------------------- Resolution: Done Merged the modules and updated the docs. I see what consolidation could be done in time for 13.0 . > Merge the admin and api sub-modules > ----------------------------------- > > Key: TEIID-5849 > URL: https://issues.jboss.org/browse/TEIID-5849 > Project: Teiid > Issue Type: Task > Components: AdminApi, Connector API > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > There isn't a compelling reason to keep the admin and api submodules separate any longer. > api depends on admin already and keeping api code out of admin makes it difficult to evolve the vdb structural components into regular api objects - or at least hold resolved references. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5849) Merge the admin and api sub-modules

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5849?focusedWorklogId=12448103&page... ] Steven Hawkins logged work on TEIID-5849: ----------------------------------------- Author: Steven Hawkins Created on: 20/Nov/19 8:26 AM Start Date: 20/Nov/19 8:26 AM Worklog Time Spent: 2 hours Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 2 hours) Time Spent: 2 hours Worklog Id: (was: 12448103) > Merge the admin and api sub-modules > ----------------------------------- > > Key: TEIID-5849 > URL: https://issues.jboss.org/browse/TEIID-5849 > Project: Teiid > Issue Type: Task > Components: AdminApi, Connector API > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > Original Estimate: 2 hours > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > There isn't a compelling reason to keep the admin and api submodules separate any longer. > api depends on admin already and keeping api code out of admin makes it difficult to evolve the vdb structural components into regular api objects - or at least hold resolved references. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

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

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5848?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5848. ----------------------------------- Resolution: Explained Resolving as explained - if there is no unique key associated with a table / view, then one needs to be added virtually for it to be an entity in odata. > views in vertica not found by teiid > ----------------------------------- > > Key: TEIID-5848 > URL: https://issues.jboss.org/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)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-136) Allow translator properties to be set via application.properties

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-136?page=com.atlassian.jira.plugi... ] Ramesh Reddy reassigned TEIIDSB-136: ------------------------------------ Assignee: Ramesh Reddy > Allow translator properties to be set via application.properties > ---------------------------------------------------------------- > > Key: TEIIDSB-136 > URL: https://issues.jboss.org/browse/TEIIDSB-136 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: core, datasource, examples > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.3.0 > > > When using a vdb-less deployment, import/model properties can be set from spring.datasource. or spring.xa.datasource. properties. However translator properties cannot. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-137) The resource-name concept seems unused

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-137?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on TEIIDSB-137: ---------------------------------------- Also removed examples of TYPE 'NONE' > The resource-name concept seems unused > -------------------------------------- > > Key: TEIIDSB-137 > URL: https://issues.jboss.org/browse/TEIIDSB-137 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: datasource, documentation > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.3.0 > > Original Estimate: 2 hours > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > Most examples show the usage of the resource-name option on create server - however this is not used anywhere in the code. It seems like the intention was to possibly use that name instead of the server name as the bean name, but everywhere makes the assumption that they match. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-137) The resource-name concept seems unused

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-137?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIIDSB-137. ------------------------------------ Assignee: Steven Hawkins Resolution: Done That's all the references I could find. The only minor issue is that the way we hold server references on the teiid side is not case sensitive, so that corner case would require the use of the resource-name in spring boot. Otherwise we'll expect that server name to match. > The resource-name concept seems unused > -------------------------------------- > > Key: TEIIDSB-137 > URL: https://issues.jboss.org/browse/TEIIDSB-137 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: datasource, documentation > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.3.0 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Most examples show the usage of the resource-name option on create server - however this is not used anywhere in the code. It seems like the intention was to possibly use that name instead of the server name as the bean name, but everywhere makes the assumption that they match. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-137) The resource-name concept seems unused

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-137?focusedWorklogId=12448096&pag... ] Steven Hawkins logged work on TEIIDSB-137: ------------------------------------------ Author: Steven Hawkins Created on: 18/Nov/19 4:14 PM Start Date: 18/Nov/19 4:14 PM Worklog Time Spent: 2 hours Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 2 hours) Time Spent: 2 hours Worklog Id: (was: 12448096) > The resource-name concept seems unused > -------------------------------------- > > Key: TEIIDSB-137 > URL: https://issues.jboss.org/browse/TEIIDSB-137 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: datasource, documentation > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.3.0 > > Original Estimate: 2 hours > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > Most examples show the usage of the resource-name option on create server - however this is not used anywhere in the code. It seems like the intention was to possibly use that name instead of the server name as the bean name, but everywhere makes the assumption that they match. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-137) The resource-name concept seems unused

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-137?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIIDSB-137: ----------------------------------- Original Estimate: 2 hours Remaining Estimate: 2 hours > The resource-name concept seems unused > -------------------------------------- > > Key: TEIIDSB-137 > URL: https://issues.jboss.org/browse/TEIIDSB-137 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: datasource, documentation > Reporter: Steven Hawkins > Priority: Major > Fix For: 1.3.0 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Most examples show the usage of the resource-name option on create server - however this is not used anywhere in the code. It seems like the intention was to possibly use that name instead of the server name as the bean name, but everywhere makes the assumption that they match. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5852) views are resolved twice in the metadata validator

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5852: ------------------------------------- Summary: views are resolved twice in the metadata validator Key: TEIID-5852 URL: https://issues.jboss.org/browse/TEIID-5852 Project: Teiid Issue Type: Quality Risk Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 13.1 There is an initial resolve to run the Validation visitor, then another resolve in resolveView. This should be combined as much as possible. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2019