March 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2875) Metadata failed to load. No column found

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2875?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2875: --------------------------------------- > Could you log an issue, possibly with DDL that highlights the situation? Logged TEIID-3379, but don't have an exact reproducer yet. > Metadata failed to load. No column found > ---------------------------------------- > > Key: TEIID-2875 > URL: https://issues.jboss.org/browse/TEIID-2875 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.6 > Environment: Windows server 2003, Windows 7. > Reporter: SHI HONG CHIN > Assignee: Steven Hawkins > Attachments: JakkerData-vdb.xml > > > Affected database: Oracle > The following error displayed when Teiid loading a dynamic VDB: > 10:21:41,458 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB JakkerData.1 model "IWMS" metadata failed to load. Reason:TEIID60011 No column found with name "RATE"."CHARGE_NAME" > 10:23:29,994 WARN [org.teiid.RUNTIME] (teiid-async-threads - 4) TEIID50036 VDB JakkerData.1 model "IWMS" metadata failed to load. Reason:TEIID60011 No column found with name "RATE"."CHARGE_NAME" > I am not the one who design the database. But, I cannot find any table with above mentioned column name in Oracle database. So, I am not sure whether the above mentioned column name is a hidden column or not. > This bug does not exist in version 8.5. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3380) Simplify Kerberos configuration with Embedded

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3380: ------------------------------------- Summary: Simplify Kerberos configuration with Embedded Key: TEIID-3380 URL: https://issues.jboss.org/browse/TEIID-3380 Project: Teiid Issue Type: Quality Risk Components: Embedded Reporter: Steven Hawkins Assignee: Ramesh Reddy Fix For: 8.11 The current code requires overriding the embedded server to install a custom session service. It may be good to have some base level of functionality built-in and/or just delegated to the security helper. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3379) Import error reporting duplicate constraints

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3379: ------------------------------------- Summary: Import error reporting duplicate constraints Key: TEIID-3379 URL: https://issues.jboss.org/browse/TEIID-3379 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 8.8 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.11 With TEIID-2922 it is now possible for metadata import to throw an exception when multiple constraints are found with the same name even erroneously - see comments on TEIID-2875. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3302) Implement ST_Transform

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3302?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3302: --------------------------------------- Is there anything still blocking you with this that I could help with? > Implement ST_Transform > ---------------------- > > Key: TEIID-3302 > URL: https://issues.jboss.org/browse/TEIID-3302 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Tom Arnold > Assignee: Steven Hawkins > Labels: spatial > > Implement [ST_Transform|http://postgis.org/docs/ST_Transform.html] system function. This would be used to transform geometry between different coordinate systems. This needs SPATIAL_REF_SYS table and a supporting library. > There are a couple of options for implementing this: > * http://trac.osgeo.org/proj4j/ - Port of the C library used by PostGIS. Fewest dependencies and should keep us close to PostGIS in capabilities. There will be a little boilerplate to interface with JTS. > * http://docs.geotools.org/latest/userguide/library/referencing/index.html - GeoTools referencing module. I think we would need to develop a simple plugin to interface with our SPATIAL_REF_SYS table. GeoTools is active and has good docs, but brings in a lot of dependencies. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3354) AdminConsole fails getting mat view info with data roles

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3354?page=com.atlassian.jira.plugin... ] Work on TEIID-3354 started by Steven Hawkins. --------------------------------------------- > AdminConsole fails getting mat view info with data roles > -------------------------------------------------------- > > Key: TEIID-3354 > URL: https://issues.jboss.org/browse/TEIID-3354 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > Once data roles are enable the web console fails to get the mat view info - unless the user allows access to systemadmin for the admin user. > I'm logging this initially against the Teiid side as depending on the resolution we may want to change the admin code (for example using a SYS.table). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3369) Add a extension point to manipulate incoming sql

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3369?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3369. ----------------------------------- Resolution: Done Updated the documentation as well. We can consider later if it makes sense to offer this on a per vdb basis (which is vastly simpler than adding to the config). It may also make sense later to make other attributes about the request editable, such as the parameters. But for now this should suffice. > Add a extension point to manipulate incoming sql > ------------------------------------------------ > > Key: TEIID-3369 > URL: https://issues.jboss.org/browse/TEIID-3369 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Driver, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > We should look at adding a client or server extension point for manipulating sql - just the sql string, pre resolving. This will allow more flexibility in dealing with clients that don't send queries directly understood by Teiid. For example a select for update. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3193) Teiid not removing/setting the correct TCCL before calling getMetadata on translator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3193?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3193: --------------------------------------- Added a tccl proxy for custom metadata repos in 8.11. > Teiid not removing/setting the correct TCCL before calling getMetadata on translator > ------------------------------------------------------------------------------------ > > Key: TEIID-3193 > URL: https://issues.jboss.org/browse/TEIID-3193 > Project: Teiid > Issue Type: Bug > Components: Common > Affects Versions: 8.8 > Reporter: Michael Farwell > Assignee: Ramesh Reddy > Labels: CR3 > Fix For: 8.9 > > > Ramesh helped me debug a class loading issue that I'm experiencing with a custom translator and asked me to open this ticket based on his findings. The forum link is specified below and contains all of the necessary information. > Ramesh's words: "OK, I believe the geoTools is using the TCCL to load the schema, thus the error. However, the error is on the Teiid side not correctly removing/setting the correct TCCL before we call "getMetadata" call on the translator. You can add JIRA for this we will fix it." -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3346) File Source | Dot in file column names causes VDB deployment errors

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3346?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3346. ----------------------------------- Resolution: Done Added a header option for text columns to specify the header name to use if something different than the column name is needed. > File Source | Dot in file column names causes VDB deployment errors > ------------------------------------------------------------------- > > Key: TEIID-3346 > URL: https://issues.jboss.org/browse/TEIID-3346 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Shiveeta Mattoo > Assignee: Steven Hawkins > Fix For: 8.11 > > > In case a Delimited Flat file , contains a "Dot" character in any of the column names, we get an issue during Virtual Data Base deployment - > Root cause - > org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered "'UTF-8') COLUMNS [*]\"name.full\"[*] STRING," at line 1, column 126. > Invalid simple identifier format: [name.full] > > The query is : SELECT A."name.full",A."surname" FROM (EXEC tabwithdot.getFiles('tab.csv')) AS F, TEXTTABLE(TO_CHARS(F.file,'UTF-8') COLUMNS "name.full" STRING,"surname" STRING delimiter ' ' quote ' ' HEADER) AS A > > Please note, that although the column name [name.full], is enclosed in Double Quotes, still this issue is observed. > If there was instead any other special character, that works successfully. > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3369) Add a extension point to manipulate incoming sql

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3369?page=com.atlassian.jira.plugin... ] Steven Hawkins edited comment on TEIID-3369 at 3/12/15 8:37 AM: ---------------------------------------------------------------- Added a PreParser hook with some light refactoring to make the command context available. Is this good enough of a start? was (Author: shawkins): Add a PreParser hook with some light refactoring to make the command context available. Is this good enough of a start? > Add a extension point to manipulate incoming sql > ------------------------------------------------ > > Key: TEIID-3369 > URL: https://issues.jboss.org/browse/TEIID-3369 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Driver, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > We should look at adding a client or server extension point for manipulating sql - just the sql string, pre resolving. This will allow more flexibility in dealing with clients that don't send queries directly understood by Teiid. For example a select for update. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3346) File Source | Dot in file column names causes VDB deployment errors

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3346?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3346: --------------------------------------- Supporting column and table aliases with . is a sizable amount of work. We would need to remove the notion of output names, change the parsing logic dealing with name validation and parsing. Change the resolving logic to not break names up based upon the last index of . and change the sql string logic to preserve quoting. So for this issue I'll instead introduce another attribute for the text column which will be the header name value. > File Source | Dot in file column names causes VDB deployment errors > ------------------------------------------------------------------- > > Key: TEIID-3346 > URL: https://issues.jboss.org/browse/TEIID-3346 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Shiveeta Mattoo > Assignee: Steven Hawkins > Fix For: 8.11 > > > In case a Delimited Flat file , contains a "Dot" character in any of the column names, we get an issue during Virtual Data Base deployment - > Root cause - > org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered "'UTF-8') COLUMNS [*]\"name.full\"[*] STRING," at line 1, column 126. > Invalid simple identifier format: [name.full] > > The query is : SELECT A."name.full",A."surname" FROM (EXEC tabwithdot.getFiles('tab.csv')) AS F, TEXTTABLE(TO_CHARS(F.file,'UTF-8') COLUMNS "name.full" STRING,"surname" STRING delimiter ' ' quote ' ' HEADER) AS A > > Please note, that although the column name [name.full], is enclosed in Double Quotes, still this issue is observed. > If there was instead any other special character, that works successfully. > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2015