April 2020 - teiid-issues - Jboss List Archives

[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'm not able to reproduce this. Can you clarify exact procedure and if you are setting the status table name as fully qualified in your metadata? > 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)

4 years, 7 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: --------------------------------------- The answer to the setting in Teiid Spring Boot is that yes, it's set by default https://github.com/teiid/teiid-spring-boot/blob/e3efdf2e751502daf9765a9bd... I'll see if we can exempt dynamic sql from this. > 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)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-57) Provide Cassandra data source support

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-57?page=com.atlassian.jira.plugi... ] Ramesh Reddy reassigned TEIIDSB-57: ----------------------------------- Assignee: Aditya Manglam Sharma > Provide Cassandra data source support > ------------------------------------- > > Key: TEIIDSB-57 > URL: https://issues.redhat.com/browse/TEIIDSB-57 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: datasource > Reporter: Ramesh Reddy > Assignee: Aditya Manglam Sharma > Priority: Major > Fix For: 1.5.0 > > > Provide data source support for Cassandra -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-195) Provide Connection properties Datasource

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIIDSB-195: ------------------------------------ Summary: Provide Connection properties Datasource Key: TEIIDSB-195 URL: https://issues.redhat.com/browse/TEIIDSB-195 Project: Teiid Spring Boot Issue Type: Feature Request Components: datasource Reporter: Ramesh Reddy When generating the connection factories JSON file, include the properties that are required for making a connection. This can then be used in design tools like VSCode or in Syndesis -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

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

by Renat Eskenin (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-163?page=com.atlassian.jira.plug... ] Renat Eskenin commented on TEIIDSB-163: --------------------------------------- Hi all! How about this task? :) > 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)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-192) Document migration for alias names

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-192?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIIDSB-192: ---------------------------------------- > Translators like salesforce and actian-vector has new name in the spring boot, we need to either document or switch back to original names. The issue with salesforce and mysql is that there taking existing names and subtly changing the behavior - not that it's necessarily bad. Like it was mentioned before we could/should combine mysql/mysql5 on the teiid side anyway and allow the connection version to drive the behavior, just like the other jdbc translators. If you think the other name changes are worth while, then now that it's easier for us to define external sources, we can just add entries for the old names to mitigate migration issues. So really the biggest problem is Salesforce - and to decide what to do with that we should commit to a versioning strategy, then align to that. > Document migration for alias names > ---------------------------------- > > Key: TEIIDSB-192 > URL: https://issues.redhat.com/browse/TEIIDSB-192 > Project: Teiid Spring Boot > Issue Type: Task > Components: documentation > Reporter: Ramesh Reddy > Priority: Major > Fix For: 1.5.0 > > > Translators like salesforce and actian-vector has new name in the spring boot, we need to either document or switch back to original names. > Also if we are updating migration utilities we can build in smarts into it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5944) Infinispan protobuf generation fails to validate name with "-" in them

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5944?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5944: ---------------------------------- Fix Version/s: 14.0 > Infinispan protobuf generation fails to validate name with "-" in them > ---------------------------------------------------------------------- > > Key: TEIID-5944 > URL: https://issues.redhat.com/browse/TEIID-5944 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 14.0 > > > When the name of the view contains like "mat-example_vix" the protobuf generation seems to succeed however the validation of it by the Infinispan seems to fail. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 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: --------------------------------------- > What do I need to set, a system property? I'm not sure we want to make changes to the property. The idea behind the property was to make sure that source constructs could not be used even if fully qualified. I think the problem could be that we're using dynamic sql in the procedure, so it's applying user level rules of accessibility. So we can verify what the default is for Teiid Spring Boot, but the fix may be to allow access from dynamic sql even to hidden things. > 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)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-57) Provide Cassandra data source support

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-57?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIIDSB-57: -------------------------------- Fix Version/s: 1.5.0 > Provide Cassandra data source support > ------------------------------------- > > Key: TEIIDSB-57 > URL: https://issues.redhat.com/browse/TEIIDSB-57 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: datasource > Reporter: Ramesh Reddy > Priority: Major > Fix For: 1.5.0 > > > Provide data source support for Cassandra -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-57) Provide Cassandra data source support

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-57?page=com.atlassian.jira.plugi... ] Ramesh Reddy reassigned TEIIDSB-57: ----------------------------------- Assignee: Ramesh Reddy > Provide Cassandra data source support > ------------------------------------- > > Key: TEIIDSB-57 > URL: https://issues.redhat.com/browse/TEIIDSB-57 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: datasource > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.5.0 > > > Provide data source support for Cassandra -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 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