April 2020 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5943) Status table not found when model is not visible

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIID-5943?page=com.atlassian.jira.plugi... ] Ramesh Reddy commented on TEIID-5943: ------------------------------------- They were the calls for loading the cache at startup. I do not remember the cross-section between admin and user calls. > Status table not found when model is not visible > ------------------------------------------------ > > Key: TEIID-5943 > URL: https://issues.redhat.com/browse/TEIID-5943 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Time Spent: 1 hour > Remaining Estimate: 0 minutes > > When materialization schema is hidden and the Materilization Status table is part of it, then references to it from Materialization scripts is not found and load auto management fails. > A workaround is simple to make model visible -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-188) Change rest properties prefix to "spring.teiid.data.rest"

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-188?page=com.atlassian.jira.plug... ] Ramesh Reddy resolved TEIIDSB-188. ---------------------------------- Resolution: Done > Change rest properties prefix to "spring.teiid.data.rest" > --------------------------------------------------------- > > Key: TEIIDSB-188 > URL: https://issues.redhat.com/browse/TEIIDSB-188 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: core > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.5.0 > > > To match with other data sources in terms of property prefixes this needs to changed from "spring.teiid.rest" to "spring.teiid.data.rest". -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-188) Change rest properties prefix to "spring.teiid.data.rest"

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-188?focusedWorklogId=12450921&pa... ] Ramesh Reddy logged work on TEIIDSB-188: ---------------------------------------- Author: Ramesh Reddy Created on: 30/Apr/20 1:20 PM Start Date: 30/Apr/20 1:20 PM Worklog Time Spent: 2 hours Issue Time Tracking ------------------- Remaining Estimate: 0 minutes Time Spent: 2 hours Worklog Id: (was: 12450921) > Change rest properties prefix to "spring.teiid.data.rest" > --------------------------------------------------------- > > Key: TEIIDSB-188 > URL: https://issues.redhat.com/browse/TEIIDSB-188 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: core > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.5.0 > > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > To match with other data sources in terms of property prefixes this needs to changed from "spring.teiid.rest" to "spring.teiid.data.rest". -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-188) Change rest properties prefix to "spring.teiid.data.rest"

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-188?page=com.atlassian.jira.plug... ] Work on TEIIDSB-188 started by Ramesh Reddy. -------------------------------------------- > Change rest properties prefix to "spring.teiid.data.rest" > --------------------------------------------------------- > > Key: TEIIDSB-188 > URL: https://issues.redhat.com/browse/TEIIDSB-188 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: core > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.5.0 > > > To match with other data sources in terms of property prefixes this needs to changed from "spring.teiid.rest" to "spring.teiid.data.rest". -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5943) Status table not found when model is not visible

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5943?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on TEIID-5943: --------------------------------------- I tested this too much in isolation. Without a stacktrace it wasn't clear you were actually talking about queries directly issued by the MaterializationManager - not called through the system admin procedures. Since those are wired in through executeQuery, they appear as user level queries subject to the visibility rules. > Status table not found when model is not visible > ------------------------------------------------ > > Key: TEIID-5943 > URL: https://issues.redhat.com/browse/TEIID-5943 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Time Spent: 1 hour > Remaining Estimate: 0 minutes > > When materialization schema is hidden and the Materilization Status table is part of it, then references to it from Materialization scripts is not found and load auto management fails. > A workaround is simple to make model visible -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5943) Status table not found when model is not visible

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5943?page=com.atlassian.jira.plugi... ] Steven Hawkins reopened TEIID-5943: ----------------------------------- > Status table not found when model is not visible > ------------------------------------------------ > > Key: TEIID-5943 > URL: https://issues.redhat.com/browse/TEIID-5943 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Time Spent: 1 hour > Remaining Estimate: 0 minutes > > When materialization schema is hidden and the Materilization Status table is part of it, then references to it from Materialization scripts is not found and load auto management fails. > A workaround is simple to make model visible -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5947) When hidden resolvable is false user anon dynamic sql should not be able to see hidden objects

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5947: ------------------------------------- Summary: When hidden resolvable is false user anon dynamic sql should not be able to see hidden objects Key: TEIID-5947 URL: https://issues.redhat.com/browse/TEIID-5947 Project: Teiid Issue Type: Bug Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 14.0 Dynamic sql is always resolved against the design time metadata, so hidden objects are effectively visible. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-163) Provide pooling for BaseConnectionFactory sources

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-163?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIIDSB-163: ---------------------------------------- Unfortunately there's a lot of other feature work going on, so this does not have sufficient priority yet. > Provide pooling for BaseConnectionFactory sources > ------------------------------------------------- > > Key: TEIIDSB-163 > URL: https://issues.redhat.com/browse/TEIIDSB-163 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: datasource > Reporter: Steven Hawkins > Priority: Major > Fix For: 1.5.0 > > > It will depend on the source and the cost of creating a connection, but in general we should provide pooling for connections rather than creating the for every operation. For example salesforce is a heavy weight connection. > The pooling will need to be tied into spring security or jca like logic to properly manage connections by identity once we re-establish that logic. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5943) Status table not found when model is not visible

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5943?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-5943. ----------------------------------- Resolution: Rejected Other than if the status table is left as unqualified, I am unable to reproduce this. If it's qualified, you can reopen. The only incongruity with access restrictions that I see is that when hidden resolvable is false, a normal user query cannot see anything hidden, but an anon dynamic sql can. I'm not sure if that is worth addressing. > Status table not found when model is not visible > ------------------------------------------------ > > Key: TEIID-5943 > URL: https://issues.redhat.com/browse/TEIID-5943 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > > When materialization schema is hidden and the Materilization Status table is part of it, then references to it from Materialization scripts is not found and load auto management fails. > A workaround is simple to make model visible -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5943) Status table not found when model is not visible

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5943?focusedWorklogId=12450916&pag... ] Steven Hawkins logged work on TEIID-5943: ----------------------------------------- Author: Steven Hawkins Created on: 30/Apr/20 9:59 AM Start Date: 30/Apr/20 9:59 AM Worklog Time Spent: 1 hour Work Description: Developed a couple of tests around visibility with hidden resolvable false. Issue Time Tracking ------------------- Remaining Estimate: 0 minutes Time Spent: 1 hour Worklog Id: (was: 12450916) > Status table not found when model is not visible > ------------------------------------------------ > > Key: TEIID-5943 > URL: https://issues.redhat.com/browse/TEIID-5943 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Time Spent: 1 hour > Remaining Estimate: 0 minutes > > When materialization schema is hidden and the Materilization Status table is part of it, then references to it from Materialization scripts is not found and load auto management fails. > A workaround is simple to make model visible -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 12 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2020