February 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3599) Excel translator and dynamic filenames

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3599?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3599. --------------------------------- Fix Version/s: 9.0 8.13.2 (was: Open To Community) Resolution: Done Labels: Alpha2 (was: ) The issue only pertains, if the user is using the metadata import feature to read metadata from existing Excel file. With this fix, the user can define a file name pattern instead of absolute name, the translator will select any random Excel file matching the pattern to read metadata from. It will also set the metadata such that the data is read from all the files matching the file pattern. If you are defining the DDL for the table manually, user already had the choice of specifying the "teiid_excel:FILE" metadata extension property as file pattern to read multiple data files. Documentation will be at https://teiid.gitbooks.io/documents/content/reference/Microsoft_Excel_Tra... > Excel translator and dynamic filenames > -------------------------------------- > > Key: TEIID-3599 > URL: https://issues.jboss.org/browse/TEIID-3599 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Ralph Martin Black > Assignee: Ramesh Reddy > Priority: Minor > Labels: Alpha2 > Fix For: 9.0, 8.13.2 > > > Hi all, > All samples I've reached on how to setup a connection to xls files, set up file names as properties in the source model: > ... > <property name="importer.ExcelFileName" value="names.xls"/> > ... > Is there any way to specify filenames dynamically at run-time? > Best regards > MB! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3983) External Materialization MATVIEW_ONERROR_ACTION WAIT problem

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3983?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3983. ----------------------------------- Fix Version/s: 9.0 8.12.5 8.13.2 Resolution: Done Changed the sql generated from an exists subquery to a scalar subquery - this allows for the subquery to be marked as being pre-evaluated and simplifies planning/processing. The change also uses an internal connection to recheck the valid state before blocking as another row will not be pulled from the outer scope. The unit test utilizes the minor changes from TEIID-3986 and TEIID-3987 > External Materialization MATVIEW_ONERROR_ACTION WAIT problem > ------------------------------------------------------------ > > Key: TEIID-3983 > URL: https://issues.jboss.org/browse/TEIID-3983 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.12.5 > Reporter: Jan Stastny > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5, 8.13.2 > > > When using "teiid_rel:MATVIEW_ONERROR_ACTION" 'WAIT' option in materialized view definition, there's problem with blocked request. > The blocked request is the one, that triggered the materialized view's loading (first query on the defined materialized view). After such request, one can observe, that the query execution doesn't end, but hangs. > Meanwhile while examining the contents of 'status' table in the underlying database, the LoadNumber column's value increases regularly according to the defined ttl. Moreover the 'LOADSTATE' column changes from LOADING to LOADED in similar manner. The materialized table is populated with correct data. From this I assume, materialization is set up correctly. > During the wait, when logging set to DEBUG, there appears regularly, apart from the logs about refreshing the mat view, this entry: > {code:plain} > [32m09:14:52,151 DEBUG [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue2695) Request Thread 87XzBpSzkyk4.0 with state PROCESSING > [32m09:14:52,151 DEBUG [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue2695) Request Thread 87XzBpSzkyk4.0 - processor blocked > {code} > The log appears in 'ttl' determined intervals, each time after materialized table loading related entries. > The thread mentioned is the one created after the original query execution was initiated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3987) SYSADMIN.setProperty should resolve property keys

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3987?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3987: ---------------------------------- Description: setProperty currently expects the key to be specified in the fully qualified form \{uri\}key - rather than the simpler namespace:key form. (was: setProperty currently expects the key to be specified in the fully qualified form {uri}key - rather than the simpler namespace:key form.) > SYSADMIN.setProperty should resolve property keys > ------------------------------------------------- > > Key: TEIID-3987 > URL: https://issues.jboss.org/browse/TEIID-3987 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5, 8.13.2 > > > setProperty currently expects the key to be specified in the fully qualified form \{uri\}key - rather than the simpler namespace:key form. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3986) Materialization planning should be sensitive to property changes

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3986?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3986. ----------------------------------- Fix Version/s: 8.13.2 Resolution: Done Added calls to remove cached materialization views on property sets. > Materialization planning should be sensitive to property changes > ---------------------------------------------------------------- > > Key: TEIID-3986 > URL: https://issues.jboss.org/browse/TEIID-3986 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5, 8.13.2 > > > The engine will cache the view for materialization including the on error action, and is not sensitive to property changes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3987) SYSADMIN.setProperty should resolve property keys

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3987?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3987. ----------------------------------- Fix Version/s: 8.13.2 Resolution: Done Added a call to resolve the property key in the setProperty logic. > SYSADMIN.setProperty should resolve property keys > ------------------------------------------------- > > Key: TEIID-3987 > URL: https://issues.jboss.org/browse/TEIID-3987 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5, 8.13.2 > > > setProperty currently expects the key to be specified in the fully qualified form {uri}key - rather than the simpler namespace:key form. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3986) Materialization planning should be sensitive to property changes

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3986?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3986: ---------------------------------- Summary: Materialization planning should be sensitive to property changes (was: Materialization should be sensitive to property changes) > Materialization planning should be sensitive to property changes > ---------------------------------------------------------------- > > Key: TEIID-3986 > URL: https://issues.jboss.org/browse/TEIID-3986 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5 > > > The engine will cache the view for materialization including the on error action, and is not sensitive to property changes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3983) External Materialization MATVIEW_ONERROR_ACTION WAIT problem

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3983?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-3983: ------------------------------------- Assignee: Steven Hawkins (was: Ramesh Reddy) > External Materialization MATVIEW_ONERROR_ACTION WAIT problem > ------------------------------------------------------------ > > Key: TEIID-3983 > URL: https://issues.jboss.org/browse/TEIID-3983 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.12.5 > Reporter: Jan Stastny > Assignee: Steven Hawkins > > When using "teiid_rel:MATVIEW_ONERROR_ACTION" 'WAIT' option in materialized view definition, there's problem with blocked request. > The blocked request is the one, that triggered the materialized view's loading (first query on the defined materialized view). After such request, one can observe, that the query execution doesn't end, but hangs. > Meanwhile while examining the contents of 'status' table in the underlying database, the LoadNumber column's value increases regularly according to the defined ttl. Moreover the 'LOADSTATE' column changes from LOADING to LOADED in similar manner. The materialized table is populated with correct data. From this I assume, materialization is set up correctly. > During the wait, when logging set to DEBUG, there appears regularly, apart from the logs about refreshing the mat view, this entry: > {code:plain} > [32m09:14:52,151 DEBUG [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue2695) Request Thread 87XzBpSzkyk4.0 with state PROCESSING > [32m09:14:52,151 DEBUG [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue2695) Request Thread 87XzBpSzkyk4.0 - processor blocked > {code} > The log appears in 'ttl' determined intervals, each time after materialized table loading related entries. > The thread mentioned is the one created after the original query execution was initiated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3987) SYSADMIN.setProperty should resolve property keys

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3987: ------------------------------------- Summary: SYSADMIN.setProperty should resolve property keys Key: TEIID-3987 URL: https://issues.jboss.org/browse/TEIID-3987 Project: Teiid Issue Type: Quality Risk Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.0, 8.12.5 setProperty currently expects the key to be specified in the fully qualified form {uri}key - rather than the simpler namespace:key form. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3986) Materialization should be sensitive to property changes

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3986: ------------------------------------- Summary: Materialization should be sensitive to property changes Key: TEIID-3986 URL: https://issues.jboss.org/browse/TEIID-3986 Project: Teiid Issue Type: Quality Risk Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.0, 8.12.5 The engine will cache the view for materialization including the on error action, and is not sensitive to property changes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3599) Excel translator and dynamic filenames

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3599?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3599: ------------------------------------- I used the FILE name as the pattern to the File connector, since there was no other property I used that. I think I will take the extension of the FILE name submitted and will use that as wildcard to "getFiles" connector method. > Excel translator and dynamic filenames > -------------------------------------- > > Key: TEIID-3599 > URL: https://issues.jboss.org/browse/TEIID-3599 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Ralph Martin Black > Assignee: Ramesh Reddy > Priority: Minor > Fix For: Open To Community > > > Hi all, > All samples I've reached on how to setup a connection to xls files, set up file names as properties in the source model: > ... > <property name="importer.ExcelFileName" value="names.xls"/> > ... > Is there any way to specify filenames dynamically at run-time? > Best regards > MB! -- 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 February 2016