February 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5657) VDB Migration Tool

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5657?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5657: ------------------------------------- Did you add the .vdb support? I thought [~shawkins] mentioned .vdb is not supported, which may be key here. I remember there were some issues last time I tried to did this but should be possible. > VDB Migration Tool > ------------------ > > Key: TEIID-5657 > URL: https://issues.jboss.org/browse/TEIID-5657 > Project: Teiid > Issue Type: Feature Request > Components: Documentation, Quick Starts, Tooling > Affects Versions: 12.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > Fix For: 12.1 > > > A migration tool will be provided to convert customer vdbs into just ddl. More than likely this will be just a single ddl file - which will probably not be acceptable to customers with large vdbs. > We have this utility already available as just a main method in one of our jars. It is anticipated that a maven repo will be distribution mechanism and minimal documentation will be provided. > There should be optional validation available for the vdb ddl at build time. This breaks down into 3 parts: > 1. static syntactic validation, potentially even fully resolving if all metadata is present. This makes sure that basic typos will be caught. > 2. providing hard errors for things that are completely removed - an error for usage of soap or function models for example. > 3. providing errors or warning for features that are not yet available - vdb imports, sources that aren't yet supported etc. > To avoid introducing a new plugin or plugging into fmp it's been suggested that the validation could be run via a generated unit test, which ties into another task which is booster, base project, or last resort an arche type that scaffolds the developer project. > This could possibly be included in the quickstarts as a means to facilitate its use. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5667) Update Infinispan Connector modules to support Infinispan 7.2 Client jars

by Van Halbert (Jira)

Van Halbert created TEIID-5667: ---------------------------------- Summary: Update Infinispan Connector modules to support Infinispan 7.2 Client jars Key: TEIID-5667 URL: https://issues.jboss.org/browse/TEIID-5667 Project: Teiid Issue Type: Enhancement Components: JDG Connector Affects Versions: 8.12.17.6_4 Reporter: Van Halbert Assignee: Steven Hawkins The Infinispan connector needs the module updated to support the Infinispan 7.2 client jar's. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5667) Update Infinispan Connector modules to support Infinispan 7.2 Client jars

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-5667?page=com.atlassian.jira.plugin... ] Van Halbert reassigned TEIID-5667: ---------------------------------- Assignee: Van Halbert (was: Steven Hawkins) > Update Infinispan Connector modules to support Infinispan 7.2 Client jars > ------------------------------------------------------------------------- > > Key: TEIID-5667 > URL: https://issues.jboss.org/browse/TEIID-5667 > Project: Teiid > Issue Type: Enhancement > Components: JDG Connector > Affects Versions: 8.12.17.6_4 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > > The Infinispan connector needs the module updated to support the Infinispan 7.2 client jar's. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5666) Clean up README.md in teiid-openshift-examples

by Van Halbert (Jira)

Van Halbert created TEIID-5666: ---------------------------------- Summary: Clean up README.md in teiid-openshift-examples Key: TEIID-5666 URL: https://issues.jboss.org/browse/TEIID-5666 Project: Teiid Issue Type: Quality Risk Components: Documentation Affects Versions: 12.1 Reporter: Van Halbert Assignee: Steven Hawkins The README.md needs to be cleaned up so that its easier to read on github. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5666) Clean up README.md in teiid-openshift-examples

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-5666?page=com.atlassian.jira.plugin... ] Van Halbert reassigned TEIID-5666: ---------------------------------- Assignee: Van Halbert (was: Steven Hawkins) > Clean up README.md in teiid-openshift-examples > ---------------------------------------------- > > Key: TEIID-5666 > URL: https://issues.jboss.org/browse/TEIID-5666 > Project: Teiid > Issue Type: Quality Risk > Components: Documentation > Affects Versions: 12.1 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Trivial > > The README.md needs to be cleaned up so that its easier to read on github. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[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 commented on TEIID-5425: --------------------------------------- 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

1
0
0 / 0

[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... ] Work on TEIID-5522 started by Steven Hawkins. --------------------------------------------- > 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

1
0
0 / 0

[JBoss JIRA] (TEIID-5645) using an alter to add a key to a view doesn't work unless columns are explicitly declared

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5645?page=com.atlassian.jira.plugin... ] Work on TEIID-5645 started by Steven Hawkins. --------------------------------------------- > using an alter to add a key to a view doesn't work unless columns are explicitly declared > ----------------------------------------------------------------------------------------- > > Key: TEIID-5645 > URL: https://issues.jboss.org/browse/TEIID-5645 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > DDL such as: > create view v as select 1 as c1, 2 as c2; > alter view v add primary key (c1); > does not work because the columns are not defined for the view until metadata validation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5508) Add community docs around openshift usage

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5508?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5508: ---------------------------------- Fix Version/s: 12.2 (was: 12.1) > Add community docs around openshift usage > ----------------------------------------- > > Key: TEIID-5508 > URL: https://issues.jboss.org/browse/TEIID-5508 > Project: Teiid > Issue Type: Quality Risk > Components: Documentation > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 12.2 > > > We should expand upon docker dealing with running Teiid in a container to reference more about running in openshift - in particular how that affects cluster, load balancing, what health checks can be used, etc. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3522) Provide Data Aggregation Extension to OData V4

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-3522?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3522: ---------------------------------- Fix Version/s: 12.2 (was: 12.1) > Provide Data Aggregation Extension to OData V4 > ---------------------------------------------- > > Key: TEIID-3522 > URL: https://issues.jboss.org/browse/TEIID-3522 > Project: Teiid > Issue Type: Feature Request > Components: OData > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2 > > > OData V4 specification defines extension for Data Aggregation http://docs.oasis-open.org/odata/odata-data-aggregation-ext/v4.0/cs01/oda... > Teiid should provide support for this extension. There is Olingo support on this yet. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2019