April 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5180) Execution of stored procedure with parameters failed on Teiid

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-5180?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-5180: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1567969 Bugzilla Update: Perform > Execution of stored procedure with parameters failed on Teiid > ------------------------------------------------------------- > > Key: TEIID-5180 > URL: https://issues.jboss.org/browse/TEIID-5180 > Project: Teiid > Issue Type: Bug > Reporter: Aditi Patel > Assignee: Steven Hawkins > Fix For: 10.1 > > > I have imported SAP IQ stored procedure and trying to execute the same. > > Below is the way I have imported the procedures and related views: > > {code:java} > <model name="SrcModel_5" type="PHYSICAL" visible="true"> > <property name="importer.importKeys" value="false"/> > <property name="importer.useFullSchemaName" value="true"/> > <property name="importer.UseQualifiedName" value="true" /> > <property name="importer.TableTypes" value="VIEW" /> > <property name="importer.schemapattern" value="%"/> > <property name="importer.importProcedures" value="true" /> > <source name="SrcModel_5" translator-name="sybase" connection-jndi-name="java:/dynamicST-DS-6" /> > </model> > {code} > > *Execution:* > > EXEC SrcModel_5.dwhdb.dbo.sp_iqfile() > > *Error Log:* > > {color:red}13:12:21,669 WARN [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue11) sQOZ5DwTHpU0 TEIID30020 Processing exception for request sQOZ5DwTHpU0.0 'TEIID30089 Required parameter 'SrcModel_5.dwhdb.dbo.sp_iqfile.dbspaceName' has no value was set or is an invalid parameter.'. Originally QueryResolverException ResolverUtil.java:505. Enable more detailed logging to see the entire stacktrace.{color} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5316) Support the window function frame clause

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-5316: ------------------------------------- Summary: Support the window function frame clause Key: TEIID-5316 URL: https://issues.jboss.org/browse/TEIID-5316 Project: Teiid Issue Type: Enhancement Components: Misc. Connectors, Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 10.x Support for the frame clause should be added to enhance window functions ability to specify the rows of the frame. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4625) Consider consolidating/managing materialization status tables

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4625?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4625: --------------------------------------- The first commit allows for a status table to specified on the model and on the vdb itself. The next enhancement would be to allow for a vdb property or properties that allows for the automatic creation of the status table. > Consider consolidating/managing materialization status tables > ------------------------------------------------------------- > > Key: TEIID-4625 > URL: https://issues.jboss.org/browse/TEIID-4625 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.3 > > > To enhance usability we should consider consolidating/managing status tables. Management would include auto creation similar (which could just leverage hibernate similar to the database log logic, regardless of whether we use hibernate to read/write). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5315) MATVIEW_MAX_STALENESS_PCT reloads only based upon ttl

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5315?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5315. ----------------------------------- Fix Version/s: 10.1.3 10.2.1 Resolution: Done Updated the code to continue the polling. Also updated the polling interval to make it more easily controlled by the unit test - but we may make it a proper property if needed. > MATVIEW_MAX_STALENESS_PCT reloads only based upon ttl > ----------------------------------------------------- > > Key: TEIID-5315 > URL: https://issues.jboss.org/browse/TEIID-5315 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.3, 10.1.3, 10.2.1 > > > https://github.com/teiid/teiid/blob/6d378d44fc7cb220ebc3a7068ff5f747e49dc... > Should schedule a recurring task for reloading based upon the staleness percentage, instead it is only a oneTimeJob. This means that after the first load, it will revert to using the ttl for reloads. > We should also be explicit in the docs that the staleness is checked every minute. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5315) MATVIEW_MAX_STALENESS_PCT reloads only based upon ttl

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-5315: ------------------------------------- Summary: MATVIEW_MAX_STALENESS_PCT reloads only based upon ttl Key: TEIID-5315 URL: https://issues.jboss.org/browse/TEIID-5315 Project: Teiid Issue Type: Bug Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 10.3 https://github.com/teiid/teiid/blob/6d378d44fc7cb220ebc3a7068ff5f747e49dc... Should schedule a recurring task for reloading based upon the staleness percentage, instead it is only a oneTimeJob. This means that after the first load, it will revert to using the ttl for reloads. We should also be explicit in the docs that the staleness is checked every minute. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5285) Add high-level feature for redirection of updates

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-5285?page=com.atlassian.jira.plugin... ] Ramesh Reddy edited comment on TEIID-5285 at 4/13/18 11:13 AM: --------------------------------------------------------------- Yes, to both. On transparency, in order for us to provide the updates transparently, we would need the VDB, I am not looking at that as the user exercise. If the Teiid is in-line or as a sidecar, the responsibility is on the user to create their domain entities which go to Teiid instead of going to their DB was (Author: rareddy): Yes, to both. > Add high-level feature for redirection of updates > ------------------------------------------------- > > Key: TEIID-5285 > URL: https://issues.jboss.org/browse/TEIID-5285 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Teiid Spring Boot > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.3 > > > In microservices testing it is desirable to test against production/live data but not commit any updates. We should offer a simple solution that can defined by extension metadata and enabled/disabled by a feature flag. We may need to make simplifying assumptions about the scope (per session, per application, etc.) and durability of the updates. > Under the covers this will be achieved by using views, update triggers, and a store for the updates and when not enabled the expectation is that all operations should pass through. However the application will be limited to using Teiid SQL and will be required to use the Teiid or pg driver, or Teiid spring boot. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5285) Add high-level feature for redirection of updates

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-5285?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5285: ------------------------------------- Yes, to both. > Add high-level feature for redirection of updates > ------------------------------------------------- > > Key: TEIID-5285 > URL: https://issues.jboss.org/browse/TEIID-5285 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Teiid Spring Boot > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.3 > > > In microservices testing it is desirable to test against production/live data but not commit any updates. We should offer a simple solution that can defined by extension metadata and enabled/disabled by a feature flag. We may need to make simplifying assumptions about the scope (per session, per application, etc.) and durability of the updates. > Under the covers this will be achieved by using views, update triggers, and a store for the updates and when not enabled the expectation is that all operations should pass through. However the application will be limited to using Teiid SQL and will be required to use the Teiid or pg driver, or Teiid spring boot. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5285) Add high-level feature for redirection of updates

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5285?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5285: --------------------------------------- > Since the user is not really after any virtualization aspects, IMO this needs to be transparent. We have a different definition of transparent. To be clear you are defining transparent as: I have a Teiid application and I want to enable/disable redirection of updates transparently. > Yes, when sidecar deploys it is in the same Pod as a different container which is the same host. Just to clarify again, you see this as a traditional sidecar as multiple containers in a pod, not something like a container per node. > Add high-level feature for redirection of updates > ------------------------------------------------- > > Key: TEIID-5285 > URL: https://issues.jboss.org/browse/TEIID-5285 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Teiid Spring Boot > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.3 > > > In microservices testing it is desirable to test against production/live data but not commit any updates. We should offer a simple solution that can defined by extension metadata and enabled/disabled by a feature flag. We may need to make simplifying assumptions about the scope (per session, per application, etc.) and durability of the updates. > Under the covers this will be achieved by using views, update triggers, and a store for the updates and when not enabled the expectation is that all operations should pass through. However the application will be limited to using Teiid SQL and will be required to use the Teiid or pg driver, or Teiid spring boot. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4745) Avoid loading the same file over again when using 'org.jboss.teiid.resource-adapter.file'

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4745?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4745: --------------------------------------- An enhancement proposal to address this would be to introduce an extension property that would return a last modification timestamp. This would allow the ttl or even the mvstatus function to check to see if a new snapshot is needed. In the case of a materialized view built from the file translator, you would need a query such as: SELECT max(lastModified) from (EXEC fileSource.getFiles...) as x > Avoid loading the same file over again when using 'org.jboss.teiid.resource-adapter.file' > ----------------------------------------------------------------------------------------- > > Key: TEIID-4745 > URL: https://issues.jboss.org/browse/TEIID-4745 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Environment: * WildFly 10 > * Teiid Server 9.1.2 > * CentOs 7 > Reporter: Pedro Inácio > Assignee: Steven Hawkins > Fix For: 10.3 > > > When using the file resource adapter _org.jboss.teiid.resource-adapter.file_, it should be possible that the system per se, by the means of a new property in the resource-adapter, or other option in the view definition, or other configuration elsewhere, to not to unnecessary load a file that is already loaded. Theoretically it should be possible, for example, to check the file date or the file checksum, to see if the file is already loaded by _Teiid_. If it is, then there is no need to parse the file again. > This is important due to, specially, performance improvements. If there are a lot of files to be processed, and these files are big (200 MB or more), the system will be processing over and over again the same files if they are not updated for quite some time. > If, for example, the user uses a Materialized View, then the view will be constantly being updated with the same data, which brings another performance penalty. > *Note*: This could be extended to other resource-adapters with some sort of last data date for example, if the user whant to use this sort of mechanism. For example, if using a database like MySQL as source, then tthe user could define a last update table, and the system could do a check first against this table before tryng to load the data. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4745) Avoid loading the same file over again when using 'org.jboss.teiid.resource-adapter.file'

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4745?page=com.atlassian.jira.plugin... ] Work on TEIID-4745 started by Steven Hawkins. --------------------------------------------- > Avoid loading the same file over again when using 'org.jboss.teiid.resource-adapter.file' > ----------------------------------------------------------------------------------------- > > Key: TEIID-4745 > URL: https://issues.jboss.org/browse/TEIID-4745 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Environment: * WildFly 10 > * Teiid Server 9.1.2 > * CentOs 7 > Reporter: Pedro Inácio > Assignee: Steven Hawkins > Fix For: 10.3 > > > When using the file resource adapter _org.jboss.teiid.resource-adapter.file_, it should be possible that the system per se, by the means of a new property in the resource-adapter, or other option in the view definition, or other configuration elsewhere, to not to unnecessary load a file that is already loaded. Theoretically it should be possible, for example, to check the file date or the file checksum, to see if the file is already loaded by _Teiid_. If it is, then there is no need to parse the file again. > This is important due to, specially, performance improvements. If there are a lot of files to be processed, and these files are big (200 MB or more), the system will be processing over and over again the same files if they are not updated for quite some time. > If, for example, the user uses a Materialized View, then the view will be constantly being updated with the same data, which brings another performance penalty. > *Note*: This could be extended to other resource-adapters with some sort of last data date for example, if the user whant to use this sort of mechanism. For example, if using a database like MySQL as source, then tthe user could define a last update table, and the system could do a check first against this table before tryng to load the data. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2018