April 2012 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-1889) Standardize logging in Teiid

by Ramesh Reddy (Created) (JIRA)

Standardize logging in Teiid ---------------------------- Key: TEIID-1889 URL: https://issues.jboss.org/browse/TEIID-1889 Project: Teiid Issue Type: Task Reporter: Ramesh Reddy Assignee: Steven Hawkins Per http://community.jboss.org/wiki/HowToLogInJBossProjects rework the logging to include the id for all the messages > INFO -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

6
7
0 / 0

[JBoss JIRA] (TEIID-1906) Settting a VDB with data roles from Teiid Designer 7.5 iand deploying to Teiid 8 get a parser error

by Sunil Varma (JIRA)

Sunil Varma created TEIID-1906: ---------------------------------- Summary: Settting a VDB with data roles from Teiid Designer 7.5 iand deploying to Teiid 8 get a parser error Key: TEIID-1906 URL: https://issues.jboss.org/browse/TEIID-1906 Project: Teiid Issue Type: Bug Components: Common, Tools Affects Versions: 8.0 Reporter: Sunil Varma Assignee: Steven Hawkins When I try to deploy a VDB with data roles set via teiid Designer to Teiid 8 I get a parser error and the VDB fails to deploy. If I remove the data roles then the VDB deploys and I can access it. Below is the stack trace: Iam using Teiid Designer 7.5 & Teiid 8 Alpha1 on Jboss AS 7.1.0.CR1b. /////// 04:15:42,233 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) Starting deployment of "H2Northwind.vdb" 04:15:42,244 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.deployment.unit."H2Northwind.vdb".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."H2Northwind.vdb".PARSE: Failed to process phase PARSE of deployment "H2Northwind.vdb" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_27] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_27] at java.lang.Thread.run(Thread.java:662) [:1.6.0_27] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[19,13] Message: Unexpected element 'allow-alter' encountered at org.teiid.jboss.VDBParserDeployer.parseVDBXML(VDBParserDeployer.java:117) at org.teiid.jboss.VDBParserDeployer.scanVDB(VDBParserDeployer.java:84) at org.teiid.jboss.VDBParserDeployer.scanVDB(VDBParserDeployer.java:79) at org.teiid.jboss.VDBParserDeployer.deploy(VDBParserDeployer.java:68) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b] ... 5 more Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[19,13] Message: Unexpected element 'allow-alter' encountered at org.teiid.adminapi.impl.VDBMetadataParser.parsePermission(VDBMetadataParser.java:179) at org.teiid.adminapi.impl.VDBMetadataParser.parseDataRole(VDBMetadataParser.java:140) at org.teiid.adminapi.impl.VDBMetadataParser.parseVDB(VDBMetadataParser.java:94) at org.teiid.adminapi.impl.VDBMetadataParser.unmarshell(VDBMetadataParser.java:63) at org.teiid.jboss.VDBParserDeployer.parseVDBXML(VDBParserDeployer.java:107) ... 9 more 04:15:42,247 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report JBAS014777: Services which failed to start: service jboss.deployment.unit."H2Northwind.vdb".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."H2Northwind.vdb".PARSE: Failed to process phase PARSE of deployment "H2Northwind.vdb" ///////////end stack trace -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

3
2
0 / 0

[JBoss JIRA] (TEIID-1895) Properly escape the column references for Excel based data

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-1895: ----------------------------------- Summary: Properly escape the column references for Excel based data Key: TEIID-1895 URL: https://issues.jboss.org/browse/TEIID-1895 Project: Teiid Issue Type: Bug Components: JDBC Connector Reporter: Ramesh Reddy Assignee: Steven Hawkins Currently when Excel based data is used through Dynamic VDB feature the JDBCODBC Driver reports the metadata in-compatible format thus when the Teiid issues the query to the source it some times sees issues like [Prepared Values: [] SQL: SELECT `C:\testing\abcd`.`Sheet1$`.`Name`, `C:\testing\abcd`.`Sheet1$`.`Address`, `C:\testing\abcd`.`Sheet1$`.`Country`, `C:\testing\abcd`.`Sheet1$`.`ZipCode` FROM `C:\testing\abcd`.`Sheet1$`] SQLState: -3010 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
5
0 / 0

[JBoss JIRA] (TEIID-1898) In Version 8, can the Teiid-<version>-client.jar (JDBC driver) be renamed because it causes confusion with the Teiid-client-<version>.jar used in the server

by Van Halbert (JIRA)

