October 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3498) missing message keys in function descriptions

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3498?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3498. --------------------------------- > missing message keys in function descriptions > --------------------------------------------- > > Key: TEIID-3498 > URL: https://issues.jboss.org/browse/TEIID-3498 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > Function metadata contains missing an incorrect entries - such as seen in TestMMDatabaseMetadata.testGetFunctionColumns -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3387) MongoDB resource adapter doesn't support all authentication mechanisms

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3387?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3387. --------------------------------- > MongoDB resource adapter doesn't support all authentication mechanisms > ---------------------------------------------------------------------- > > Key: TEIID-3387 > URL: https://issues.jboss.org/browse/TEIID-3387 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.10 > Reporter: Burak Serdar > Assignee: Ramesh Reddy > Labels: Beta2 > Fix For: 8.11 > > > It appears like mongodb resource adapter only supports Database, Username, Password, and RemoteServerList properties. It does not support: > - SSL connections > - a way to specify authenticationDatabase for MONGODB-CR mechanism -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3496) update status table in ON_VDB_DROP_SCRIPT should point to correct name and schemaname

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3496?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3496. --------------------------------- > update status table in ON_VDB_DROP_SCRIPT should point to correct name and schemaname > ------------------------------------------------------------------------------------- > > Key: TEIID-3496 > URL: https://issues.jboss.org/browse/TEIID-3496 > Project: Teiid > Issue Type: Bug > Components: Quick Starts > Reporter: Kylin Soong > Assignee: Kylin Soong > Fix For: 8.11 > > > This may be caused by miss spelling , in "teiid_rel:ON_VDB_DROP_SCRIPT" section, the name and schemaname should point to stockPricesMatView and StocksMatModel, but current looks > ~~~ > <model name="StocksMatModel" type="VIRTUAL"> > <metadata type="DDL"><![CDATA[ > CREATE view stockPricesMatView > ... > ) OPTIONS( > ... > "teiid_rel:ON_VDB_DROP_SCRIPT" 'DELETE FROM Accounts.status WHERE Name=''stock'' AND schemaname = ''Stocks''', > ~~~ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3486) Add array data type support to Loopback Translator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3486?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3486. --------------------------------- > Add array data type support to Loopback Translator > -------------------------------------------------- > > Key: TEIID-3486 > URL: https://issues.jboss.org/browse/TEIID-3486 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.11 > > > Adding the array data type support will be nice for testing purposes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3747) Deploying a .vdb where a dynamic vdb has already been deployed, fails due to duplicates

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3747?page=com.atlassian.jira.plugin... ] Van Halbert edited comment on TEIID-3747 at 10/9/15 1:05 PM: ------------------------------------------------------------- Designer allows you to redeploy the same named VDB over and over. Why would it matter that some else deployed the VDB and now a different user can't. I think the issue has to do with the types of VDB's are different and the deployment mechanism in Teiid doesn't recognize them as being the same (even though they use different artifact types). was (Author: van.halbert): Designer allows you to redeploy the same named VDB over and over. Why would it matter that some else deployed the VDB and now a different user can't. I think the issue has to do with the types of VDB's are different and the deployment mechanism in Teiid doesn't recognize them as being the same (even though the use different artifact types). > Deploying a .vdb where a dynamic vdb has already been deployed, fails due to duplicates > --------------------------------------------------------------------------------------- > > Key: TEIID-3747 > URL: https://issues.jboss.org/browse/TEIID-3747 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.1.6_2 > Reporter: Van Halbert > Assignee: Steven Hawkins > > deployed a dynamic vdb using CLI: deploy teiidfiles/vdb/portfolio-vdb.xml > then in Designer, tried to deploy the same named VDB, but as a .vdb and the deployment fails with errors indicating duplicate service: > 11:26:31,301 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.unit."Portfolio.vdb".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."Portfolio.vdb".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "Portfolio.vdb" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [jboss-as-server-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_55] > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.teiid.ds-listener.Portfolio.1./accounts-ds is already registered > at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3426) Salesforce importer does not set cardinalities

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3426?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3426. --------------------------------- > Salesforce importer does not set cardinalities > ---------------------------------------------- > > Key: TEIID-3426 > URL: https://issues.jboss.org/browse/TEIID-3426 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector > Reporter: Burak Serdar > Assignee: Steven Hawkins > Fix For: 8.11 > > > The salesforce importer does not set cardinalities for salesforce objects it imports. That is causing problems with joins involving more than two tables, and when there are no criteria on a large table. If the large table is joined later, it retrieves all the rows of that table and joins them with the result of the previous joins. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3468) Exception with same table name in materialization procedures

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3468?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3468. --------------------------------- > Exception with same table name in materialization procedures > ------------------------------------------------------------ > > Key: TEIID-3468 > URL: https://issues.jboss.org/browse/TEIID-3468 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.5 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > The sql defining the mat view procedures is not qualifying the reference to the schemaName, and throwing an exception when the scalar subquery returns more than 1 value. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3747) Deploying a .vdb where a dynamic vdb has already been deployed, fails due to duplicates

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3747?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3747: ------------------------------------ Designer allows you to redeploy the same named VDB over and over. Why would it matter that some else deployed the VDB and now a different user can't. I think the issue has to do with the types of VDB's are different and the deployment mechanism in Teiid doesn't recognize them as being the same (even though the use different artifact types). > Deploying a .vdb where a dynamic vdb has already been deployed, fails due to duplicates > --------------------------------------------------------------------------------------- > > Key: TEIID-3747 > URL: https://issues.jboss.org/browse/TEIID-3747 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.1.6_2 > Reporter: Van Halbert > Assignee: Steven Hawkins > > deployed a dynamic vdb using CLI: deploy teiidfiles/vdb/portfolio-vdb.xml > then in Designer, tried to deploy the same named VDB, but as a .vdb and the deployment fails with errors indicating duplicate service: > 11:26:31,301 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.unit."Portfolio.vdb".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."Portfolio.vdb".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "Portfolio.vdb" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [jboss-as-server-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_55] > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.teiid.ds-listener.Portfolio.1./accounts-ds is already registered > at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3746) Add ETL functionality to Teiid

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3746?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3746: --------------------------------------- There needs to be a little more here to flesh this out. You are mentioning both ETL and specifically a database migration scenario. On the ETL side our basic support is just with standard SQL - insert into target ... select ... What supporting logic / tooling are you thinking about around that to round out an ETL story? And on database migration there are quite a few open source projects in that space. Are you proposing developing similar functionality in Teiid or simply offering something like http://flywaydb.org/ in tandem? > Add ETL functionality to Teiid > ------------------------------ > > Key: TEIID-3746 > URL: https://issues.jboss.org/browse/TEIID-3746 > Project: Teiid > Issue Type: Feature Request > Reporter: Jérôme Fenal > Assignee: Steven Hawkins > > Teeid can offer schema discovery, schema creation, data massaging from one format to another, and handle writes. > ETL is all about that: > - Extract > - Tranform > - Load > in batch mode. > With the dawn of batch mode in JEE7, it could be interesting to add ETL functionality, possibly in the form of a continuous datamover, or a batch datamover, which could also be used in a complete database migration scenario. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3747) Deploying a .vdb where a dynamic vdb has already been deployed, fails due to duplicates

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3747?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3747: ------------------------------------- Not sure what you looking for expected behavior, but the rule is no same named VDBs can co-exist at the same time in the container. It applies equally well to Dynamic VDBs or .vdb or combination of both. Designer should check if there is an existing VDB with same "name" along with their "deployed" names. Both should not match, if there are collisions you will see some sort of an error like above. If this satisfies as answer, please move this into Designer JIRA Issues. > Deploying a .vdb where a dynamic vdb has already been deployed, fails due to duplicates > --------------------------------------------------------------------------------------- > > Key: TEIID-3747 > URL: https://issues.jboss.org/browse/TEIID-3747 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.1.6_2 > Reporter: Van Halbert > Assignee: Steven Hawkins > > deployed a dynamic vdb using CLI: deploy teiidfiles/vdb/portfolio-vdb.xml > then in Designer, tried to deploy the same named VDB, but as a .vdb and the deployment fails with errors indicating duplicate service: > 11:26:31,301 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.unit."Portfolio.vdb".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."Portfolio.vdb".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "Portfolio.vdb" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [jboss-as-server-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_55] > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.teiid.ds-listener.Portfolio.1./accounts-ds is already registered > at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2015