January 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4725) ObjectTranslator SearchByKey limit handling issue

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4725?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4725: ---------------------------------- Fix Version/s: 9.1.3 > ObjectTranslator SearchByKey limit handling issue > ------------------------------------------------- > > Key: TEIID-4725 > URL: https://issues.jboss.org/browse/TEIID-4725 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.2, 9.1.3 > > > Less than the desired number or rows will be returned if an in clause and limit are used together as the row limit counter is incremented for each value tested, rather than for each value that passes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4725) ObjectTranslator SearchByKey limit handling issue

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4725?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4725. ----------------------------------- Resolution: Done Changed the index to be only for successful matches. > ObjectTranslator SearchByKey limit handling issue > ------------------------------------------------- > > Key: TEIID-4725 > URL: https://issues.jboss.org/browse/TEIID-4725 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.2 > > > Less than the desired number or rows will be returned if an in clause and limit are used together as the row limit counter is incremented for each value tested, rather than for each value that passes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4725) ObjectTranslator SearchByKey limit handling issue

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4725: ------------------------------------- Summary: ObjectTranslator SearchByKey limit handling issue Key: TEIID-4725 URL: https://issues.jboss.org/browse/TEIID-4725 Project: Teiid Issue Type: Bug Components: Misc. Connectors Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.2 Less than the desired number or rows will be returned if an in clause and limit are used together as the row limit counter is incremented for each value tested, rather than for each value that passes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3349) Allow column type to be altered

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3349?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3349. --------------------------------- Resolution: Done Labels: CR1 (was: ) Added both DDL support for both TYPE and RENAME changes for column types. > Allow column type to be altered > ------------------------------- > > Key: TEIID-3349 > URL: https://issues.jboss.org/browse/TEIID-3349 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Labels: CR1 > Fix For: 9.2 > > > Add ddl support for alter column type to assist in importing. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3349) Allow column type to be altered

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3349?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-3349: -------------------------------- Fix Version/s: 9.2 (was: 9.3) > Allow column type to be altered > ------------------------------- > > Key: TEIID-3349 > URL: https://issues.jboss.org/browse/TEIID-3349 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 9.2 > > > Add ddl support for alter column type to assist in importing. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4497) Add upsert support for JDG

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4497?page=com.atlassian.jira.plugin... ] Work on TEIID-4497 started by Steven Hawkins. --------------------------------------------- > Add upsert support for JDG > -------------------------- > > Key: TEIID-4497 > URL: https://issues.jboss.org/browse/TEIID-4497 > Project: Teiid > Issue Type: Sub-task > Components: JDG Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.2 > > > The infinispan/JDG/object translator logic should support upsert. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4644) anonymous block dynamic issues

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4644?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4644. ----------------------------------- Fix Version/s: 9.1.3 Resolution: Done Restricted anon blocks to only situations where results were not expected (either into a table, or as a result) and limited rewrite. > anonymous block dynamic issues > ------------------------------ > > Key: TEIID-4644 > URL: https://issues.jboss.org/browse/TEIID-4644 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.2, 9.1.3 > > > Using execute immediate 'begin ... end' > Has several issues. First any variable references such as rowcount will be rewritten in the outer scope and not evaluated as part of the procedure. Also the anonymous block cannot be used with targeting an into as the statement we create is insert into select ... from (begin ... end) .. - which is not valid, however the exception message does not make this clear. > So we either need to improve these issues or disallow using anonymous blocks as dynamic sql. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3952) Update to updatable internal materialized view should update the materialized view as well as the database

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3952?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3952. ----------------------------------- Resolution: Done Labels: (was: jboss) Marking as resolved with the addition of the doc note. > Update to updatable internal materialized view should update the materialized view as well as the database > ---------------------------------------------------------------------------------------------------------- > > Key: TEIID-3952 > URL: https://issues.jboss.org/browse/TEIID-3952 > Project: Teiid > Issue Type: Enhancement > Components: VDB > Affects Versions: 8.7 > Environment: Red Hat JBoss Data Virtualization 6.2 based on Teiid 8.7.x > Reporter: Andy Yuen > Assignee: Steven Hawkins > Fix For: 9.2 > > > Updating an updatable internal materized view updates the database but not the materialized view at present. The requested enhancement is that they, both, should be updated. > Setup > Client - SquirrelSQL to access JDV > JDV 6.2 - with an updatable nternal materialized view of one table from the data source > Data Source - just one data source: MySQL > I can see from the console that the target table/view has been materialized > Then I did the following: > 1) select a row from the materialized table > 2) update a field in a row in the materialized view > 3) select that row (value unchanged ie, same as int 1) - tried multiple times > 4) issue EXEC SYSADMIN.refreshMatViewRow(...) using primary key for the row that has been changed > 5) select that row (value unchanged) - now I can see the changed data > This behaviour is counter-intuitive because I was expecting that since it is an updatable materialized view, my change will write through the materialized view ie, change both the materialized view as well as the database. But in this case, it changed the database and not the materialized view? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3349) Allow column type to be altered

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3349?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3349: ------------------------------------- Sure, I will check as I am looking at this issue, see if this can be easily done to round up the feature little further. The RENAME syntax going to be {code} ALTER TABLE {table-name} RENAME COLUMN {column-name} TO {new-name}; {code} > Allow column type to be altered > ------------------------------- > > Key: TEIID-3349 > URL: https://issues.jboss.org/browse/TEIID-3349 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 9.3 > > > Add ddl support for alter column type to assist in importing. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3349) Allow column type to be altered

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3349?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3349: --------------------------------------- If it's a simple change. The intent of this issue was to address performing a native import, but then altering/correcting the types the importer has chosen. > Allow column type to be altered > ------------------------------- > > Key: TEIID-3349 > URL: https://issues.jboss.org/browse/TEIID-3349 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 9.3 > > > Add ddl support for alter column type to assist in importing. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2017