July 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3544) teiid-odata-*.war not deploying in EAP when using domain

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3544?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3544: --------------------------------------- Ah, yes. So we'll pick this up with some later productization. > teiid-odata-*.war not deploying in EAP when using domain > -------------------------------------------------------- > > Key: TEIID-3544 > URL: https://issues.jboss.org/browse/TEIID-3544 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7.1.6_2 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 8.7.1.6_2 > > > The Teiid odata war, located: > modules/system/layers/dv/org/jboss/teiid/main/deployments/teiid-odata-8.7.1.6_2-redhat-2.war > was not being deployed. It's working in standalone. > The workaround in domain mode is to re-deploy the war using the admin console. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3544) teiid-odata-*.war not deploying in EAP when using domain

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3544?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3544: ------------------------------------- master has only "HA" profile group, does not have others, so I am thinking it does not require 501 > teiid-odata-*.war not deploying in EAP when using domain > -------------------------------------------------------- > > Key: TEIID-3544 > URL: https://issues.jboss.org/browse/TEIID-3544 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7.1.6_2 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 8.7.1.6_2 > > > The Teiid odata war, located: > modules/system/layers/dv/org/jboss/teiid/main/deployments/teiid-odata-8.7.1.6_2-redhat-2.war > was not being deployed. It's working in standalone. > The workaround in domain mode is to re-deploy the war using the admin console. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3544) teiid-odata-*.war not deploying in EAP when using domain

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3544?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3544: --------------------------------------- Do 501 and the other commits need to be made on master as well? > teiid-odata-*.war not deploying in EAP when using domain > -------------------------------------------------------- > > Key: TEIID-3544 > URL: https://issues.jboss.org/browse/TEIID-3544 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7.1.6_2 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 8.7.1.6_2 > > > The Teiid odata war, located: > modules/system/layers/dv/org/jboss/teiid/main/deployments/teiid-odata-8.7.1.6_2-redhat-2.war > was not being deployed. It's working in standalone. > The workaround in domain mode is to re-deploy the war using the admin console. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3573) Infinispan-dsl-cache translator: Operator <> incorrectly handles NULL values

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3573?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3573: --------------------------------------- IS NULL/IS NOT NULL is appropriate from the user query when you are explicitly testing for null. In this case we are not testing null, rather intNum <> 1. It's returning true for a null intNum - that is not expected with 3 valued SQL (but could be the result in 2 valued systems). > Unless you're thinking of adding an additional filtering in the translator such that when a column that's used in the WHERE clause is returned that has a null value, and NULL or ISNULL checks are not used, then filter out the row? Yes, if they are a 2 valued system, then we should change the translator logic to compensate. So if it sees where intNum<>1 it would need to produce "intNum<>1 and intNum IS NOT NULL". If that's not generally something that the translator can handle we can look at letting the engine compensate, but that could come with a lot of restrictions. > Infinispan-dsl-cache translator: Operator <> incorrectly handles NULL values > ---------------------------------------------------------------------------- > > Key: TEIID-3573 > URL: https://issues.jboss.org/browse/TEIID-3573 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Filip Elias > Assignee: Van Halbert > > Operator '<>' returns true for NULL <> 1 > Example: > {code} > select intKey,intNum from smallA where intNum<>1 > {code} > It returns also rows which have NULL in column intNum > I believe that NULL <> 1 is not true in SQL. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3544) teiid-odata-*.war not deploying in EAP when using domain

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3544?page=com.atlassian.jira.plugin... ] Van Halbert edited comment on TEIID-3544 at 7/24/15 11:40 AM: -------------------------------------------------------------- added: /server-group=other-server-group/deployment=teiid-odata-${project.version}.war:add(enabled=true) PR: https://github.com/teiid/teiid/pull/501 was (Author: van.halbert): added: /server-group=other-server-group/deployment=teiid-odata-${project.version}.war:add(enabled=true) > teiid-odata-*.war not deploying in EAP when using domain > -------------------------------------------------------- > > Key: TEIID-3544 > URL: https://issues.jboss.org/browse/TEIID-3544 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7.1.6_2 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 8.7.1.6_2 > > > The Teiid odata war, located: > modules/system/layers/dv/org/jboss/teiid/main/deployments/teiid-odata-8.7.1.6_2-redhat-2.war > was not being deployed. It's working in standalone. > The workaround in domain mode is to re-deploy the war using the admin console. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3544) teiid-odata-*.war not deploying in EAP when using domain

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3544?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3544: ------------------------------------ added: /server-group=other-server-group/deployment=teiid-odata-${project.version}.war:add(enabled=true) > teiid-odata-*.war not deploying in EAP when using domain > -------------------------------------------------------- > > Key: TEIID-3544 > URL: https://issues.jboss.org/browse/TEIID-3544 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7.1.6_2 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 8.7.1.6_2 > > > The Teiid odata war, located: > modules/system/layers/dv/org/jboss/teiid/main/deployments/teiid-odata-8.7.1.6_2-redhat-2.war > was not being deployed. It's working in standalone. > The workaround in domain mode is to re-deploy the war using the admin console. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3589) MongoDB metadata import fails with NPE

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3589?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3589: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1246153|https://bugzilla.redhat.com/show_bug.cgi?id=1246153] from NEW to MODIFIED > MongoDB metadata import fails with NPE > -------------------------------------- > > Key: TEIID-3589 > URL: https://issues.jboss.org/browse/TEIID-3589 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.7.1.6_2 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Labels: Alpha2 > Fix For: 8.7.1.6_2, 8.12 > > > Deploying the following dynamic vdb fails with a NullPointerException when Teiid Connection importer is used: > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <vdb name="mongo" version="1"> > <description>Importer VDB</description> > <property name="UseConnectorMetadata" value="true" /> > <property name="deployment-name" value="mongo-vdb.xml" /> > <model name="importVDBSrcModel"> > <source name="importVDBSrcModel" translator-name="mongodb" connection-jndi-name="java:/mongoDS" /> > </model> > </vdb> > The resource adapter is defined as: > <resource-adapter id="mongoDS"> > <module slot="main" id="org.jboss.teiid.resource-adapter.mongodb"/> > <transaction-support>NoTransaction</transaction-support> > <connection-definitions> > <connection-definition class-name="org.teiid.resource.adapter.mongodb.MongoDBManagedConnectionFactory" jndi-name="java:/mongoDS" enabled="true" use-java-context="true" pool-name="mongoDS"> > <config-property name="Database"> > bqt > </config-property> > <config-property name="RemoteServerList"> > vmgdb01.mw.lab.eng.bos.redhat.com:27017 > </config-property> > <config-property name="Username"> > dv > </config-property> > <config-property name="Password"> > dv > </config-property> > </connection-definition> > </connection-definitions> > </resource-adapter> > Server log: > 16:46:49,793 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "mongo-vdb.xml" (runtime-name: "mongo-vdb.xml") > 16:46:49,809 DEBUG [org.teiid.RUNTIME] (MSC service thread 1-5) VDB mongo-vdb.xml has been parsed. > 16:46:49,835 INFO [org.teiid.RUNTIME] (MSC service thread 1-1) TEIID50029 VDB mongo.1 model "importVDBSrcModel" metadata is currently being loaded. Start Time: 7/23/15 4:46 PM > 16:46:49,869 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015859: Deployed "mongo-vdb.xml" (runtime-name : "mongo-vdb.xml") > 16:46:50,626 WARN [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50036 VDB mongo.1 model "importVDBSrcModel" metadata failed to load. Reason:java.lang.NullPointerException: java.lang.NullPointerException > at org.teiid.translator.mongodb.MongoDBMetadataProcessor.addTable(MongoDBMetadataProcessor.java:92) > at org.teiid.translator.mongodb.MongoDBMetadataProcessor.process(MongoDBMetadataProcessor.java:57) > at org.teiid.translator.mongodb.MongoDBMetadataProcessor.process(MongoDBMetadataProcessor.java:38) > at org.teiid.translator.ExecutionFactory.getMetadata(ExecutionFactory.java:935) [teiid-api-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3] > at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:73) [teiid-engine-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3] > at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) [teiid-engine-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3] > at org.teiid.jboss.VDBService$6.run(VDBService.java:395) [teiid-jboss-integration-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3] > at org.teiid.jboss.VDBService$7.run(VDBService.java:442) [teiid-jboss-integration-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_79] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_79] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3582) Add the query requestID to all lines for that query in the logs

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3582?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-3582: ------------------------------------- Fix Version/s: 8.12 Assignee: (was: Steven Hawkins) > Add the query requestID to all lines for that query in the logs > --------------------------------------------------------------- > > Key: TEIID-3582 > URL: https://issues.jboss.org/browse/TEIID-3582 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Van Halbert > Fix For: 8.12 > > > Currently when running a query, the logs show the requestId on most of the lines but not all, especially CONNECTOR. > for example, the following line doesn't have it: > 14:13:34,071 DEBUG [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue13) Source-specific command: .... > That's the problem. When lots of queries are running, user wants to grep through the log for that requestid and get just that one query's stuff. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3480) External Materialization status

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3480?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3480: --------------------------------------- Unless we try to reflect the status in an active way on the metadata record, it doesn't seem like a good idea to have a system table rely on issuing subqueries to determine the status. It would probably be better to introduce a procedure that will return the db info for a given mat view. > External Materialization status > ------------------------------- > > Key: TEIID-3480 > URL: https://issues.jboss.org/browse/TEIID-3480 > Project: Teiid > Issue Type: Enhancement > Components: Server > Affects Versions: 8.4 > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 8.12 > > > When external materialization is configured with "STATUS" table, then Teiid should expose those stats over CLI and in the web-console. Currently the internal materialization does show status, need to expand to the external matviews. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3485) Decompose joins only works with a single join

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3485?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3485. ----------------------------------- Fix Version/s: (was: 8.12) Resolution: Won't Fix Making this work with a non-removable view layer isn't straight-forward. Marking as won't fix. > Decompose joins only works with a single join > --------------------------------------------- > > Key: TEIID-3485 > URL: https://issues.jboss.org/browse/TEIID-3485 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > A multi-way join or joins through non-removable view layers cannot currently be decomposed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2015