[JBoss JIRA] (TEIID-2636) Stream corruption errors when doing big query
by Graeme Gillies (JIRA)
[ https://issues.jboss.org/browse/TEIID-2636?page=com.atlassian.jira.plugin... ]
Graeme Gillies updated TEIID-2636:
----------------------------------
Attachment: server.log
> Stream corruption errors when doing big query
> ---------------------------------------------
>
> Key: TEIID-2636
> URL: https://issues.jboss.org/browse/TEIID-2636
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.5
> Environment: Teiid 8.5 Beta2 Running in JBoss EAP 6.1 on RHEL6
> Java 7 openjdk
> Reporter: Graeme Gillies
> Assignee: Steven Hawkins
> Attachments: server.log
>
>
> Hi,
> When performing the following big query against a virtual db we have setup in this environment, we get an error
> The query is
> {noformat}
> SELECT
> bugs.bug_id, classification.name, bugs.cf_internal_whiteboard,
> dev_cond_nak_grouped."value", partner_grouped."value",
> bugs.cf_last_closed, bugs.bug_severity, bugs.cf_qa_whiteboard,
> bugs.short_desc, qe_cond_nak_grouped."value", bugs.priority,
> bugs.version, bugs.cf_pm_score, bugs.bug_status, product.name,
> blocks_grouped.blocked, qa_contact.login_name, reporter.login_name,
> component.name, flag_grouped.flag_full, bugs.delta_ts,
> dependson_grouped.dependson, verified_grouped."value",
> bugs.creation_ts, bugs.cf_devel_whiteboard, keyword_grouped.name,
> target_release_grouped."value", bugs.target_milestone, assigned_to.login_name,
> bugs.resolution
> FROM Bugzilla_raw.bugs
> LEFT JOIN Bugzilla_raw.products ON products.id = bugs.product_id
> LEFT JOIN Bugzilla_raw.classifications classification ON classification.id = products.classification_id
> LEFT JOIN (SELECT bugs.bug_id, TEXTAGG(FOR(dev_cond_nak."value")) AS "value" FROM Bugzilla_raw.bugs JOIN Bugzilla_raw.bug_cf_conditional_nak dev_cond_nak ON dev_cond_nak.bug_id = bugs.bug_id GROUP BY bugs.bug_id) dev_cond_nak_grouped ON bugs.bug_id = dev_cond_nak_grouped.bug_id
> LEFT JOIN (SELECT bugs.bug_id, TEXTAGG(FOR(partner."value")) AS "value" FROM Bugzilla_raw.bugs JOIN Bugzilla_raw.bug_cf_partner partner ON partner.bug_id = bugs.bug_id GROUP BY bugs.bug_id) partner_grouped ON bugs.bug_id = partner_grouped.bug_id
> LEFT JOIN (SELECT bugs.bug_id, TEXTAGG(FOR(qe_cond_nak."value")) AS "value" FROM Bugzilla_raw.bugs JOIN Bugzilla_raw.bug_cf_qe_conditional_nak qe_cond_nak ON qe_cond_nak.bug_id = bugs.bug_id GROUP BY bugs.bug_id) qe_cond_nak_grouped ON bugs.bug_id = qe_cond_nak_grouped.bug_id
> LEFT JOIN Bugzilla_raw.products product ON product.id = bugs.product_id LEFT JOIN (SELECT bugs.bug_id, TEXTAGG(FOR(blocks.blocked)) AS blocked FROM Bugzilla_raw.bugs JOIN Bugzilla_raw.dependencies blocks ON blocks.dependson = bugs.bug_id GROUP BY bugs.bug_id) blocks_grouped ON bugs.bug_id = blocks_grouped.bug_id
> LEFT JOIN Bugzilla_raw.profiles qa_contact ON qa_contact.userid = bugs.qa_contact LEFT JOIN Bugzilla_raw.profiles reporter ON reporter.userid = bugs.reporter LEFT JOIN Bugzilla_raw.components component ON component.id = bugs.component_id LEFT JOIN ( SELECT flags.bug_id, TEXTAGG(FOR(concat(ft.name, flags.status))) AS flag_full FROM Bugzilla_raw.flags
> LEFT JOIN Bugzilla_raw.flagtypes ft ON ft.id = flags.type_id GROUP BY flags.bug_id) flag_grouped ON bugs.bug_id = flag_grouped.bug_id
> LEFT JOIN (SELECT bugs.bug_id, TEXTAGG(FOR(dependson.dependson)) AS dependson FROM Bugzilla_raw.bugs JOIN Bugzilla_raw.dependencies dependson ON dependson.blocked = bugs.bug_id GROUP BY bugs.bug_id) dependson_grouped ON bugs.bug_id = dependson_grouped.bug_id
> LEFT JOIN (SELECT bugs.bug_id, TEXTAGG(FOR(verified."value")) AS "value" FROM Bugzilla_raw.bugs JOIN Bugzilla_raw.bug_cf_verified verified ON verified.bug_id = bugs.bug_id GROUP BY bugs.bug_id) verified_grouped ON bugs.bug_id = verified_grouped.bug_id
> LEFT JOIN ( SELECT keywords.bug_id, TEXTAGG(FOR(kw.name)) AS name FROM Bugzilla_raw.keywords LEFT JOIN Bugzilla_raw.keyworddefs kw ON kw.id = keywords.keywordid GROUP BY keywords.bug_id) keyword_grouped ON bugs.bug_id = keyword_grouped.bug_id
> LEFT JOIN (SELECT bugs.bug_id, TEXTAGG(FOR(target_release."value")) AS "value" FROM Bugzilla_raw.bugs JOIN Bugzilla_raw.bugs_release target_release ON target_release.bug_id = bugs.bug_id GROUP BY bugs.bug_id) target_release_grouped ON bugs.bug_id = target_release_grouped.bug_id
> LEFT JOIN Bugzilla_raw.profiles assigned_to ON assigned_to.userid = bugs.assigned_to
> WHERE bugs.bug_id > 990410 OR bugs.delta_ts > parseTimestamp('2013-07-31 06:57:31 +0000', 'yyyy-MM-dd HH:mm:ss z')
> LIMIT 0,1000000
> {noformat}
> The error the client sees is
> ERROR: TEIID30048 Error reading 24,668
> DETAIL: org.teiid.jdbc.TeiidSQLException: TEIID30048 Error reading 24,668
> This is using the Postgresql ODBC interface or the JDBC interface
> The errors in the log file are quite long so I will attach the whole log file.
> Regards,
> Graeme
--
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, 4 months
[JBoss JIRA] (TEIID-2636) Stream corruption errors when doing big query
by Graeme Gillies (JIRA)
[ https://issues.jboss.org/browse/TEIID-2636?page=com.atlassian.jira.plugin... ]
Graeme Gillies commented on TEIID-2636:
---------------------------------------
server.log is now attached to this issue. Error should be towards the bottom. Contact me via email if you would like access into the environment and the vdb to help diagnose.
Thanks again,
Graeme
> Stream corruption errors when doing big query
> ---------------------------------------------
>
> Key: TEIID-2636
> URL: https://issues.jboss.org/browse/TEIID-2636
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.5
> Environment: Teiid 8.5 Beta2 Running in JBoss EAP 6.1 on RHEL6
> Java 7 openjdk
> Reporter: Graeme Gillies
> Assignee: Steven Hawkins
> Attachments: server.log
>
>
> Hi,
> When performing the following big query against a virtual db we have setup in this environment, we get an error
> The query is
> {noformat}
> SELECT
> bugs.bug_id, classification.name, bugs.cf_internal_whiteboard,
> dev_cond_nak_grouped."value", partner_grouped."value",
> bugs.cf_last_closed, bugs.bug_severity, bugs.cf_qa_whiteboard,
> bugs.short_desc, qe_cond_nak_grouped."value", bugs.priority,
> bugs.version, bugs.cf_pm_score, bugs.bug_status, product.name,
> blocks_grouped.blocked, qa_contact.login_name, reporter.login_name,
> component.name, flag_grouped.flag_full, bugs.delta_ts,
> dependson_grouped.dependson, verified_grouped."value",
> bugs.creation_ts, bugs.cf_devel_whiteboard, keyword_grouped.name,
> target_release_grouped."value", bugs.target_milestone, assigned_to.login_name,
> bugs.resolution
> FROM Bugzilla_raw.bugs
> LEFT JOIN Bugzilla_raw.products ON products.id = bugs.product_id
> LEFT JOIN Bugzilla_raw.classifications classification ON classification.id = products.classification_id
> LEFT JOIN (SELECT bugs.bug_id, TEXTAGG(FOR(dev_cond_nak."value")) AS "value" FROM Bugzilla_raw.bugs JOIN Bugzilla_raw.bug_cf_conditional_nak dev_cond_nak ON dev_cond_nak.bug_id = bugs.bug_id GROUP BY bugs.bug_id) dev_cond_nak_grouped ON bugs.bug_id = dev_cond_nak_grouped.bug_id
> LEFT JOIN (SELECT bugs.bug_id, TEXTAGG(FOR(partner."value")) AS "value" FROM Bugzilla_raw.bugs JOIN Bugzilla_raw.bug_cf_partner partner ON partner.bug_id = bugs.bug_id GROUP BY bugs.bug_id) partner_grouped ON bugs.bug_id = partner_grouped.bug_id
> LEFT JOIN (SELECT bugs.bug_id, TEXTAGG(FOR(qe_cond_nak."value")) AS "value" FROM Bugzilla_raw.bugs JOIN Bugzilla_raw.bug_cf_qe_conditional_nak qe_cond_nak ON qe_cond_nak.bug_id = bugs.bug_id GROUP BY bugs.bug_id) qe_cond_nak_grouped ON bugs.bug_id = qe_cond_nak_grouped.bug_id
> LEFT JOIN Bugzilla_raw.products product ON product.id = bugs.product_id LEFT JOIN (SELECT bugs.bug_id, TEXTAGG(FOR(blocks.blocked)) AS blocked FROM Bugzilla_raw.bugs JOIN Bugzilla_raw.dependencies blocks ON blocks.dependson = bugs.bug_id GROUP BY bugs.bug_id) blocks_grouped ON bugs.bug_id = blocks_grouped.bug_id
> LEFT JOIN Bugzilla_raw.profiles qa_contact ON qa_contact.userid = bugs.qa_contact LEFT JOIN Bugzilla_raw.profiles reporter ON reporter.userid = bugs.reporter LEFT JOIN Bugzilla_raw.components component ON component.id = bugs.component_id LEFT JOIN ( SELECT flags.bug_id, TEXTAGG(FOR(concat(ft.name, flags.status))) AS flag_full FROM Bugzilla_raw.flags
> LEFT JOIN Bugzilla_raw.flagtypes ft ON ft.id = flags.type_id GROUP BY flags.bug_id) flag_grouped ON bugs.bug_id = flag_grouped.bug_id
> LEFT JOIN (SELECT bugs.bug_id, TEXTAGG(FOR(dependson.dependson)) AS dependson FROM Bugzilla_raw.bugs JOIN Bugzilla_raw.dependencies dependson ON dependson.blocked = bugs.bug_id GROUP BY bugs.bug_id) dependson_grouped ON bugs.bug_id = dependson_grouped.bug_id
> LEFT JOIN (SELECT bugs.bug_id, TEXTAGG(FOR(verified."value")) AS "value" FROM Bugzilla_raw.bugs JOIN Bugzilla_raw.bug_cf_verified verified ON verified.bug_id = bugs.bug_id GROUP BY bugs.bug_id) verified_grouped ON bugs.bug_id = verified_grouped.bug_id
> LEFT JOIN ( SELECT keywords.bug_id, TEXTAGG(FOR(kw.name)) AS name FROM Bugzilla_raw.keywords LEFT JOIN Bugzilla_raw.keyworddefs kw ON kw.id = keywords.keywordid GROUP BY keywords.bug_id) keyword_grouped ON bugs.bug_id = keyword_grouped.bug_id
> LEFT JOIN (SELECT bugs.bug_id, TEXTAGG(FOR(target_release."value")) AS "value" FROM Bugzilla_raw.bugs JOIN Bugzilla_raw.bugs_release target_release ON target_release.bug_id = bugs.bug_id GROUP BY bugs.bug_id) target_release_grouped ON bugs.bug_id = target_release_grouped.bug_id
> LEFT JOIN Bugzilla_raw.profiles assigned_to ON assigned_to.userid = bugs.assigned_to
> WHERE bugs.bug_id > 990410 OR bugs.delta_ts > parseTimestamp('2013-07-31 06:57:31 +0000', 'yyyy-MM-dd HH:mm:ss z')
> LIMIT 0,1000000
> {noformat}
> The error the client sees is
> ERROR: TEIID30048 Error reading 24,668
> DETAIL: org.teiid.jdbc.TeiidSQLException: TEIID30048 Error reading 24,668
> This is using the Postgresql ODBC interface or the JDBC interface
> The errors in the log file are quite long so I will attach the whole log file.
> Regards,
> Graeme
--
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, 4 months
[JBoss JIRA] (TEIID-2636) Stream corruption errors when doing big query
by Graeme Gillies (JIRA)
Graeme Gillies created TEIID-2636:
-------------------------------------
Summary: Stream corruption errors when doing big query
Key: TEIID-2636
URL: https://issues.jboss.org/browse/TEIID-2636
Project: Teiid
Issue Type: Bug
Affects Versions: 8.5
Environment: Teiid 8.5 Beta2 Running in JBoss EAP 6.1 on RHEL6
Java 7 openjdk
Reporter: Graeme Gillies
Assignee: Steven Hawkins
Hi,
When performing the following big query against a virtual db we have setup in this environment, we get an error
The query is
{noformat}
SELECT
bugs.bug_id, classification.name, bugs.cf_internal_whiteboard,
dev_cond_nak_grouped."value", partner_grouped."value",
bugs.cf_last_closed, bugs.bug_severity, bugs.cf_qa_whiteboard,
bugs.short_desc, qe_cond_nak_grouped."value", bugs.priority,
bugs.version, bugs.cf_pm_score, bugs.bug_status, product.name,
blocks_grouped.blocked, qa_contact.login_name, reporter.login_name,
component.name, flag_grouped.flag_full, bugs.delta_ts,
dependson_grouped.dependson, verified_grouped."value",
bugs.creation_ts, bugs.cf_devel_whiteboard, keyword_grouped.name,
target_release_grouped."value", bugs.target_milestone, assigned_to.login_name,
bugs.resolution
FROM Bugzilla_raw.bugs
LEFT JOIN Bugzilla_raw.products ON products.id = bugs.product_id
LEFT JOIN Bugzilla_raw.classifications classification ON classification.id = products.classification_id
LEFT JOIN (SELECT bugs.bug_id, TEXTAGG(FOR(dev_cond_nak."value")) AS "value" FROM Bugzilla_raw.bugs JOIN Bugzilla_raw.bug_cf_conditional_nak dev_cond_nak ON dev_cond_nak.bug_id = bugs.bug_id GROUP BY bugs.bug_id) dev_cond_nak_grouped ON bugs.bug_id = dev_cond_nak_grouped.bug_id
LEFT JOIN (SELECT bugs.bug_id, TEXTAGG(FOR(partner."value")) AS "value" FROM Bugzilla_raw.bugs JOIN Bugzilla_raw.bug_cf_partner partner ON partner.bug_id = bugs.bug_id GROUP BY bugs.bug_id) partner_grouped ON bugs.bug_id = partner_grouped.bug_id
LEFT JOIN (SELECT bugs.bug_id, TEXTAGG(FOR(qe_cond_nak."value")) AS "value" FROM Bugzilla_raw.bugs JOIN Bugzilla_raw.bug_cf_qe_conditional_nak qe_cond_nak ON qe_cond_nak.bug_id = bugs.bug_id GROUP BY bugs.bug_id) qe_cond_nak_grouped ON bugs.bug_id = qe_cond_nak_grouped.bug_id
LEFT JOIN Bugzilla_raw.products product ON product.id = bugs.product_id LEFT JOIN (SELECT bugs.bug_id, TEXTAGG(FOR(blocks.blocked)) AS blocked FROM Bugzilla_raw.bugs JOIN Bugzilla_raw.dependencies blocks ON blocks.dependson = bugs.bug_id GROUP BY bugs.bug_id) blocks_grouped ON bugs.bug_id = blocks_grouped.bug_id
LEFT JOIN Bugzilla_raw.profiles qa_contact ON qa_contact.userid = bugs.qa_contact LEFT JOIN Bugzilla_raw.profiles reporter ON reporter.userid = bugs.reporter LEFT JOIN Bugzilla_raw.components component ON component.id = bugs.component_id LEFT JOIN ( SELECT flags.bug_id, TEXTAGG(FOR(concat(ft.name, flags.status))) AS flag_full FROM Bugzilla_raw.flags
LEFT JOIN Bugzilla_raw.flagtypes ft ON ft.id = flags.type_id GROUP BY flags.bug_id) flag_grouped ON bugs.bug_id = flag_grouped.bug_id
LEFT JOIN (SELECT bugs.bug_id, TEXTAGG(FOR(dependson.dependson)) AS dependson FROM Bugzilla_raw.bugs JOIN Bugzilla_raw.dependencies dependson ON dependson.blocked = bugs.bug_id GROUP BY bugs.bug_id) dependson_grouped ON bugs.bug_id = dependson_grouped.bug_id
LEFT JOIN (SELECT bugs.bug_id, TEXTAGG(FOR(verified."value")) AS "value" FROM Bugzilla_raw.bugs JOIN Bugzilla_raw.bug_cf_verified verified ON verified.bug_id = bugs.bug_id GROUP BY bugs.bug_id) verified_grouped ON bugs.bug_id = verified_grouped.bug_id
LEFT JOIN ( SELECT keywords.bug_id, TEXTAGG(FOR(kw.name)) AS name FROM Bugzilla_raw.keywords LEFT JOIN Bugzilla_raw.keyworddefs kw ON kw.id = keywords.keywordid GROUP BY keywords.bug_id) keyword_grouped ON bugs.bug_id = keyword_grouped.bug_id
LEFT JOIN (SELECT bugs.bug_id, TEXTAGG(FOR(target_release."value")) AS "value" FROM Bugzilla_raw.bugs JOIN Bugzilla_raw.bugs_release target_release ON target_release.bug_id = bugs.bug_id GROUP BY bugs.bug_id) target_release_grouped ON bugs.bug_id = target_release_grouped.bug_id
LEFT JOIN Bugzilla_raw.profiles assigned_to ON assigned_to.userid = bugs.assigned_to
WHERE bugs.bug_id > 990410 OR bugs.delta_ts > parseTimestamp('2013-07-31 06:57:31 +0000', 'yyyy-MM-dd HH:mm:ss z')
LIMIT 0,1000000
{noformat}
The error the client sees is
ERROR: TEIID30048 Error reading 24,668
DETAIL: org.teiid.jdbc.TeiidSQLException: TEIID30048 Error reading 24,668
This is using the Postgresql ODBC interface or the JDBC interface
The errors in the log file are quite long so I will attach the whole log file.
Regards,
Graeme
--
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, 4 months
[JBoss JIRA] (TEIID-2584) Add management features to materialization
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2584?page=com.atlassian.jira.plugin... ]
Ramesh Reddy edited comment on TEIID-2584 at 8/21/13 4:30 PM:
--------------------------------------------------------------
1) If an view is configured for external materilization, if it needs to be
managed by the Teiid scheduler for loading the below properties need to be
defined
2) The view is expected to be populated with following properties
{code}
teiid_rel:ALLOW_MATVIEW_MANAGEMENT = allow the auto management
teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT = script for loading the mat view table
teiid_rel:MATVIEW_BEFORE_LOAD_SCRIPT = script to run before load; like truncate tables
teiid_rel:MATVIEW_LOAD_SCRIPT = script to run after load; like swap/rename tables
teiid_rel:MATVIEW_STATUS_TABLE = name of the status table.
MATERIALIZED_TABLE = materialized table
{code}
3) The above properties expects the status table to be in the format
{code}
CREATE TABLE status
(
vdbname varchar(50) not null,
vdbversion integer not null,
schemaname varchar(50) not null,
name varchar(256) not null,
targetschemaname varchar(50),
targetname varchar(256) not null,
valid boolean not null,
loadstate varchar(25) not null,
cardinality integer,
updated timestamp not null,
primary key (vdbname, vdbversion, schemaname, name)
);
{code}
4) A SYSADMIN.loadMatView and SYSADMIN.matviewStatus procedures are provided
that will load the materialization results and manage the status of the load
in the status table defined above.
5) During the VDB deployment a timer sevice is started to run the above
load procedure at defined CacheHint intervals defined by the original View.
was (Author: rareddy):
1) If an view is configured for external materilization, if it needs to be
managed by the Teiid scheduler for loading the below properties need to be
defined
2) The view is expected to be populated with following properties
teiid_rel:ALLOW_MATVIEW_MANAGEMENT = allow the auto management
teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT = script for loading the mat view table
teiid_rel:MATVIEW_BEFORE_LOAD_SCRIPT = script to run before load; like truncate tables
teiid_rel:MATVIEW_LOAD_SCRIPT = script to run after load; like swap/rename tables
teiid_rel:MATVIEW_STATUS_TABLE = name of the status table.
MATERIALIZED_TABLE = materialized table
3) The above properties expects the status table to be in the format
CREATE TABLE status
(
vdbname varchar(50) not null,
vdbversion integer not null,
schemaname varchar(50) not null,
name varchar(256) not null,
targetschemaname varchar(50),
targetname varchar(256) not null,
valid boolean not null,
loadstate varchar(25) not null,
cardinality integer,
updated timestamp not null,
primary key (vdbname, vdbversion, schemaname, name)
);
4) A SYSADMIN.loadMatView and SYSADMIN.matviewStatus procedures are provided
that will load the materialization results and manage the status of the load
in the status table defined above.
5) During the VDB deployment a timer sevice is started to run the above
load procedure at defined CacheHint intervals defined by the original View.
> Add management features to materialization
> ------------------------------------------
>
> Key: TEIID-2584
> URL: https://issues.jboss.org/browse/TEIID-2584
> Project: Teiid
> Issue Type: Feature Request
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Labels: Beta3
> Fix For: 8.5
>
>
> Currently Teiid supports internal and external materialization features. The internal is managed completely by the Teiid query engine along with the infinispan cache.
> External materialization is completely unmanaged and left out to the user to manage it externally. This goals for this feature are unify the materialization logic for internal and external, such that both are managed similarly irrespective of the type of materialization chosen.
--
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, 4 months
[JBoss JIRA] (TEIID-2584) Add management features to materialization
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2584?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-2584.
---------------------------------
Labels: Beta3 (was: )
Resolution: Done
1) If an view is configured for external materilization, if it needs to be
managed by the Teiid scheduler for loading the below properties need to be
defined
2) The view is expected to be populated with following properties
teiid_rel:ALLOW_MATVIEW_MANAGEMENT = allow the auto management
teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT = script for loading the mat view table
teiid_rel:MATVIEW_BEFORE_LOAD_SCRIPT = script to run before load; like truncate tables
teiid_rel:MATVIEW_LOAD_SCRIPT = script to run after load; like swap/rename tables
teiid_rel:MATVIEW_STATUS_TABLE = name of the status table.
MATERIALIZED_TABLE = materialized table
3) The above properties expects the status table to be in the format
CREATE TABLE status
(
vdbname varchar(50) not null,
vdbversion integer not null,
schemaname varchar(50) not null,
name varchar(256) not null,
targetschemaname varchar(50),
targetname varchar(256) not null,
valid boolean not null,
loadstate varchar(25) not null,
cardinality integer,
updated timestamp not null,
primary key (vdbname, vdbversion, schemaname, name)
);
4) A SYSADMIN.loadMatView and SYSADMIN.matviewStatus procedures are provided
that will load the materialization results and manage the status of the load
in the status table defined above.
5) During the VDB deployment a timer sevice is started to run the above
load procedure at defined CacheHint intervals defined by the original View.
> Add management features to materialization
> ------------------------------------------
>
> Key: TEIID-2584
> URL: https://issues.jboss.org/browse/TEIID-2584
> Project: Teiid
> Issue Type: Feature Request
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Labels: Beta3
> Fix For: 8.5
>
>
> Currently Teiid supports internal and external materialization features. The internal is managed completely by the Teiid query engine along with the infinispan cache.
> External materialization is completely unmanaged and left out to the user to manage it externally. This goals for this feature are unify the materialization logic for internal and external, such that both are managed similarly irrespective of the type of materialization chosen.
--
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, 4 months
[JBoss JIRA] (TEIID-2635) Block exit does not reset the temptablestore
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2635:
-------------------------------------
Summary: Block exit does not reset the temptablestore
Key: TEIID-2635
URL: https://issues.jboss.org/browse/TEIID-2635
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.6
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Critical
Fix For: 8.4.1, 8.5
Once a block has completed the proper temp table context is not established until another block is pushed. This can result in odd behavior such as not finding a temporary table that should obviously exist.
--
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, 4 months
[JBoss JIRA] (TEIID-2634) Dynamic SQL will fail to execute in an exception handling block
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2634?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2634.
-----------------------------------
Resolution: Done
Removed the type checking logic from the constant constructor as it's quite a bit of overhead and is inconsistent.
> Dynamic SQL will fail to execute in an exception handling block
> ---------------------------------------------------------------
>
> Key: TEIID-2634
> URL: https://issues.jboss.org/browse/TEIID-2634
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.2
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.4.1, 8.5
>
>
> A dynamic variable statement will convert the current variable context into a substitution map for placement in the command during rewrite. However since there is a value typed as "exception" in the context the correponding constant created will throw what amounts to an assertion error.
--
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, 4 months
[JBoss JIRA] (TEIID-2634) Dynamic SQL will fail to execute in an exception handling block
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2634:
-------------------------------------
Summary: Dynamic SQL will fail to execute in an exception handling block
Key: TEIID-2634
URL: https://issues.jboss.org/browse/TEIID-2634
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 8.2
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.4.1, 8.5
A dynamic variable statement will convert the current variable context into a substitution map for placement in the command during rewrite. However since there is a value typed as "exception" in the context the correponding constant created will throw what amounts to an assertion error.
--
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, 4 months