Van Halbert created TEIID-1898: ---------------------------------- Summary: In Version 8, can the Teiid-<version>-client.jar (JDBC driver) be renamed because it causes confusion with the Teiid-client-<version>.jar used in the server Key: TEIID-1898 URL: https://issues.jboss.org/browse/TEIID-1898 Project: Teiid Issue Type: Enhancement Components: Build/Kits Affects Versions: 8.0 Reporter: Van Halbert Assignee: Steven Hawkins The close naming between the teiid jdbc driver (teiid-<version>-client.jar) and the server jar (teiid-client-<version>.jar) is causing confusion as which one goes where. It is requested that one of the 2 jar's names be changed, maybe the jdbc driver to something like teiid-jdbc-<version>.jar. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

3
4
0 / 0

[JBoss JIRA] (TEIID-1851) run.bat in simpleclient for teiid 7.5 incorrect path

by Mike Bailey (Created) (JIRA)

run.bat in simpleclient for teiid 7.5 incorrect path ---------------------------------------------------- Key: TEIID-1851 URL: https://issues.jboss.org/browse/TEIID-1851 Project: Teiid Issue Type: Bug Components: Common Affects Versions: 7.5 Environment: Windows 7 Reporter: Mike Bailey Assignee: Steven Hawkins Priority: Minor following the instructions in the quick start guide and the README for the simpleclient, the command fails when run on windows. run.bat localhost 31000 dynamicportfolio "select * from tables" This part of the run.bat is incorrect: rem Second one adds the Teiid client set TEIID_PATH=../lib/teiid-7.5.0.Final-client.jar should be: rem Second one adds the Teiid client set TEIID_PATH=../../lib/teiid-7.5.0.Final-client.jar -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

4
3
0 / 0

[JBoss JIRA] (TEIID-1819) Reading multi entity data from a single data file

by Peter Larsen (Created) (JIRA)

Reading multi entity data from a single data file ------------------------------------------------- Key: TEIID-1819 URL: https://issues.jboss.org/browse/TEIID-1819 Project: Teiid Issue Type: Feature Request Components: Connector API Environment: Any Reporter: Peter Larsen Assignee: Steven Hawkins A common problem for data files is the concept of multiple data sets inclosed in the same file. An example is a data file of accounts receivable orders. You'll export at least two logical entities: Orders and OrderLines. Each of the two entities have very different data sets; the relate (OrderLines belong to a particular Order) and there are a dynamic number of OrderLines per Order. A common way to differentiate is to put a special "record type" selector as the first field in each record. Ie. A and B. The load program will based on this selector apply different templates to map the columns, and it will also know that the OrderLines are associated with the Order above it and create that relation column ID in the out put. Example: ;selector=A,orderdate,ordernumber,customernumber,ordertotal,ordertax ;selector=B,lineno,itemno,description,quantity,priceach,pricetotal A,10-dec-2011,12345,3322,3000,222 B,1,123,Sprockets Black,30,50,1500 B,2,333,Sprockets Blue,300,5,1500 A,11-dec-2011,12346,3311,..... etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

5
14
0 / 0

[JBoss JIRA] (TEIID-1829) Clarify source warnings

by Steven Hawkins (Created) (JIRA)

Clarify source warnings ----------------------- Key: TEIID-1829 URL: https://issues.jboss.org/browse/TEIID-1829 Project: Teiid Issue Type: Quality Risk Components: JDBC Driver Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.6 When a warning is added through an ExecutionContext, the client receives the exception wrapped by a SourceException, then wrapped as a SQLException. The issues with this are that the SourceException class is not expressly public and there is an unnecessary level of wrapping. We should introduce a TeiddSQLWarning for non-partial results warnings that would contain source/model information and prevent the unnecessary wrapping. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

3
4
0 / 0

[JBoss JIRA] (TEIID-1878) Problem with accessing custom generated materialized views

by Andriy Rokhmanov (Created) (JIRA)

