July 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3033) Importing metadata thru Designer versus using dynamic VDB is different

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3033?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3033: ------------------------------------ Its not a designer issue. The translator mete data processor will expose this usability issue if a dynamic VDB is used or the metadata is imported by obtaining the DDL from teiid (as designer does). > Importing metadata thru Designer versus using dynamic VDB is different > ---------------------------------------------------------------------- > > Key: TEIID-3033 > URL: https://issues.jboss.org/browse/TEIID-3033 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.7.1, 8.9 > Reporter: Van Halbert > Assignee: Van Halbert > > The columns names and NIS, imported via Designer, show that the column name is set as the NIS, and then converted (replace colon with underscore) to be used as the column name. However, in the mode shape translator, this logic isn't being applied -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3033) Importing metadata thru Designer versus using dynamic VDB is different

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3033?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3033: --------------------------------------- You mean it's a regression from Designer perspective if the Teiid based importer is used? It seems like Designer should universally offer an option to use "simple" identifiers. > Importing metadata thru Designer versus using dynamic VDB is different > ---------------------------------------------------------------------- > > Key: TEIID-3033 > URL: https://issues.jboss.org/browse/TEIID-3033 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.7.1, 8.9 > Reporter: Van Halbert > Assignee: Van Halbert > > The columns names and NIS, imported via Designer, show that the column name is set as the NIS, and then converted (replace colon with underscore) to be used as the column name. However, in the mode shape translator, this logic isn't being applied -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3033) Importing metadata thru Designer versus using dynamic VDB is different

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3033?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3033: ------------------------------------ The current metadata processor (JDBCMetadataProcessor) imports the table names and column names as x:y This doesn't correspond to what was previously done. If we leave as is, then any user will have 2 options: - change their queries to quote the table and columns - remodel Because this is a minor release, it should be backwards compatible. What do you suggest to do in order that it be backwards compatible? > Importing metadata thru Designer versus using dynamic VDB is different > ---------------------------------------------------------------------- > > Key: TEIID-3033 > URL: https://issues.jboss.org/browse/TEIID-3033 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.7.1, 8.9 > Reporter: Van Halbert > Assignee: Van Halbert > > The columns names and NIS, imported via Designer, show that the column name is set as the NIS, and then converted (replace colon with underscore) to be used as the column name. However, in the mode shape translator, this logic isn't being applied -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3033) Importing metadata thru Designer versus using dynamic VDB is different

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3033?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3033: --------------------------------------- I'm still not sure what the issue is. All that should matter to the translator is name in source. > Importing metadata thru Designer versus using dynamic VDB is different > ---------------------------------------------------------------------- > > Key: TEIID-3033 > URL: https://issues.jboss.org/browse/TEIID-3033 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.7.1, 8.9 > Reporter: Van Halbert > Assignee: Van Halbert > > The columns names and NIS, imported via Designer, show that the column name is set as the NIS, and then converted (replace colon with underscore) to be used as the column name. However, in the mode shape translator, this logic isn't being applied -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3033) Importing metadata thru Designer versus using dynamic VDB is different

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3033?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3033: ------------------------------------ all the table names were converted from x:y to x_y as well as the column names. Where the database mete data names were set as the NIS with quotes. > Importing metadata thru Designer versus using dynamic VDB is different > ---------------------------------------------------------------------- > > Key: TEIID-3033 > URL: https://issues.jboss.org/browse/TEIID-3033 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.7.1, 8.9 > Reporter: Van Halbert > Assignee: Van Halbert > > The columns names and NIS, imported via Designer, show that the column name is set as the NIS, and then converted (replace colon with underscore) to be used as the column name. However, in the mode shape translator, this logic isn't being applied -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3033) Importing metadata thru Designer versus using dynamic VDB is different

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3033?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3033: --------------------------------------- Generally there's no need to automagically convert table names. You run the risk of introducing conflicts, making it harder to correlate teiid to source names, and the only thing that it helps with is not having to quote the identifiers. > Importing metadata thru Designer versus using dynamic VDB is different > ---------------------------------------------------------------------- > > Key: TEIID-3033 > URL: https://issues.jboss.org/browse/TEIID-3033 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.7.1, 8.9 > Reporter: Van Halbert > Assignee: Van Halbert > > The columns names and NIS, imported via Designer, show that the column name is set as the NIS, and then converted (replace colon with underscore) to be used as the column name. However, in the mode shape translator, this logic isn't being applied -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3034) Add support for OData query parameters

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3034?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3034: --------------------------------------- > ?$inlineCount=allpages&$top=N : always returns count = $top This was addressed by TEIID-2935 > $expand : does not appear to work (but no ostensible error) Yes, it's documented that expand does not work. You would prefer an error correct? > $count : "TEIID30088 Unrelated order by column g0.SYSID cannot be used in a SET query, with SELECT DISTINCT, or GROUP BY" occurs using this URI pattern entity/$count , per the OData documentation for using this parameter Yes that is an issue. The query that is being generated is SELECT count(*) from tbl order by pk - it should not have the order by. > Add support for OData query parameters > -------------------------------------- > > Key: TEIID-3034 > URL: https://issues.jboss.org/browse/TEIID-3034 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: OData > Affects Versions: 8.7 > Reporter: Greg MacKinnon > Assignee: Steven Hawkins > Priority: Minor > > There are some OData v2 query parameters that don't appear to work as of Teiid 8.7 (please see teiid forum thread 241566 on this topic). I believe these are all OData v2 conventions. > ?$inlineCount=allpages&$top=N : always returns count = $top > $expand : does not appear to work (but no ostensible error) > $count : "TEIID30088 Unrelated order by column g0.SYSID cannot be used in a SET query, with SELECT DISTINCT, or GROUP BY" occurs using this URI pattern entity/$count , per the OData documentation for using this parameter -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3033) Importing metadata thru Designer versus using dynamic VDB is different

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3033?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-3033: ------------------------------- Description: The columns names and NIS, imported via Designer, show that the column name is set as the NIS, and then converted (replace colon with underscore) to be used as the column name. However, in the mode shape translator, this logic isn't being applied was: The importing of metadata using JDBC importer (using ModeShape driver) returns tables as under Views and columns with underscore, like: nt_base but when using dynamic VDB, the tables show up under Tables and the columns have a colon, like:L nt:base and there require you to quote the columns in order to query ("nt:base") > Importing metadata thru Designer versus using dynamic VDB is different > ---------------------------------------------------------------------- > > Key: TEIID-3033 > URL: https://issues.jboss.org/browse/TEIID-3033 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.7.1, 8.9 > Reporter: Van Halbert > Assignee: Van Halbert > > The columns names and NIS, imported via Designer, show that the column name is set as the NIS, and then converted (replace colon with underscore) to be used as the column name. However, in the mode shape translator, this logic isn't being applied -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3034) Add support for OData query parameters

