January 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2182) Mechanism to hook up event listener into Teiid runtime

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2182?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2182: ------------------------------------- Yes, I noticed that too. The only place right now is you can read this information is from the model's error properties. I will hook that event too with error message. > Mechanism to hook up event listener into Teiid runtime > ------------------------------------------------------ > > Key: TEIID-2182 > URL: https://issues.jboss.org/browse/TEIID-2182 > Project: Teiid > Issue Type: Feature Request > Components: AdminApi, Server > Affects Versions: 8.1 > Environment: Windows 7 64 bit > Reporter: Anil Allewar > Assignee: Ramesh Reddy > Fix For: 8.3 > > > It would be to useful allow the installation of custom listeners since we don't have a global vdb table that could have customizable triggers. This could cover for example custom strategies for external materialization initialization. > This would also help in where an application wants to listen to when a VDB was added, made active, destroyed so that it can handle those events as required by the application. > Please see the thread below for the context & details > https://community.jboss.org/message/756060 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2182) Mechanism to hook up event listener into Teiid runtime

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2182?page=com.atlassian.jira.plugin... ] Ramesh Reddy reopened TEIID-2182: --------------------------------- > Mechanism to hook up event listener into Teiid runtime > ------------------------------------------------------ > > Key: TEIID-2182 > URL: https://issues.jboss.org/browse/TEIID-2182 > Project: Teiid > Issue Type: Feature Request > Components: AdminApi, Server > Affects Versions: 8.1 > Environment: Windows 7 64 bit > Reporter: Anil Allewar > Assignee: Ramesh Reddy > Fix For: 8.3 > > > It would be to useful allow the installation of custom listeners since we don't have a global vdb table that could have customizable triggers. This could cover for example custom strategies for external materialization initialization. > This would also help in where an application wants to listen to when a VDB was added, made active, destroyed so that it can handle those events as required by the application. > Please see the thread below for the context & details > https://community.jboss.org/message/756060 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2152) MERGE support

by Mark Addleman (JIRA)

