February 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4762) Split the configure api separately

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-4762?page=com.atlassian.jira.plugin... ] Kylin Soong updated TEIID-4762: ------------------------------- Description: current config api together with the fraction, after some investigation, separate it from fractions should be better. [1] is wildfly config api which represent all wildfly subsystems. [1] https://github.com/wildfly-swarm/wildfly-config-api was:current config api together with the fraction, after some investigation, separate it from fractions should be better. > Split the configure api separately > ---------------------------------- > > Key: TEIID-4762 > URL: https://issues.jboss.org/browse/TEIID-4762 > Project: Teiid > Issue Type: Task > Components: Embedded > Affects Versions: 9.3 > Reporter: Kylin Soong > Assignee: Kylin Soong > Fix For: 9.3 > > > current config api together with the fraction, after some investigation, separate it from fractions should be better. > [1] is wildfly config api which represent all wildfly subsystems. > [1] https://github.com/wildfly-swarm/wildfly-config-api -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4762) Split the configure api separately

by Kylin Soong (JIRA)

Kylin Soong created TEIID-4762: ---------------------------------- Summary: Split the configure api separately Key: TEIID-4762 URL: https://issues.jboss.org/browse/TEIID-4762 Project: Teiid Issue Type: Task Components: Embedded Affects Versions: 9.3 Reporter: Kylin Soong Assignee: Kylin Soong Fix For: 9.3 current config api together with the fraction, after some investigation, separate it from fractions should be better. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3825) Add a wildfly-swarm-teiid Fraction for running teiid as an uberjar

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-3825?page=com.atlassian.jira.plugin... ] Kylin Soong updated TEIID-3825: ------------------------------- Fix Version/s: 9.3 (was: 9.2) > Add a wildfly-swarm-teiid Fraction for running teiid as an uberjar > ------------------------------------------------------------------ > > Key: TEIID-3825 > URL: https://issues.jboss.org/browse/TEIID-3825 > Project: Teiid > Issue Type: Feature Request > Components: Embedded > Affects Versions: 9.0 > Reporter: Kylin Soong > Assignee: Kylin Soong > Fix For: 9.3 > > > Fractions within WildFly Swarm are roughly equivalent to subsystems within WildFly, we have teiid subsystem in Server mode, so I think a Fraction is necessary to run teiid with Swarm. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4636) In the SWARM readme's, need to indicate the URL to connect

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-4636?page=com.atlassian.jira.plugin... ] Kylin Soong updated TEIID-4636: ------------------------------- Fix Version/s: 9.3 (was: 9.2) > In the SWARM readme's, need to indicate the URL to connect > ---------------------------------------------------------- > > Key: TEIID-4636 > URL: https://issues.jboss.org/browse/TEIID-4636 > Project: Teiid > Issue Type: Enhancement > Components: Quick Starts > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Minor > Fix For: 9.3 > > > The quickstarts needs to include the information (i.e, URL, username, password, etc.) needed to connect to the swarm example. > Per Kylin: > By default 0.0.0.0 be bound as IP, 31000 as port. To bind a specific IP use system properties > --- > -Dswarm.bind.address=127.0.0.1 > --- > Some Fractions use a system properties to change the port number, but teiid not support it at moment. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3624) No way to associate enterprise data types in dynamic vdb constructs

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3624?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3624: --------------------------------------- Schema scoping is even more difficult than I had anticipated - all logic dealing with types will need to change. We also have a conceptual issue with the ddl logic - that goes beyond datatype resolving. The usage of set schema allows for the definition of the schemas to be interleaved, however our notion of resolving order is only from within a schema. We may need to make resolving order a global concern. > No way to associate enterprise data types in dynamic vdb constructs > ------------------------------------------------------------------- > > Key: TEIID-3624 > URL: https://issues.jboss.org/browse/TEIID-3624 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 9.3 > > > I don't find any doc's on how to define enterprise data types in a dynamic vdb. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4738) Change JDG Materialization to use Upsert

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4738?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4738: ------------------------------------ As much as I want to yank out the original materialization logic, it maybe better to just document how someone could use UPSERT in a dynamic vdb xml to use the new UPSERT feature. Deprecate the current usage and tooling. And we'll need tool enhancements to utilize the new option. > Change JDG Materialization to use Upsert > ---------------------------------------- > > Key: TEIID-4738 > URL: https://issues.jboss.org/browse/TEIID-4738 > Project: Teiid > Issue Type: Enhancement > Components: JDG Connector > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 9.3 > > > Change materialization to use the new Upsert feature. > This will enable the removing of the Alias and Staging caches. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4757) Support Postgres OLEDB driver for Teiid

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4757?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4757: ------------------------------------- That does not sound very promising :( for open source project. So, either the technology is dead or project is. > Support Postgres OLEDB driver for Teiid > --------------------------------------- > > Key: TEIID-4757 > URL: https://issues.jboss.org/browse/TEIID-4757 > Project: Teiid > Issue Type: Feature Request > Components: ODBC > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 9.3 > > > Provide support for Postgres OLEDB driver to connect to Teiid in issuing the queries. This will help .NET applications to be written to the Teiid. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4738) Change JDG Materialization to use Upsert

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4738?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4738: ------------------------------------ I am. For the Teiid / JDG use case, I do think this is the better option and easier to control. As for a usage just for the object translator, its not very appealing and complicates the process. And I think moving forward, and not having to account for the CacheNameProxy and DDLHandler, will make it easier to do other thing.s > Change JDG Materialization to use Upsert > ---------------------------------------- > > Key: TEIID-4738 > URL: https://issues.jboss.org/browse/TEIID-4738 > Project: Teiid > Issue Type: Enhancement > Components: JDG Connector > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 9.3 > > > Change materialization to use the new Upsert feature. > This will enable the removing of the Alias and Staging caches. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4757) Support Postgres OLEDB driver for Teiid

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4757?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4757: --------------------------------------- pgFoundary has been down since last week, but the ftp site is still up. From there it looks like the open source driver hasn't changed since 2006: https://ftp.postgresql.org/pub/projects/pgFoundry/oledb/PgOleDb/1.0.0.20/ I can use that source to determine additional support that may be needed, but it would be good to have confirmation on the driver before committing to the work. > Support Postgres OLEDB driver for Teiid > --------------------------------------- > > Key: TEIID-4757 > URL: https://issues.jboss.org/browse/TEIID-4757 > Project: Teiid > Issue Type: Feature Request > Components: ODBC > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 9.3 > > > Provide support for Postgres OLEDB driver to connect to Teiid in issuing the queries. This will help .NET applications to be written to the Teiid. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4738) Change JDG Materialization to use Upsert

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4738?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4738: --------------------------------------- > That only UPSERT will be used for JDG cache sources or any other map cache that uses object translator. As long as you are comfortable with that breaking change - both for the object model, and for the teiid metadata - then yes. > Change JDG Materialization to use Upsert > ---------------------------------------- > > Key: TEIID-4738 > URL: https://issues.jboss.org/browse/TEIID-4738 > Project: Teiid > Issue Type: Enhancement > Components: JDG Connector > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 9.3 > > > Change materialization to use the new Upsert feature. > This will enable the removing of the Alias and Staging caches. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 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 2017