March 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3944) Accumulo translator: rowid column is compared as string in WHERE clause

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3944?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3944: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1302977|https://bugzilla.redhat.com/show_bug.cgi?id=1302977] from MODIFIED to ON_QA > Accumulo translator: rowid column is compared as string in WHERE clause > ----------------------------------------------------------------------- > > Key: TEIID-3944 > URL: https://issues.jboss.org/browse/TEIID-3944 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.3 > Reporter: Jan Stastny > Assignee: Ramesh Reddy > Fix For: 9.0, 8.12.5 > > > When in SOURCE model user specifies the required rowid column as integer: > {code:xml} > CREATE FOREIGN TABLE "SmallA" ( > rowid integer OPTIONS (UPDATABLE FALSE, SEARCHABLE 'All_Except_Like'), > . > . > . > {code} > and performs similar query: > {code:sql} > Select rowid, StringKey From accumulo.SmallA WHERE rowid >= 15 ORDER BY rowid > {code} > following results are returned: > || rowid | StringKey || > || 2 | 2 || > || 3 | 3 || > || 4 | 4 || > || 5 | 5 || > || 6 | 6 || > || 7 | 7 || > || 8 | 8 || > || 9 | 9 || > || 15 | 15 || > || ... | ... || > and given the fact, that rowid is modelled as integer, values 2,3,4,5,6,7,8,9 shouldn't appear in the result set. Interesting to note is that the resultset is then ordered by rowid, but this time correctly as expected. > Other integer columns, mapped from accumulo's Column Family: Column Qualifier pairs works as expected and are being compared as corresponding types. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3974) MIN and MAX on boolean not supported in Vertica

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3974?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3974: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1306991|https://bugzilla.redhat.com/show_bug.cgi?id=1306991] from MODIFIED to ON_QA > MIN and MAX on boolean not supported in Vertica > ----------------------------------------------- > > Key: TEIID-3974 > URL: https://issues.jboss.org/browse/TEIID-3974 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.12.3 > Reporter: Andrej Šmigala > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5 > > > Vertica does not support calling MIN and MAX aggregate functions on boolean values, attempting that fails with > {noformat} > Remote com.vertica.support.exceptions.SyntaxErrorException: [Vertica][VJDBC](3457) ERROR: Function MIN(boolean) does not exist, or permission is denied for MIN(boolean) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3971) Clob.getSubstring(int, int) returns empty or whole string

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3971?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3971: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1306519|https://bugzilla.redhat.com/show_bug.cgi?id=1306519] from MODIFIED to ON_QA > Clob.getSubstring(int,int) returns empty or whole string > -------------------------------------------------------- > > Key: TEIID-3971 > URL: https://issues.jboss.org/browse/TEIID-3971 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver, Query Engine > Affects Versions: 8.3 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 9.0, 8.12.5, 8.13.1, 8.7.3.6_2 > > > Method java.sql.Clob.getSubstring(int,int) returns either empty string (if second argument, length, is 0) or whole string (if length >= 1). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4022) Materialization issue dynamic SQL command can't be executed due ambiguous group name

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4022?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4022. ----------------------------------- Fix Version/s: 9.0 8.12.5 8.13.2 Resolution: Done Changed to use the qualified form and corrected/added logging so that errors will be easy to see. > Materialization issue dynamic SQL command can't be executed due ambiguous group name > -------------------------------------------------------------------------------------- > > Key: TEIID-4022 > URL: https://issues.jboss.org/browse/TEIID-4022 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.12.x > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 9.0, 8.12.5, 8.13.2 > > > The defined model for materialization: > {code} > <model name="PersonMatModel" type="VIRTUAL"> > <metadata type="DDL"><![CDATA[ > CREATE view PersonMatView > ( > name string, > id integer, > email string > ) OPTIONS (MATERIALIZED 'TRUE', UPDATABLE 'TRUE', > MATERIALIZED_TABLE 'PersonMatCache.Person', > "teiid_rel:MATVIEW_TTL" 60000, > "teiid_rel:MATVIEW_BEFORE_LOAD_SCRIPT" 'execute PersonMatCache.native(''truncate cache'');', > "teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'execute PersonMatCache.native(''swap cache names'');', > "teiid_rel:MATERIALIZED_STAGE_TABLE" 'PersonMatCache.Person', > "teiid_rel:MATVIEW_SHARE_SCOPE" 'NONE', > "teiid_rel:ALLOW_MATVIEW_MANAGEMENT" 'true', > "teiid_rel:MATVIEW_STATUS_TABLE" 'Accounts.status', > "teiid_rel:MATVIEW_ONERROR_ACTION" 'THROW_EXCEPTION') > AS SELECT name, id, email from PersonInfoModel.Person; > ]]> > </metadata> > </model> > {code} > causes the following exception: > {code} > org.teiid.api.exception.query.QueryProcessingException: TEIID30168 Couldn't > execute the dynamic SQL command "EXECUTE IMMEDIATE ('SELECT count(*) as > rowCount FROM ' || matViewTable) AS rowCount integer INTO #load_count" with > the SQL statement "('SELECT count(*) as rowCount FROM ' || matViewTable)" due > to: Group specified is ambiguous, resubmit the query by fully qualifying the group > name: Person > {code} > And executing the following internal call that Teiid uses does produce the non-qualifed name > {ccode} > SELECT TargetName from SYSADMIN.MatViews WHERE VDBName = 'PeopleMat' AND SchemaName = 'PersonMatModel' AND Name = 'PersonMatView' > {code} > returns: Person -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4023) Exception with unresolved Array expression hashcode

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4023?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4023. ----------------------------------- Resolution: Done Changed the hash to not depend upon the type and removed the pre-computed hashcode from scalar subquery - as the command is mutable > Exception with unresolved Array expression hashcode > --------------------------------------------------- > > Key: TEIID-4023 > URL: https://issues.jboss.org/browse/TEIID-4023 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5, 8.13.2 > > > The type is being used in the hashCode, but it may not be set. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4023) Exception with unresolved Array expression hashcode

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4023: ------------------------------------- Summary: Exception with unresolved Array expression hashcode Key: TEIID-4023 URL: https://issues.jboss.org/browse/TEIID-4023 Project: Teiid Issue Type: Bug Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.0, 8.12.5, 8.13.2 The type is being used in the hashCode, but it may not be set. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3994) AliasSymbol wrapping AliasSymbol error

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3994?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3994: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1314909 Bugzilla Update: Perform > AliasSymbol wrapping AliasSymbol error > -------------------------------------- > > Key: TEIID-3994 > URL: https://issues.jboss.org/browse/TEIID-3994 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7.1.6_2 > Environment: Red Hat JBoss Data Virtualization 6.2 on EAP6.4.0 patched to version 6.4.3, > JBoss Developer Studio 8.1.0GA with Teiid Designer plugin 9.0.3.Final.v20150810-1438-B1157 > 64-bit Windows 7 environment > Reporter: Steve Tran > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5, 8.13.2 > > Attachments: Oracle.PNG, SQLServer.PNG > > > I've defined a view and overrode the default triggers for Select, Insert, Update, and Delete. I overrode the triggers because the select is returning "hardcoded" values for a few fields (calling them virtual columns). The Update and Insert triggers will ignore these hardcoded values just in case the caller tries to update a virtual column. > I'm trying to run a insert into <tableA> select * from <tableB> query. When I run this, I get an error org.teiid.jdbc.TeiidSQLException: Cannot create AliasSymbol wrapping AliasSymbol. > Facts: > -- I can insert a record if I only select one column from tableB. > -- If I select two or more columns, it throws the error every time. > -- If I remove the overridden triggers, the insert into <tableA> select * from <tableB> works fine. > -- I can insert one or more columns into <tableA> when *not* using a insert into <tableA> select * from <tableB> query > -- Table A is Oracle > -- Table B is SQL Server > My hunch is the generated query (hibernate, or whatever SQL generator) is choking with the overridden trigger. Perhaps this use-case slipped through testing, or even more probable, I made a mistake in the trigger creation. > Here's a snip of the insert trigger, with a lot of fields removed for simplicity. > {code} > FOR EACH ROW > BEGIN ATOMIC > INSERT INTO <schema>.<tableA> (SourceSystemID, RecordTypeID, BatchID ...) > VALUES ( > convert("NEW".SourceSystemID, short), > convert("NEW".RecordTypeID, short), > convert("NEW".BatchID, integer) > ... > ) > END > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4022) Materialization issue dynamic SQL command can't be executed due ambiguous group name

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4022?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4022: --------------------------------------- Looks like there's a lot of unqualified usage of the matTableName that needs to be fixed. As for the logging of the error, that has been fixed upstream by several changes including TEIID-3995. That can be backported if desired. > Materialization issue dynamic SQL command can't be executed due ambiguous group name > -------------------------------------------------------------------------------------- > > Key: TEIID-4022 > URL: https://issues.jboss.org/browse/TEIID-4022 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.12.x > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Blocker > > The defined model for materialization: > {code} > <model name="PersonMatModel" type="VIRTUAL"> > <metadata type="DDL"><![CDATA[ > CREATE view PersonMatView > ( > name string, > id integer, > email string > ) OPTIONS (MATERIALIZED 'TRUE', UPDATABLE 'TRUE', > MATERIALIZED_TABLE 'PersonMatCache.Person', > "teiid_rel:MATVIEW_TTL" 60000, > "teiid_rel:MATVIEW_BEFORE_LOAD_SCRIPT" 'execute PersonMatCache.native(''truncate cache'');', > "teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'execute PersonMatCache.native(''swap cache names'');', > "teiid_rel:MATERIALIZED_STAGE_TABLE" 'PersonMatCache.Person', > "teiid_rel:MATVIEW_SHARE_SCOPE" 'NONE', > "teiid_rel:ALLOW_MATVIEW_MANAGEMENT" 'true', > "teiid_rel:MATVIEW_STATUS_TABLE" 'Accounts.status', > "teiid_rel:MATVIEW_ONERROR_ACTION" 'THROW_EXCEPTION') > AS SELECT name, id, email from PersonInfoModel.Person; > ]]> > </metadata> > </model> > {code} > causes the following exception: > {code} > org.teiid.api.exception.query.QueryProcessingException: TEIID30168 Couldn't > execute the dynamic SQL command "EXECUTE IMMEDIATE ('SELECT count(*) as > rowCount FROM ' || matViewTable) AS rowCount integer INTO #load_count" with > the SQL statement "('SELECT count(*) as rowCount FROM ' || matViewTable)" due > to: Group specified is ambiguous, resubmit the query by fully qualifying the group > name: Person > {code} > And executing the following internal call that Teiid uses does produce the non-qualifed name > {ccode} > SELECT TargetName from SYSADMIN.MatViews WHERE VDBName = 'PeopleMat' AND SchemaName = 'PersonMatModel' AND Name = 'PersonMatView' > {code} > returns: Person -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4022) Materialization issue dynamic SQL command can't be executed due ambiguous group name

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4022?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4022: ------------------------------------ I thought maybe the status table query (or info) was part of the problem, because the TARGETSCHEMANAME was null. Updating it didn't change the loading issue. > Materialization issue dynamic SQL command can't be executed due ambiguous group name > -------------------------------------------------------------------------------------- > > Key: TEIID-4022 > URL: https://issues.jboss.org/browse/TEIID-4022 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.12.x > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Blocker > > The defined model for materialization: > {code} > <model name="PersonMatModel" type="VIRTUAL"> > <metadata type="DDL"><![CDATA[ > CREATE view PersonMatView > ( > name string, > id integer, > email string > ) OPTIONS (MATERIALIZED 'TRUE', UPDATABLE 'TRUE', > MATERIALIZED_TABLE 'PersonMatCache.Person', > "teiid_rel:MATVIEW_TTL" 60000, > "teiid_rel:MATVIEW_BEFORE_LOAD_SCRIPT" 'execute PersonMatCache.native(''truncate cache'');', > "teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'execute PersonMatCache.native(''swap cache names'');', > "teiid_rel:MATERIALIZED_STAGE_TABLE" 'PersonMatCache.Person', > "teiid_rel:MATVIEW_SHARE_SCOPE" 'NONE', > "teiid_rel:ALLOW_MATVIEW_MANAGEMENT" 'true', > "teiid_rel:MATVIEW_STATUS_TABLE" 'Accounts.status', > "teiid_rel:MATVIEW_ONERROR_ACTION" 'THROW_EXCEPTION') > AS SELECT name, id, email from PersonInfoModel.Person; > ]]> > </metadata> > </model> > {code} > causes the following exception: > {code} > org.teiid.api.exception.query.QueryProcessingException: TEIID30168 Couldn't > execute the dynamic SQL command "EXECUTE IMMEDIATE ('SELECT count(*) as > rowCount FROM ' || matViewTable) AS rowCount integer INTO #load_count" with > the SQL statement "('SELECT count(*) as rowCount FROM ' || matViewTable)" due > to: Group specified is ambiguous, resubmit the query by fully qualifying the group > name: Person > {code} > And executing the following internal call that Teiid uses does produce the non-qualifed name > {ccode} > SELECT TargetName from SYSADMIN.MatViews WHERE VDBName = 'PeopleMat' AND SchemaName = 'PersonMatModel' AND Name = 'PersonMatView' > {code} > returns: Person -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4022) Materialization issue dynamic SQL command can't be executed due ambiguous group name

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4022?page=com.atlassian.jira.plugin... ] Van Halbert edited comment on TEIID-4022 at 3/4/16 1:40 PM: ------------------------------------------------------------ There was no error being seen when this was occurring. The status table was updated to indicate the load had failed. Only after trying to query the cache was the following exception seen: {code}Caused by: org.teiid.api.exception.query.FunctionExecutionException: TEIID31147 The materialized view PersonMatModel.PersonMatView materialization table is currently not in valid state. {code} And the above exception: org.teiid.api.exception.query.QueryProcessingException was not being seen in the server log, only thru debug did I see the issue found in the ProcedurePlan code (line 394). was (Author: van.halbert): Also, to note, the above exception: org.teiid.api.exception.query.QueryProcessingException was not being seen in the server log, only thru debug did I see the issue found in the ProcedurePlan code (line 394). > Materialization issue dynamic SQL command can't be executed due ambiguous group name > -------------------------------------------------------------------------------------- > > Key: TEIID-4022 > URL: https://issues.jboss.org/browse/TEIID-4022 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.12.x > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Blocker > > The defined model for materialization: > {code} > <model name="PersonMatModel" type="VIRTUAL"> > <metadata type="DDL"><![CDATA[ > CREATE view PersonMatView > ( > name string, > id integer, > email string > ) OPTIONS (MATERIALIZED 'TRUE', UPDATABLE 'TRUE', > MATERIALIZED_TABLE 'PersonMatCache.Person', > "teiid_rel:MATVIEW_TTL" 60000, > "teiid_rel:MATVIEW_BEFORE_LOAD_SCRIPT" 'execute PersonMatCache.native(''truncate cache'');', > "teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'execute PersonMatCache.native(''swap cache names'');', > "teiid_rel:MATERIALIZED_STAGE_TABLE" 'PersonMatCache.Person', > "teiid_rel:MATVIEW_SHARE_SCOPE" 'NONE', > "teiid_rel:ALLOW_MATVIEW_MANAGEMENT" 'true', > "teiid_rel:MATVIEW_STATUS_TABLE" 'Accounts.status', > "teiid_rel:MATVIEW_ONERROR_ACTION" 'THROW_EXCEPTION') > AS SELECT name, id, email from PersonInfoModel.Person; > ]]> > </metadata> > </model> > {code} > causes the following exception: > {code} > org.teiid.api.exception.query.QueryProcessingException: TEIID30168 Couldn't > execute the dynamic SQL command "EXECUTE IMMEDIATE ('SELECT count(*) as > rowCount FROM ' || matViewTable) AS rowCount integer INTO #load_count" with > the SQL statement "('SELECT count(*) as rowCount FROM ' || matViewTable)" due > to: Group specified is ambiguous, resubmit the query by fully qualifying the group > name: Person > {code} > And executing the following internal call that Teiid uses does produce the non-qualifed name > {ccode} > SELECT TargetName from SYSADMIN.MatViews WHERE VDBName = 'PeopleMat' AND SchemaName = 'PersonMatModel' AND Name = 'PersonMatView' > {code} > returns: Person -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2016