[ https://issues.jboss.org/browse/TEIID-2152?page=com.atlassian.jira.plugin... ] Mark Addleman edited comment on TEIID-2152 at 1/14/13 4:29 PM: --------------------------------------------------------------- Is a draft reference guide available? I'd like to understand how this works without pushdown and KEY support. Due to an unfortunate scrolling issue, I missed the major change in QueryRewriter. I see that it takes keys from the metadata and then forms an IF statement. I didn't realize that IF was valid outside a procedure. was (Author: markaddleman): Is a draft reference guide available? I'd like to understand how this works without pushdown and KEY support > MERGE support > ------------- > > Key: TEIID-2152 > URL: https://issues.jboss.org/browse/TEIID-2152 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Mark Addleman > Assignee: Steven Hawkins > Fix For: 8.3 > > > Support for functionality similar to H2's MERGE command: http://www.h2database.com/html/grammar.html?highlight=merge&search=merge#... > I don't know if there is a SQL standard for this and I don't care if the command is identical to H2's. I'm mostly interested in a single command to support somewhat atomic* "if pkey exists then update else insert" operation > * somewhat atomic = this doesn't have to be entirely atomic but, to the degree the data source supports the equivalent of a MERGE or JTA -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2347) Inherently updatable view validation fails with ddl metadata

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2347?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2347. ----------------------------------- Resolution: Done Moved the fk resolution ahead of the query plan logic in the metadata validator. Also made sure that deployments will be marked as failed even if an unexpected exception occurs in finalizing the deployment. > Inherently updatable view validation fails with ddl metadata > ------------------------------------------------------------ > > Key: TEIID-2347 > URL: https://issues.jboss.org/browse/TEIID-2347 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.3 > > > Depending upon the vdb structure an inherently updatable view may cause an exception during validation since the foreign keys are not yet resolved. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2152) MERGE support

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2152?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2152: --------------------------------------- Not quite yet. That will of course be posted before this is resolved. The short form is this merge is just a modified insert statement, just like h2. Also like h2 when a key clause is not specified we assume that the primary key (or first unique key) of the table is being used to ensure uniqueness. That support can be expanded, but the pk will likely be the most common case. The implementation simply performs an existence check for each row being merged and perform an update if the row exists. That of course could be optimized a little more in this simple case. > MERGE support > ------------- > > Key: TEIID-2152 > URL: https://issues.jboss.org/browse/TEIID-2152 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Mark Addleman > Assignee: Steven Hawkins > Fix For: 8.3 > > > Support for functionality similar to H2's MERGE command: http://www.h2database.com/html/grammar.html?highlight=merge&search=merge#... > I don't know if there is a SQL standard for this and I don't care if the command is identical to H2's. I'm mostly interested in a single command to support somewhat atomic* "if pkey exists then update else insert" operation > * somewhat atomic = this doesn't have to be entirely atomic but, to the degree the data source supports the equivalent of a MERGE or JTA -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2152) MERGE support

by Mark Addleman (JIRA)

[ https://issues.jboss.org/browse/TEIID-2152?page=com.atlassian.jira.plugin... ] Mark Addleman commented on TEIID-2152: -------------------------------------- Is a draft reference guide available? I'd like to understand how this works without pushdown and KEY support > MERGE support > ------------- > > Key: TEIID-2152 > URL: https://issues.jboss.org/browse/TEIID-2152 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Mark Addleman > Assignee: Steven Hawkins > Fix For: 8.3 > > > Support for functionality similar to H2's MERGE command: http://www.h2database.com/html/grammar.html?highlight=merge&search=merge#... > I don't know if there is a SQL standard for this and I don't care if the command is identical to H2's. I'm mostly interested in a single command to support somewhat atomic* "if pkey exists then update else insert" operation > * somewhat atomic = this doesn't have to be entirely atomic but, to the degree the data source supports the equivalent of a MERGE or JTA -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2182) Mechanism to hook up event listener into Teiid runtime

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2182?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2182: --------------------------------------- Another thought is that we are currently not performing a notification when the deployment fails. > Mechanism to hook up event listener into Teiid runtime > ------------------------------------------------------ > > Key: TEIID-2182 > URL: https://issues.jboss.org/browse/TEIID-2182 > Project: Teiid > Issue Type: Feature Request > Components: AdminApi, Server > Affects Versions: 8.1 > Environment: Windows 7 64 bit > Reporter: Anil Allewar > Assignee: Ramesh Reddy > Fix For: 8.3 > > > It would be to useful allow the installation of custom listeners since we don't have a global vdb table that could have customizable triggers. This could cover for example custom strategies for external materialization initialization. > This would also help in where an application wants to listen to when a VDB was added, made active, destroyed so that it can handle those events as required by the application. > Please see the thread below for the context & details > https://community.jboss.org/message/756060 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2152) MERGE support

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2152?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2152: ---------------------------------- Fix Version/s: 8.3 Targeting an even more simplistic form of merge (without the ability to specify the key clause) than h2 for 8.3. Broader ANSI and pushdown support will come later as needed. > MERGE support > ------------- > > Key: TEIID-2152 > URL: https://issues.jboss.org/browse/TEIID-2152 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Mark Addleman > Assignee: Steven Hawkins > Fix For: 8.3 > > > Support for functionality similar to H2's MERGE command: http://www.h2database.com/html/grammar.html?highlight=merge&search=merge#... > I don't know if there is a SQL standard for this and I don't care if the command is identical to H2's. I'm mostly interested in a single command to support somewhat atomic* "if pkey exists then update else insert" operation > * somewhat atomic = this doesn't have to be entirely atomic but, to the degree the data source supports the equivalent of a MERGE or JTA -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2348) Internal procedures can have a name conflict

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2348?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2348. ----------------------------------- Resolution: Done Added a check to make sure a non-conflicting name is being used. > Internal procedures can have a name conflict > -------------------------------------------- > > Key: TEIID-2348 > URL: https://issues.jboss.org/browse/TEIID-2348 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.3 > > > The compensating procedures used for inherent loop processing and other constructs use a loop cursor name of x - which will not correctly resolve if the update is being processed against a view/table named x. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2348) Internal procedures can have a name conflict

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2348: ------------------------------------- Summary: Internal procedures can have a name conflict Key: TEIID-2348 URL: https://issues.jboss.org/browse/TEIID-2348 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.3 The compensating procedures used for inherent loop processing and other constructs use a loop cursor name of x - which will not correctly resolve if the update is being processed against a view/table named x. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2013