[JBoss JIRA] (TEIID-5156) Quickstarts unify simpleclient instructions
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5156?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5156.
-----------------------------------
Resolution: Won't Fix
> Quickstarts unify simpleclient instructions
> -------------------------------------------
>
> Key: TEIID-5156
> URL: https://issues.jboss.org/browse/TEIID-5156
> Project: Teiid
> Issue Type: Bug
> Components: Quick Starts
> Affects Versions: 8.12.11.6_4
> Reporter: Jan Stastny
> Assignee: Van Halbert
> Priority: Major
>
> Unify simpleclient instructions
> {code}
> ==== Using the simpleclient example ====
> 1) Change your working directory to ${JBOSS_HOME}/quickstarts/simpleclient"
> 2) Use the simpleclient example to run the following queries:
> Example: mvn exec:java -Dvdb="portfolio" -Dsql="example query" -Dusername="xx" -Dpassword="xx"
> {code}
> vs.
> {code}
> ==== Using the simpleclient example ====
> 1. Change your working directory to "<quickstart.install.dir>/simpleclient"
> 2. Use the simpleclient example to run the following queries:
> Example: mvn exec:java -Dvdb="portfolio" -Dsql="example query"
> {code}
> * the location of simpleclient project is different each time
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 2 months
[JBoss JIRA] (TEIID-4628) Support incremental materialization refresh strategies
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-4628?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4628.
-----------------------------------
Resolution: Done
Marking this initial parent issue as resolved based upon the additional loadnumber / upsert update strategies. Additional issues will be opened as needed.
> Support incremental materialization refresh strategies
> ------------------------------------------------------
>
> Key: TEIID-4628
> URL: https://issues.jboss.org/browse/TEIID-4628
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine, Server
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Priority: Major
>
> Further enhance/refine the built in materialization management to support alternative invalidation and refresh strategies.
> In terms of priority, this would target external materialization first.
> There must be an alternative to the implied default of the table rename strategy - which is problematic when a source is not transactional and should be changed to a merge/delete approach.
> The general approaches are lazy (rows marked as dirty with refresh on query/schedule) and eager (which can even attempt to maintain close to transactional consistency). Optionally incremental loading can be used as well, to only load the portions of the materialization that are requested.
> This requires more logic that we currently have:
> - mapping source level row events to row level effects in materialized views (at worst we can refresh the whole row)
> - additional status information possibly down to a column level, which much be added to the materialization table.
> - incremental loading requires tracking the effectively covered predicate ranges and even columns of what has been loaded
> It would probably be good to focus on a single scenario at first, such as:
> external materialization, with non-incremental load (to reuse the existing simplistic load, but not rename logic), and eager refresh - and only considering transitive row effects based upon key relationships.
> Then we can ensure that sufficient options are being added to account for additional scenarios.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 2 months
[JBoss JIRA] (TEIID-2554) Enhance MERGE to support INSERT/UPDATE and DELETE
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-2554?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2554:
----------------------------------
Fix Version/s: 12.x
> Enhance MERGE to support INSERT/UPDATE and DELETE
> -------------------------------------------------
>
> Key: TEIID-2554
> URL: https://issues.jboss.org/browse/TEIID-2554
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Affects Versions: 8.4
> Reporter: Van Halbert
> Priority: Major
> Fix For: 12.x
>
>
> Add delete support to MERGE. Example is SQL Server:
> MERGE <target_table> [AS TARGET]
> USING <table_source> [AS SOURCE]
> ON <search_condition>
> [WHEN MATCHED
> THEN <merge_matched> ]
> [WHEN NOT MATCHED [BY TARGET]
> THEN <merge_not_matched> ]
> [WHEN NOT MATCHED BY SOURCE
> THEN <merge_ matched> ];
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 2 months
[JBoss JIRA] (TEIID-5525) add a flag to revert to the prior behavior (TEIID-4557)
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5525?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-5525:
----------------------------------
Fix Version/s: 11.0.3
11.1.2
> add a flag to revert to the prior behavior (TEIID-4557)
> -------------------------------------------------------
>
> Key: TEIID-5525
> URL: https://issues.jboss.org/browse/TEIID-5525
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.12.14.6_4, 8.12.15.6_4
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 11.0.3, 11.1.2, 12.0, 11.2.1
>
>
> Several customers are seeing errors[1] after https://issues.jboss.org/browse/TEIID-4557 was implemented and generally have to drop the max-active-plans to 1 for their queries to succeed. Can a flag be added to revert to the behavior prior to TEIID-4557?
> [1]
> ERROR [org.teiid.PROCESSOR] TEIID30019 Unexpected exception for request rcX003UtoyEg.0: org.teiid.core.TeiidComponentException: TEIID31261 Max estimated size 4,963,628,721 for a single operation/table id 85 has been exceeded. The server may need to increase the amount of disk or memory available, or decrease the number of max active plans.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 2 months
[JBoss JIRA] (TEIID-5525) add a flag to revert to the prior behavior (TEIID-4557)
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5525?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5525.
-----------------------------------
Resolution: Done
Updated the default formula based upon the size difference between serialized and heap storage. Also added a doc note for the org.teiid.enforceSingleMaxBufferSizeEstimate property - which is now also mentioned in the exception/warning.
> add a flag to revert to the prior behavior (TEIID-4557)
> -------------------------------------------------------
>
> Key: TEIID-5525
> URL: https://issues.jboss.org/browse/TEIID-5525
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.12.14.6_4, 8.12.15.6_4
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.0, 11.2.1
>
>
> Several customers are seeing errors[1] after https://issues.jboss.org/browse/TEIID-4557 was implemented and generally have to drop the max-active-plans to 1 for their queries to succeed. Can a flag be added to revert to the behavior prior to TEIID-4557?
> [1]
> ERROR [org.teiid.PROCESSOR] TEIID30019 Unexpected exception for request rcX003UtoyEg.0: org.teiid.core.TeiidComponentException: TEIID31261 Max estimated size 4,963,628,721 for a single operation/table id 85 has been exceeded. The server may need to increase the amount of disk or memory available, or decrease the number of max active plans.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 2 months
[JBoss JIRA] (TEIID-5525) add a flag to revert to the prior behavior (TEIID-4557)
by Ramesh Reddy (Jira)
[ https://issues.jboss.org/browse/TEIID-5525?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-5525:
-------------------------------------
> I'm not sure what you are saying here. Reducing the batch size will not help the overall amount of committed memory.
I was entirely thinking it was heap issue, that if processing batch size is reduced then it may take more time but will not run into issues with overflow going to disk. But it looks like what you found is overestimation on the size of the disk which is inadvertently erroring out.
> add a flag to revert to the prior behavior (TEIID-4557)
> -------------------------------------------------------
>
> Key: TEIID-5525
> URL: https://issues.jboss.org/browse/TEIID-5525
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.12.14.6_4, 8.12.15.6_4
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.0, 11.2.1
>
>
> Several customers are seeing errors[1] after https://issues.jboss.org/browse/TEIID-4557 was implemented and generally have to drop the max-active-plans to 1 for their queries to succeed. Can a flag be added to revert to the behavior prior to TEIID-4557?
> [1]
> ERROR [org.teiid.PROCESSOR] TEIID30019 Unexpected exception for request rcX003UtoyEg.0: org.teiid.core.TeiidComponentException: TEIID31261 Max estimated size 4,963,628,721 for a single operation/table id 85 has been exceeded. The server may need to increase the amount of disk or memory available, or decrease the number of max active plans.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 2 months