May 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5754) Schema visibility issues

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5754?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5754. ----------------------------------- Resolution: Done Addressed the regression, corrected the docs, and updated the logic to just have visible as a option. > Schema visibility issues > ------------------------ > > Key: TEIID-5754 > URL: https://issues.jboss.org/browse/TEIID-5754 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.3, 12.2.1 > > > Schema visibility is documented incorrectly. It also is not reflected in the DDL to string logic. > And there's a regression with TEIID-5715 where non-visible schema in ddl cause unexpected parsing errors since groups are being resolved against the non-design time metadata. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5754) Schema visibility issues

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5754?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5754: ---------------------------------- Description: Schema visibility is documented incorrectly. It also is not reflected in the DDL to string logic. And there's a regression with TEIID-5715 where non-visible schema in ddl cause unexpected parsing errors since groups are being resolved against the non-design time metadata. was:Information held directly on the SchemaMetadata object is not reflected in DDL. At the least we need visibility and the description. Summary: Schema visibility issues (was: Schema visibility is not captured by DDL) > Schema visibility issues > ------------------------ > > Key: TEIID-5754 > URL: https://issues.jboss.org/browse/TEIID-5754 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.3, 12.2.1 > > > Schema visibility is documented incorrectly. It also is not reflected in the DDL to string logic. > And there's a regression with TEIID-5715 where non-visible schema in ddl cause unexpected parsing errors since groups are being resolved against the non-design time metadata. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5754) Schema visibility is not captured by DDL

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5754?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5754: --------------------------------------- [~rareddy] Yes, I see that now. It's just a doc issue - it's captured as VISIBILITY > Schema visibility is not captured by DDL > ---------------------------------------- > > Key: TEIID-5754 > URL: https://issues.jboss.org/browse/TEIID-5754 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.3, 12.2.1 > > > Information held directly on the SchemaMetadata object is not reflected in DDL. At the least we need visibility and the description. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5754) Schema visibility is not captured by DDL

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5754?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5754: ------------------------------------- I believe I captured this on the OPTIONS? > Schema visibility is not captured by DDL > ---------------------------------------- > > Key: TEIID-5754 > URL: https://issues.jboss.org/browse/TEIID-5754 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.3, 12.2.1 > > > Information held directly on the SchemaMetadata object is not reflected in DDL. At the least we need visibility and the description. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5754) Schema visibility is not captured by DDL

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5754?page=com.atlassian.jira.plugin... ] Work on TEIID-5754 started by Steven Hawkins. --------------------------------------------- > Schema visibility is not captured by DDL > ---------------------------------------- > > Key: TEIID-5754 > URL: https://issues.jboss.org/browse/TEIID-5754 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.3, 12.2.1 > > > Information held directly on the SchemaMetadata object is not reflected in DDL. At the least we need visibility and the description. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5754) Schema visibility is not captured by DDL

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5754: ------------------------------------- Summary: Schema visibility is not captured by DDL Key: TEIID-5754 URL: https://issues.jboss.org/browse/TEIID-5754 Project: Teiid Issue Type: Bug Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 12.3, 12.2.1 Information held directly on the SchemaMetadata object is not reflected in DDL. At the least we need visibility and the description. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5748) Cassandra issue with table names containing upper case characters

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5748?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5748. ----------------------------------- Resolution: Done Updated the importer to set the quoted name in source. A workaround for other releases is to set the name in source manually for any affected table/column name. > Cassandra issue with table names containing upper case characters > ----------------------------------------------------------------- > > Key: TEIID-5748 > URL: https://issues.jboss.org/browse/TEIID-5748 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Mark Tawk > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.3, 12.2.1 > > > Teiid is not putting table names and column names between double quotes when executing CQL over Cassandra. > An exception is raised when querying tables or columns containing upper case characters in their names. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5753) Please add extension metadata support to allow for an invisibility option on single foreign tables/views for odata layer

by Christoph John (Jira)

Christoph John created TEIID-5753: ------------------------------------- Summary: Please add extension metadata support to allow for an invisibility option on single foreign tables/views for odata layer Key: TEIID-5753 URL: https://issues.jboss.org/browse/TEIID-5753 Project: Teiid Issue Type: Enhancement Components: OData Reporter: Christoph John Assignee: Steven Hawkins The issue arose from the discussion at https://developer.jboss.org/message/989502#989502 > Every tables and view I specify is becoming visible in the odata service. Of course I can use GRANT to resctrict access, however, it would be more nice to not export the tables in the odata layer in the first place. Would it be possible to add some kind of per table/view INVISIBLE OPTION for odata, or could I reach the same result in a different way and how would this look like? -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5751) Please add optimization support for foreign keys in materialized tables

by Christoph John (Jira)

Christoph John created TEIID-5751: ------------------------------------- Summary: Please add optimization support for foreign keys in materialized tables Key: TEIID-5751 URL: https://issues.jboss.org/browse/TEIID-5751 Project: Teiid Issue Type: Enhancement Components: Query Engine Affects Versions: 12.2 Reporter: Christoph John Assignee: Steven Hawkins The issues came up in the following discussion https://developer.jboss.org/message/989502#989502 > 1a) Are the constraints (indexes, foreign keys) now used to optimize queries in materialized tables or not? Pk, Unique Key, and Indexes on the view will result in the creation of an index on the materialization target table and are fully utilized in planning decisions. Things are a little more complicated with foreign keys. {color:red}Currently they are not propagated onto the generated materialization target table metadata, so they are only considered in pre-planner activities, such as rewrite, before the view reference is replaced with the materialization target - but there aren't meaningful optimizations being made at that time based upon foreign key. There are couple of narrow situations where that information would be useful{color}, so it probably should be added. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-4) Provide rest access with SpringBoot

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-4?page=com.atlassian.jira.plugin.... ] Ramesh Reddy updated TEIIDSB-4: ------------------------------- Fix Version/s: 1.2.0 (was: 1.1.0) > Provide rest access with SpringBoot > ----------------------------------- > > Key: TEIIDSB-4 > URL: https://issues.jboss.org/browse/TEIIDSB-4 > Project: Teiid Spring Boot > Issue Type: Feature Request > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.2.0 > > > The current rest access layer is based upon the generation of a war with deployment hooks in wildfly. There should be a build-time or similar mechanism to expose rest with spring boot. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2019