by Greg MacKinnon (JIRA)

Greg MacKinnon created TEIID-3034: ------------------------------------- Summary: Add support for OData query parameters Key: TEIID-3034 URL: https://issues.jboss.org/browse/TEIID-3034 Project: Teiid Issue Type: Feature Request Security Level: Public (Everyone can see) Components: OData Affects Versions: 8.7 Reporter: Greg MacKinnon Assignee: Steven Hawkins Priority: Minor There are some OData v2 query parameters that don't appear to work as of Teiid 8.7 (please see teiid forum thread 241566 on this topic). I believe these are all OData v2 conventions. ?$inlineCount=allpages&$top=N : always returns count = $top $expand : does not appear to work (but no ostensible error) $count : "TEIID30088 Unrelated order by column g0.SYSID cannot be used in a SET query, with SELECT DISTINCT, or GROUP BY" occurs using this URI pattern entity/$count , per the OData documentation for using this parameter -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2982) Allow to change visibility to a model from imported vdb

by Marco Grigull (JIRA)

[ https://issues.jboss.org/browse/TEIID-2982?page=com.atlassian.jira.plugin... ] Marco Grigull commented on TEIID-2982: -------------------------------------- Hi, please except my apologies and ignore the link back to RH BZ 1027517 Regards, Marco > Allow to change visibility to a model from imported vdb > ------------------------------------------------------- > > Key: TEIID-2982 > URL: https://issues.jboss.org/browse/TEIID-2982 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Query Engine > Affects Versions: 8.7 > Reporter: Kenichi Takemura > Assignee: Steven Hawkins > Fix For: 8.9 > > > When a new vdb uses import-vdb, changing(override) visibility to a model from imported vdb would need to hide non-related model to the new vdb. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 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 July 2014