[JBoss JIRA] (TEIID-5522) Avoid pushing join to datasource if DS cannot handle 1600+ columns
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5522?page=com.atlassian.jira.plugin... ]
Steven Hawkins moved TEIIDTOOLS-519 to TEIID-5522:
--------------------------------------------------
Project: Teiid (was: Teiid Tools)
Key: TEIID-5522 (was: TEIIDTOOLS-519)
> Avoid pushing join to datasource if DS cannot handle 1600+ columns
> -------------------------------------------------------------------
>
> Key: TEIID-5522
> URL: https://issues.jboss.org/browse/TEIID-5522
> Project: Teiid
> Issue Type: Feature Request
> Reporter: Norbert Funke
> Priority: Major
>
> Problem: I am trying to create a wide view (~5000 columns), which works across data sources fine JDV. However, when I try to create the view with a join on 2+ table from data source, the optimizer pushes down the join to the source. The current source cannot handle more then ~1600 columns.
> Example: When trying to join Member_DX1 and Member_DX2 at client, JDV pushes the enter code herecombined join to postgres as one getting the too max column error.
> /* TABLE 1 */
> CREATE VIEW Member_DX1 (
> MEMB_BID Integer
> , DX130402000000 Integer
> , DX180608000000 Integer
> , DX20401070000 Integer
> .... /* 1000 more */
> as
> SELECT dx.memb_bid
> , case dx.EPI_1_DX4 when 130402000000 then 1 else 0 END as DX130402000000
> , case dx.EPI_1_DX4 when 180608000000 then 1 else 0 END as DX180608000000
> , case dx.EPI_1_DX4 when 20401070000 then 1 else 0 END as DX20401070000
> ...
> FROM BDR.ENH_EPI_DETAIL dx
> /* TABLE 2 */
> CREATE VIEW Member_DX2 (
> MEMB_BID Integer
> , DX200102010000 Integer
> , DX90125000000 Integer
> , DX160603070000 Integer
> ... /* 1000 more ...
> SELECT dx.memb_bid /* FOREIGN TABLE */
> , case dx.EPI_1_DX4 when 200102010000 then 1 else 0 END as DX200102010000
> , case dx.EPI_1_DX4 when 90125000000 then 1 else 0 END as DX90125000000
> , case dx.EPI_1_DX4 when 160603070000 then 1 else 0 END as DX160603070000
> ...`enter code here`
> FROM BDR.ENH_EPI_DETAIL dx;
> then my query in (e.g. dBeaver) looks like this:
> SELECT * from Member_DX1 dx1
> join Member_DX2 dx2
> on dx1.MEMB_BID = dx2.MEMB_BID
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 1 month
[JBoss JIRA] (TEIID-5521) Add build plugins used by basepom to help with dependency handling
by Van Halbert (Jira)
Van Halbert created TEIID-5521:
----------------------------------
Summary: Add build plugins used by basepom to help with dependency handling
Key: TEIID-5521
URL: https://issues.jboss.org/browse/TEIID-5521
Project: Teiid
Issue Type: Task
Components: Build/Kits
Affects Versions: 12.x
Reporter: Van Halbert
Assignee: Steven Hawkins
Utilize plugins that basebom uses, which will help reduce half the headaches you go though during the productization with versions.
plugins:
* duplicate-finder-maven-plugin
* maven-dependency-plugin
* maven-dependency-versions-check-plugin
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 1 month