[JBoss JIRA] (TEIID-2482) Allow the use of the enhanced join for left outer joins
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2482?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2482:
---------------------------------------
The second commits gives the planner more flexibility to not push down sorts that it believes will not be necessary. The only drawback to this optimization is that there is no hint to override the behavior should a pushdown sort be needed. This commit is currently not needed for backporting.
> Allow the use of the enhanced join for left outer joins
> -------------------------------------------------------
>
> Key: TEIID-2482
> URL: https://issues.jboss.org/browse/TEIID-2482
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.4
>
>
> Left equi outer joins are currently only implemented using the full sort merge join and would benefit from using the enhanced merge when the inner side is relatively small.
--
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
12 years, 11 months
[JBoss JIRA] (TEIID-2486) Standalone CLI script has a small required change to work with EAP 6.1
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2486?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2486.
-----------------------------------
Resolution: Done
Confirmed the fix is fine for 8.4 with Ramesh.
> Standalone CLI script has a small required change to work with EAP 6.1
> ----------------------------------------------------------------------
>
> Key: TEIID-2486
> URL: https://issues.jboss.org/browse/TEIID-2486
> Project: Teiid
> Issue Type: Bug
> Components: Build/Kits
> Affects Versions: 8.4
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Minor
> Fix For: 8.4
>
>
> The following command doesn't support the "name" attribute:
> /subsystem=threads/bounded-queue-thread-pool=teiid-async:add(name=teiid-async, max-threads=4, queue-length=100)
> This is the same issue seen in the domain script. So the command should be changed to be:
> /subsystem=threads/bounded-queue-thread-pool=teiid-async:add(max-threads=4, queue-length=100)
--
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
12 years, 11 months
[JBoss JIRA] (TEIID-2498) Insert with simple select ? fails
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2498:
-------------------------------------
Summary: Insert with simple select ? fails
Key: TEIID-2498
URL: https://issues.jboss.org/browse/TEIID-2498
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Minor
Fix For: 8.4
A query such as
Insert Into TableA( col1, col2 ) Select ?, ?
will fail as we are not expecting to implicitly resolve references in an insert query expression.
--
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
12 years, 11 months
[JBoss JIRA] (TEIID-2497) Add support for DECODE(column, column_value, column_to_replace_with)
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-2497?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-2497:
------------------------------------
The following worked:
Select IntKey, SUM(CASE StringKey WHEN '11' THEN IntNum END) As NewColumnA,
SUM(CASE StringKey WHEN '12' THEN IntNum END) As NewColumnB,
SUM(CASE StringKey WHEN '13' THEN IntNum END) As NewColumnC
FROM BQT1.SmallA
Group By IntKey
I assume you can close this feature request as being satisfied.
> Add support for DECODE(column, column_value, column_to_replace_with)
> --------------------------------------------------------------------
>
> Key: TEIID-2497
> URL: https://issues.jboss.org/browse/TEIID-2497
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Affects Versions: 7.7.6
> Reporter: Van Halbert
> Assignee: Steven Hawkins
>
> Looking at pivot and trying to use it like:
> Select salesperson, SUM(DECODE(product, 'CarA', amount)) as ProductCarA,
> SUM(DECODE(product, 'CarB', amount)) as ProductCarB,
> SUM(DECODE(product, 'CarC', amount)) as ProductCarC
> From SALES
> Group By salesperson
> Teiid's Decode requires you to know the value to substitute, with this option, it can be dynamically substituted at run time.
>
> See: http://www.clearpeaks.com/blog/data-warehousing/pivot-data-in-sql
--
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
12 years, 11 months
[JBoss JIRA] (TEIID-2497) Add support for DECODE(column, column_value, column_to_replace_with)
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2497?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2497.
-----------------------------------
Resolution: Rejected
DECODE is just a short cut for a case expression
DECODE(product, 'CarB', amount)
can be expressed as:
CASE product WHEN 'CarB' THEN amount END
> Add support for DECODE(column, column_value, column_to_replace_with)
> --------------------------------------------------------------------
>
> Key: TEIID-2497
> URL: https://issues.jboss.org/browse/TEIID-2497
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Affects Versions: 7.7.6
> Reporter: Van Halbert
> Assignee: Steven Hawkins
>
> Looking at pivot and trying to use it like:
> Select salesperson, SUM(DECODE(product, 'CarA', amount)) as ProductCarA,
> SUM(DECODE(product, 'CarB', amount)) as ProductCarB,
> SUM(DECODE(product, 'CarC', amount)) as ProductCarC
> From SALES
> Group By salesperson
> Teiid's Decode requires you to know the value to substitute, with this option, it can be dynamically substituted at run time.
>
> See: http://www.clearpeaks.com/blog/data-warehousing/pivot-data-in-sql
--
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
12 years, 11 months