[JBoss JIRA] (TEIID-5604) Issue with javadoc plugin
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5604?page=com.atlassian.jira.plugin... ]
Work on TEIID-5604 started by Steven Hawkins.
---------------------------------------------
> Issue with javadoc plugin
> -------------------------
>
> Key: TEIID-5604
> URL: https://issues.jboss.org/browse/TEIID-5604
> Project: Teiid
> Issue Type: Task
> Components: Build/Kits
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.1
>
>
> With the 12.0.0 release it was missed that version.javadoc.plugin was not set in the root pom.xml - it had previously come from jboss parent. Using either the new version 3.0.1 or the old 2.10.4 (from the 11.2 jboss parent) results in a lot of javadoc issues that were previously ignored.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (TEIID-5513) Fully automate release
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5513?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-5513:
----------------------------------
Fix Version/s: 12.2
(was: 12.1)
outstanding tasks:
- doc release, javacc grammar generation / branching if needed
- adding signing, jboss.org credentials to travis
> Fully automate release
> ----------------------
>
> Key: TEIID-5513
> URL: https://issues.jboss.org/browse/TEIID-5513
> Project: Teiid
> Issue Type: Task
> Components: Build/Kits
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.2
>
>
> We should add a fully automated release on the creation of a tag.
> One outstanding task is to clean up the javacc doc generation and link that with the doc release as well.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (TEIID-4251) Built in support for Postgres DB as materialization target
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-4251?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4251:
----------------------------------
Fix Version/s: 12.2
(was: 12.1)
> Built in support for Postgres DB as materialization target
> ----------------------------------------------------------
>
> Key: TEIID-4251
> URL: https://issues.jboss.org/browse/TEIID-4251
> Project: Teiid
> Issue Type: Sub-task
> Components: Server
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.2
>
>
> If Postgres database is available along with install or assumed that it is available, then some of the materialization task can be automated, like
> - Creation of a common STATUS table
> - Creation of the materilization targets (create views on dbms)
> - On load, on undeploy and load scripts for all the materialization views
> We need to device a way this to be pluggable, such that based on success of this, we can provide additional support for other sources.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[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 resolved TEIID-5522.
-----------------------------------
Resolution: Done
Added a new method ExecutionFactory.getMaxProjectedColumns to limit how much can be pushed - this will not subdivide a single table, but will prevent joins. It also can rely on an estimate on the number of output columns, so that we don't incur running rule assign output elements again.
> 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
> Components: Misc. Connectors, Query Engine
> Reporter: Norbert Funke
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.1
>
>
> 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)
5 years, 10 months
[JBoss JIRA] (TEIID-5425) Concurrency/timing issues observed with travis builds
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5425?page=com.atlassian.jira.plugin... ]
Steven Hawkins edited comment on TEIID-5425 at 2/22/19 3:25 PM:
----------------------------------------------------------------
After the basepom changes I have not observed the materialization related issue - disregard it's still occurring.
was (Author: shawkins):
After the basepom changes I have not observed the materialization related issue.
> Concurrency/timing issues observed with travis builds
> -----------------------------------------------------
>
> Key: TEIID-5425
> URL: https://issues.jboss.org/browse/TEIID-5425
> Project: Teiid
> Issue Type: Bug
> Components: Build/Kits
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.1
>
>
> Several unit tests have been observed to fail during travis builds occasionally:
> 1. TestODBCSocketTransport.testRegClass:757 » PSQL ResultSet not positioned prope...
> 2. TestExternalMatViews.testLazyUpdate:930 expected:<2> but was:<1> (see https://api.travis-ci.org/v3/job/405801976/log.txt)
> 3. [ERROR] TestLocalConnections.testWaitForLoadTimeout:475
> 4. From https://api.travis-ci.org/v3/job/415138409/log.txt
> [ERROR] testReplication(org.teiid.systemmodel.TestReplication) Time elapsed: 35.21 s <<< FAILURE!
> java.lang.AssertionError: expected:<0.9164140964242746> but was:<0.18750528722359294>
> at org.teiid.systemmodel.TestReplication.testReplication(TestReplication.java:122)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months