Problem with accessing custom generated materialized views ---------------------------------------------------------- Key: TEIID-1878 URL: https://issues.jboss.org/browse/TEIID-1878 Project: Teiid Issue Type: Bug Affects Versions: 7.6 Environment: java version "1.6.0_22" Java(TM) SE Runtime Environment (build 1.6.0_22-b04) Java HotSpot(TM) 64-Bit Server VM (build 17.1-b03, mixed mode) JBoss 5.1.0 Windows 7, 8GB RAM Reporter: Andriy Rokhmanov Assignee: Steven Hawkins We have a problem with custom-generated materialized view. The way we do it works fine with Teiid 7.3 but fails when we try to migrate to 7.6. Here is the SQL which gives the problem: select * from chorus_metadata.property; Remote org.teiid.api.exception.query.QueryPlannerException: Group does not exist: chorus_metadata.property_CHORUS_NON_MAT_VIEW Some additional info: 1. System tables: select * from SYS.tables where Name like 'property%' and SchemaName = 'chorus_metadata'; VDBName SchemaName Name Type NameInSource IsPhysical SupportsUpdates UID Cardinality Description IsSystem IsMaterialized OID ------- --------------- ---------------------------- ---- ------------ ---------- --------------- ------------------------------------------- ----------- ----------- -------- -------------- --- Chorus chorus_metadata property_union View NULL true false mmuuid:319d6147-6145-4f56-bc2e-42326b19368c 0 NULL false false 393 Chorus chorus_metadata property_CHORUS_NON_MAT_VIEW View NULL true false mmuuid:bb25b63d-bded-4704-8638-e507197af6f1 0 NULL false false 398 Chorus chorus_metadata property View NULL false false mmuuid:9070f66d-df9c-4f37-bd4f-00020ceef492 0 NULL false true 399 select * from SYSADMIN.matviews; VDBName SchemaName Name TargetSchemaName TargetName Valid LoadState Updated Cardinality ------- --------------- -------------- ---------------- ------------------------------ ----- ------------- ------- ----------- Chorus chorus_metadata property NULL #MAT_CHORUS_METADATA.PROPERTY false NEEDS_LOADING NULL 0 Chorus pg_catalog pg_class NULL #MAT_PG_CATALOG.PG_CLASS false NEEDS_LOADING NULL NULL Chorus pg_catalog pg_attribute NULL #MAT_PG_CATALOG.PG_ATTRIBUTE false NEEDS_LOADING NULL NULL Chorus pg_catalog pg_index NULL #MAT_PG_CATALOG.PG_INDEX false NEEDS_LOADING NULL NULL Chorus pg_catalog pg_proc NULL #MAT_PG_CATALOG.PG_PROC false NEEDS_LOADING NULL NULL Chorus pg_catalog matpg_relatt NULL #MAT_PG_CATALOG.MATPG_RELATT false NEEDS_LOADING NULL NULL Chorus pg_catalog matpg_datatype NULL #MAT_PG_CATALOG.MATPG_DATATYPE false NEEDS_LOADING NULL NULL Note: looks like the chorus_metadata.propoerty needs loading, but attempt to load it fails with the same error: CALL SYSADMIN.refreshMatView(viewname=>'chorus_metadata.property', invalidate=>'true'); Remote org.teiid.api.exception.query.QueryResolverException: Group does not exist: chorus_metadata.property_CHORUS_NON_MAT_VIEW 2. The view chorus_metadata.property_CHORUS_NON_MAT_VIEW is actually exist and available: select * from chorus_metadata.property_CHORUS_NON_MAT_VIEW; propertyName objectName subType propertyValue objectInstance ----------------- ------------------------------- ----------- ----------------------- ----------------------- Sequence chorusdata.note Column 1 CREATED_ON Sequence demodata.someSeq Column 1 ... 3. How the chorus_metadata.property gets defined (sample code): org.teiid.metadata.Table table = org.teiid.metadata.MetadataFactory.addTable("property"); table.setMaterialized(true); table.setVirtual(true); table.setSelectTransformation( "/*+ cache */ SELECT propertyName, objectName, subType, propertyValue, objectInstance FROM chorus_metadata.property_CHORUS_NON_MAT_VIEW"); table.setTableType(Type.View); Note: we tried today a patch for TEIID-1868, it did not help. Let us know please if we can help with any additional information. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

7
16
0 / 0

[JBoss JIRA] (TEIID-1931) buffer setting maxStorageObjectSize is not factored into maxMemoryBlocks

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-1931: ------------------------------------- Summary: buffer setting maxStorageObjectSize is not factored into maxMemoryBlocks Key: TEIID-1931 URL: https://issues.jboss.org/browse/TEIID-1931 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.6 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.7 The max object size should restrict the number of permits needed by an initial write operation. Instead only the max blocks are being used, which cause contention on the semaphore. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
2
0 / 0

[JBoss JIRA] (TEIID-1809) Teiid maven build needs to work off of Jboss parent pom

by Ramesh Reddy (Created) (JIRA)

Teiid maven build needs to work off of Jboss parent pom ------------------------------------------------------- Key: TEIID-1809 URL: https://issues.jboss.org/browse/TEIID-1809 Project: Teiid Issue Type: Enhancement Components: Build/Kits Reporter: Ramesh Reddy Version 7 of the JBoss parent POM was released today. Please consider using this as the parent POM for your Maven builds, because it helps keep our builds consistent. Also, be aware that this POM is now in the Public Domain (i.e. no copyright), and the license setting will be inherited to your POMs unless overridden. So make sure your POM contains the correct <license> settings after updating. Some other notable changes in this version are that the release profile is now called "jboss-release". If you use the maven release plugin this profile will be called automatically, but if you release manually, then you should add "-Pjboss-release" to the build command, and the jboss-parent configuration will generate javadoc jars, and update the release info in the repository. The full list of changes in this version is available in jira [1], and more information about using the POM is available on the github site [2] [1]https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310081&ver... [2]https://github.com/jboss/jboss-parent-pom -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

4
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2012