November 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5851) teiid rename table in salesforce

by Renat Eskenin (Jira)

[ https://issues.jboss.org/browse/TEIID-5851?page=com.atlassian.jira.plugin... ] Renat Eskenin commented on TEIID-5851: -------------------------------------- I need to use this example SOQL from salesforce SELECT Id, Who.FirstName, Who.LastName FROM Task WHERE Owner.FirstName LIKE 'B%' SELECT Id, Owner.Name FROM Task WHERE Owner.FirstName like 'B%' > teiid rename table in salesforce > -------------------------------- > > Key: TEIID-5851 > URL: https://issues.jboss.org/browse/TEIID-5851 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Reporter: Renat Eskenin > Assignee: Steven Hawkins > Priority: Major > > In example project connected to SF i have a table named "User" in SF but "User_" in teiid metadata. > And another strange behavior is: system tables from teiid as GEOGRAPHY_COLUMNS > GEOMETRY_COLUMNS placed in teiid server to same schema as Salesforce tables. May be "User_" named because we have same name in teiid metadata system names? > So, select "SELECT Id, User.FirstName, User.LastName FROM Task LEFT OUTER JOIN User ON User.Id=Task.OwnerId" do not working. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5851) teiid rename table in salesforce

by Renat Eskenin (Jira)

[ https://issues.jboss.org/browse/TEIID-5851?page=com.atlassian.jira.plugin... ] Renat Eskenin commented on TEIID-5851: -------------------------------------- NameUtil:31 User is teiid reserved word, so User changed to User_ But how to i can select old name User in my requests? > teiid rename table in salesforce > -------------------------------- > > Key: TEIID-5851 > URL: https://issues.jboss.org/browse/TEIID-5851 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Reporter: Renat Eskenin > Assignee: Steven Hawkins > Priority: Major > > In example project connected to SF i have a table named "User" in SF but "User_" in teiid metadata. > And another strange behavior is: system tables from teiid as GEOGRAPHY_COLUMNS > GEOMETRY_COLUMNS placed in teiid server to same schema as Salesforce tables. May be "User_" named because we have same name in teiid metadata system names? > So, select "SELECT Id, User.FirstName, User.LastName FROM Task LEFT OUTER JOIN User ON User.Id=Task.OwnerId" do not working. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5851) teiid rename table in salesforce

by Renat Eskenin (Jira)

[ https://issues.jboss.org/browse/TEIID-5851?page=com.atlassian.jira.plugin... ] Renat Eskenin updated TEIID-5851: --------------------------------- Description: In example project connected to SF i have a table named "User" in SF but "User_" in teiid metadata. And another strange behavior is: system tables from teiid as GEOGRAPHY_COLUMNS GEOMETRY_COLUMNS placed in teiid server to same schema as Salesforce tables. May be "User_" named because we have same name in teiid metadata system names? So, select "SELECT Id, User.FirstName, User.LastName FROM Task LEFT OUTER JOIN User ON User.Id=Task.OwnerId" do not working. was: In example project connected to SF i have a table named "User" in SF but "User_" in teiid metadata. And another strange behavior is: system tables from teiid as GEOGRAPHY_COLUMNS GEOMETRY_COLUMNS placed in teiid server to same schema as Salesforce tables. May be "User_" named because we have same name in teiid metadata system names? So, select "SELECT Id, User.FirstName, User.LastName FROM Task LEFT OUTER JOIN User ON User.Id=Task.OwnerId" is not working. > teiid rename table in salesforce > -------------------------------- > > Key: TEIID-5851 > URL: https://issues.jboss.org/browse/TEIID-5851 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Reporter: Renat Eskenin > Assignee: Steven Hawkins > Priority: Major > > In example project connected to SF i have a table named "User" in SF but "User_" in teiid metadata. > And another strange behavior is: system tables from teiid as GEOGRAPHY_COLUMNS > GEOMETRY_COLUMNS placed in teiid server to same schema as Salesforce tables. May be "User_" named because we have same name in teiid metadata system names? > So, select "SELECT Id, User.FirstName, User.LastName FROM Task LEFT OUTER JOIN User ON User.Id=Task.OwnerId" do not working. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5851) teiid rename table in salesforce

by Renat Eskenin (Jira)

Renat Eskenin created TEIID-5851: ------------------------------------ Summary: teiid rename table in salesforce Key: TEIID-5851 URL: https://issues.jboss.org/browse/TEIID-5851 Project: Teiid Issue Type: Bug Components: Salesforce Connector Reporter: Renat Eskenin Assignee: Steven Hawkins In example project connected to SF i have a table named "User" in SF but "User_" in teiid metadata. And another strange behavior is: system tables from teiid as GEOGRAPHY_COLUMNS GEOMETRY_COLUMNS placed in teiid server to same schema as Salesforce tables. May be "User_" named because we have same name in teiid metadata system names? So, select "SELECT Id, User.FirstName, User.LastName FROM Task LEFT OUTER JOIN User ON User.Id=Task.OwnerId" is not working. -- 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 Renat Eskenin (Jira)

[ https://issues.jboss.org/browse/TEIID-5848?page=com.atlassian.jira.plugin... ] Renat Eskenin commented on TEIID-5848: -------------------------------------- It is working with ddl altering view. But i think need to implement full metadata reading from vertica :) > 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-137) The resource-name concept seems unused

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-137?page=com.atlassian.jira.plugi... ] Ramesh Reddy commented on TEIIDSB-137: -------------------------------------- +1 sure. > 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 > > > 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 commented on TEIIDSB-137: ---------------------------------------- [~rareddy] are you good with removing resource-name from the examples? > 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 > > > 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-5792) Permissions don't work with virtual procedures' ResultSet

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5792?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-5792: ------------------------------------- Assignee: (was: Steven Hawkins) > Permissions don't work with virtual procedures' ResultSet > --------------------------------------------------------- > > Key: TEIID-5792 > URL: https://issues.jboss.org/browse/TEIID-5792 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 12.0 > Environment: teiid-12.0.0 on WildFly Full 14.0.1.Final (WildFly Core 6.0.2.Final) > Reporter: Dmitrii Pogorelov > Priority: Major > Fix For: Open To Community > > > Teiid doesn't work with ResultSet of a virtual procedure. For example, if we have procs.testProc virtual procedure which can return two values in ResultSet: a and b and we specify a permission for one of these columns in ResultSet, the permission won't work: > {code:xml} > <permission> > <resource-name>procs.testProc.a</resource-name> > <allow-read>false</allow-read> > </permission> > {code} > I think it would be great to set permissions also for ResultSets of virtual procedures, so AuthorizationValidationVisitor.validateEntitlements method for a GroupSymbol, which is a procedure, should analyze also its ResultSet. At the same time permissions work for virtual views and we can set permissions for some views' columns separately. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5792) Permissions don't work with virtual procedures' ResultSet

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5792?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5792: ---------------------------------- Fix Version/s: Open To Community > Permissions don't work with virtual procedures' ResultSet > --------------------------------------------------------- > > Key: TEIID-5792 > URL: https://issues.jboss.org/browse/TEIID-5792 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 12.0 > Environment: teiid-12.0.0 on WildFly Full 14.0.1.Final (WildFly Core 6.0.2.Final) > Reporter: Dmitrii Pogorelov > Priority: Major > Fix For: Open To Community > > > Teiid doesn't work with ResultSet of a virtual procedure. For example, if we have procs.testProc virtual procedure which can return two values in ResultSet: a and b and we specify a permission for one of these columns in ResultSet, the permission won't work: > {code:xml} > <permission> > <resource-name>procs.testProc.a</resource-name> > <allow-read>false</allow-read> > </permission> > {code} > I think it would be great to set permissions also for ResultSets of virtual procedures, so AuthorizationValidationVisitor.validateEntitlements method for a GroupSymbol, which is a procedure, should analyze also its ResultSet. At the same time permissions work for virtual views and we can set permissions for some views' columns separately. -- 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 Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-136?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIIDSB-136: ----------------------------------- Fix Version/s: 1.3.0 > 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 > 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2019