[JBoss JIRA] (TEIID-5537) Move Thorntail examples to use new modules
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5537?page=com.atlassian.jira.plugin... ]
Steven Hawkins edited comment on TEIID-5537 at 11/9/18 10:47 AM:
-----------------------------------------------------------------
so you want something like:
{code}
teiid/
thorntail/
examples
fractions
config-api
{code}
was (Author: shawkins):
so you want something like:
teiid/
thorntail/
examples
fractions
config-api
> Move Thorntail examples to use new modules
> ------------------------------------------
>
> Key: TEIID-5537
> URL: https://issues.jboss.org/browse/TEIID-5537
> Project: Teiid
> Issue Type: Sub-task
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Priority: Major
>
> Also, how about closing the "thorntail-examples" repo and merging the examples with the new Thontail repo?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 1 month
[JBoss JIRA] (TEIID-5534) Smaller initial memory buffer allocations
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5534?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5534.
-----------------------------------
Resolution: Done
Changed the code to allocate in 1/4 increments for smaller vms - but did not yet add any logic to reclaim them if unused.
> Smaller initial memory buffer allocations
> -----------------------------------------
>
> Key: TEIID-5534
> URL: https://issues.jboss.org/browse/TEIID-5534
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.0, 11.2.1
>
>
> For smaller vms, under 16 GB, the default allocation scheme for on-heap fixed memory buffers is in 1 GB increments.
> This can be quite large for VMs under 8 GBs - especially if the full commit of that memory is not needed.
> The allocation scheme should introduce the buffers more incrementally and release them when compaction is run if they aren't needed.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 1 month
[JBoss JIRA] (TEIID-5532) Common table projection minimization does not account for usage in a subquery nested in an aggregate or in some view scenarios
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5532?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5532.
-----------------------------------
Resolution: Done
Marking as resolved now that further cases involving CTEs nested in views are also addressed. In short we needed to use a different collection mechanism to discover all of the commands.
> Common table projection minimization does not account for usage in a subquery nested in an aggregate or in some view scenarios
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIID-5532
> URL: https://issues.jboss.org/browse/TEIID-5532
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 11.0.3, 11.1.2, 12.0, 11.2.1
>
>
> Nesting the usage of a common table in an aggregate means that the columns can be removed inappropriately by projection minimization. A query such as:
> with CTE1 as /*+ no_inline */ (SELECT e1, e2, e3 from pm1.g1)
> select array_agg((select e3 from cte1 where e1=pm1.g2.e1 and e2=pm1.g2.e2)) from pm1.g2
> will return null values for all e3 as projection minimization of CTE1 will replace the column with a null value.
> A similar situation occurs when the query above is defined instead in a view. A similar issue was captured on TEIID-5535
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 1 month
[JBoss JIRA] (TEIID-5532) Common table projection minimization does not account for usage in a subquery nested in an aggregate or in some view scenarios
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5532?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-5532:
----------------------------------
Description:
Nesting the usage of a common table in an aggregate means that the columns can be removed inappropriately by projection minimization. A query such as:
with CTE1 as /*+ no_inline */ (SELECT e1, e2, e3 from pm1.g1)
select array_agg((select e3 from cte1 where e1=pm1.g2.e1 and e2=pm1.g2.e2)) from pm1.g2
will return null values for all e3 as projection minimization of CTE1 will replace the column with a null value.
A similar situation occurs when the query above is defined instead in a view. A similar issue was captured on TEIID-5535
was:
Nesting the usage of a common table in an aggregate means that the columns can be removed inappropriately by projection minimization. A query such as:
with CTE1 as /*+ no_inline */ (SELECT e1, e2, e3 from pm1.g1)
select array_agg((select e3 from cte1 where e1=pm1.g2.e1 and e2=pm1.g2.e2)) from pm1.g2
will return null values for all e3 as projection minimization of CTE1 will replace the column with a null value.
Summary: Common table projection minimization does not account for usage in a subquery nested in an aggregate or in some view scenarios (was: Common table projection minimization does not account for usage in a subquery nested in an aggregate)
> Common table projection minimization does not account for usage in a subquery nested in an aggregate or in some view scenarios
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIID-5532
> URL: https://issues.jboss.org/browse/TEIID-5532
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 11.0.3, 11.1.2, 12.0, 11.2.1
>
>
> Nesting the usage of a common table in an aggregate means that the columns can be removed inappropriately by projection minimization. A query such as:
> with CTE1 as /*+ no_inline */ (SELECT e1, e2, e3 from pm1.g1)
> select array_agg((select e3 from cte1 where e1=pm1.g2.e1 and e2=pm1.g2.e2)) from pm1.g2
> will return null values for all e3 as projection minimization of CTE1 will replace the column with a null value.
> A similar situation occurs when the query above is defined instead in a view. A similar issue was captured on TEIID-5535
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 1 month
[JBoss JIRA] (TEIID-5536) Create separate repository for Thorntail modules
by Ramesh Reddy (Jira)
Ramesh Reddy created TEIID-5536:
-----------------------------------
Summary: Create separate repository for Thorntail modules
Key: TEIID-5536
URL: https://issues.jboss.org/browse/TEIID-5536
Project: Teiid
Issue Type: Task
Reporter: Ramesh Reddy
Assignee: Steven Hawkins
THORN-2232 Removes the Teiid modules from the core Thorntail repo for better release management. However, Teiid Thorntail would need a new home.
Most notable breaking change will be, the package names will change from that of Thorntail.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 1 month
[JBoss JIRA] (TEIID-5535) CTE: Inconsistent Error Message when SELECTing a View Instead of its Definition
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5535?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5535.
-----------------------------------
Resolution: Duplicate Issue
Duplicate of TEIID-5532 - I had just reopened that issue to cover the view case as well.
> CTE: Inconsistent Error Message when SELECTing a View Instead of its Definition
> -------------------------------------------------------------------------------
>
> Key: TEIID-5535
> URL: https://issues.jboss.org/browse/TEIID-5535
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 11.1
> Environment: teiid-11.1.0 (from 01.09.2018) on WildFly Full 11.0.0.Final (WildFly Core 3.0.8.Final)
> Reporter: dalex dalex
> Assignee: Steven Hawkins
> Priority: Critical
>
> There are queries involving CTEs and set operators that can be executed and return results.
> However, creating a view based on the working queries makes these views unusable as they return an error message.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 1 month