February 2012 - teiid-issues - Jboss List Archives

[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, 1 month

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 month

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, 1 month

4
3
0 / 0

[JBoss JIRA] (TEIID-1862) add regression test for nested selects using UNION ALL and multiple aliases of the same column.

by Johnathon Lee (Created) (JIRA)

add regression test for nested selects using UNION ALL and multiple aliases of the same column. ----------------------------------------------------------------------------------------------- Key: TEIID-1862 URL: https://issues.jboss.org/browse/TEIID-1862 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.6.1 Environment: Teiid 7.6.x Reporter: Johnathon Lee Assignee: Johnathon Lee Pre 7.x code would throw a NPE with a query similar to [1]. Adding JUnit to prevent regression [1] SELECT enterprise_id FROM ( SELECT * FROM ( SELECT id, id AS display_id, 103 AS enterprise_id FROM ( SELECT 'x' as id) AS nexted103) as table103Source UNION ALL SELECT 'x', 'x' AS display_id, 101 AS enterprise_id FROM ( SELECT 'x') AS nested101 UNION ALL SELECT 'x', 'x' AS display_id, 100 AS enterprise_id FROM ( SELECT 'x') AS nested100) as tableFrom1stSelect WHERE enterprise_id = 100 -- 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 month

5
4
0 / 0

[JBoss JIRA] (TEIID-1904) Prepared statement for SOURCE_NAME in multi-source mode throws exception Message:Unable to evaluate

by Ganesh Kumar (JIRA)

Ganesh Kumar created TEIID-1904: ----------------------------------- Summary: Prepared statement for SOURCE_NAME in multi-source mode throws exception Message:Unable to evaluate Key: TEIID-1904 URL: https://issues.jboss.org/browse/TEIID-1904 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.6, 7.3 Environment: Windows 7 JDK 1.6.0_23 Jboss 5.1.0.GA Reporter: Ganesh Kumar Assignee: Steven Hawkins I have a VDB which has a multi-source model. I have a prepared statement for which SOURCE_NAME is passed as a parameter. When this prepared statement is executed, I get an exception [TeiidComponentException] ERR.015.006.0033: Error Code:ERR.015.006.0033 Message:Unable to evaluate ?: No value was available This exception does not occur when I specify other conditions in combination with SOURCE_NAME. Also, the query works fine when SOURCE_NAME value is not a parameter, that is, its value is provided in the query. -- 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 month

2
7
0 / 0

[JBoss JIRA] (TEIID-1870) Querying random number from DB2 v97 does not push down to source

by Paul Nittel (Created) (JIRA)

Querying random number from DB2 v97 does not push down to source ---------------------------------------------------------------- Key: TEIID-1870 URL: https://issues.jboss.org/browse/TEIID-1870 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.6 Reporter: Paul Nittel Assignee: Steven Hawkins When I query SELECT RAND(), IntKey from SmallA using DB2 directly, I get back: 1,INTKEY 0.00125,0 0.56359,1 0.1933,2 0.80874,3 Using the equivalent SQL through Teiid to DB2, I get: expr,IntKey 0.86867,0 0.86867,1 0.86867,2 0.86867,3 The command log entry for the Teiid query looks like this: 2011-12-14 07:50:22,093 DEBUG [org.teiid.COMMAND_LOG] (New I/O server worker #1-2 START USER COMMAND: startTime=2011-12-14 07:50:22.093 requestID=KURKVzpMf/MI.12 txID=null sessionID=KURKVzpMf/MI applicationName=JDBC principal=user@teiid-security vdbName=QT_db2v97ds_Push vdbVersion=1 sql=select rand(), curtime(), intkey from bqt1.smalla limit 5 2011-12-14 07:50:22,099 DEBUG [org.teiid.COMMAND_LOG] (Worker6_QueryProcessorQueue1394 START DATA SRC COMMAND: startTime=2011-12-14 07:50:22.098 requestID=KURKVzpMf/MI.12 sourceCommandID=0 txID=null modelName=Source connectorBindingName=db2 sessionID=KURKVzpMf/MI principal=user@teiid-security sql=SELECT convert(g_0.INTKEY, integer) AS c_2 FROM Source.SMALLA AS g_0 LIMIT 5 2011-12-14 07:50:22,394 DEBUG [org.teiid.COMMAND_LOG] (Worker6_QueryProcessorQueue1396 END SRC COMMAND: endTime=2011-12-14 07:50:22.394 requestID=KURKVzpMf/MI.12 sourceCommandID=0 txID=null modelName=Source connectorBindingName=db2 sessionID=KURKVzpMf/MI principal=user@teiid-security finalRowCount=5 2011-12-14 07:50:22,427 DEBUG [org.teiid.COMMAND_LOG] (Worker5_QueryProcessorQueue1397 END USER COMMAND: endTime=2011-12-14 07:50:22.427 requestID=KURKVzpMf/MI.12 txID=null sessionID=KURKVzpMf/MI principal=user@teiid-security vdbName=QT_db2v97ds_Push vdbVersion=1 finalRowCount=0 The source command appears to be lacking the rand() function call. In response, dev says, "So the issue here is that the final rewrite of the pushdown query is pre-evaluating the non-deterministic pushdown function. If the function were not pushed-down you would get something more like you would expect." -- 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 month

5
5
0 / 0

[JBoss JIRA] Created: (TEIID-1687) GSSAPI support for postgres emulation layer

by Graeme Gillies (JIRA)

GSSAPI support for postgres emulation layer ------------------------------------------- Key: TEIID-1687 URL: https://issues.jboss.org/browse/TEIID-1687 Project: Teiid Issue Type: Feature Request Affects Versions: 7.4 Environment: All Reporter: Graeme Gillies Assignee: Steven Hawkins Priority: Minor Similar to TEIID-1610 Postgres clients support authentication via GSSAPI http://www.google.com/url?sa=t&source=web&cd=2&ved=0CB4QFjAB&url=http%3A%... It would be great if teiid's postgres emulation layer would allow it to support GSSAPI as an authentication mechanism from clients. Server side you could setup a keytab with the correct server side principal postgres/$fqdn(a)REALM.COM which teiid would use to authenticate clients connecting to it via the postgres emulation layer. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

5
4
0 / 0

[JBoss JIRA] (TEIID-1894) Consolidate bulk/iterator based inserts

by Steven Hawkins (Created) (JIRA)

Consolidate bulk/iterator based inserts --------------------------------------- Key: TEIID-1894 URL: https://issues.jboss.org/browse/TEIID-1894 Project: Teiid Issue Type: Quality Risk Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.0 There is redundancy and inconsistency in the translator api around performing bulk/iterator based updates. These should be consolidated to a single execution model. -- 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 month

4
3
0 / 0

[JBoss JIRA] (TEIID-1932) Add comparable lob logic to 7.7

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-1932: ------------------------------------- Summary: Add comparable lob logic to 7.7 Key: TEIID-1932 URL: https://issues.jboss.org/browse/TEIID-1932 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.7 Back-port the comparable lob logic from TEIID-1834 from 8.0 to 7.7 -- 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 month

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1540) Add the ability to delegate one shot dependent joins to the translators

by Steven Hawkins (JIRA)

Add the ability to delegate one shot dependent joins to the translators ----------------------------------------------------------------------- Key: TEIID-1540 URL: https://issues.jboss.org/browse/TEIID-1540 Project: Teiid Issue Type: Sub-task Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.4 Using a memory safe iterator, like with bulk handling, we should be able to push dependent joins to the translator to perform specialized source specific one-shot join handling. With the other dependent join improvements this should hopefully be needed only in the most extreme cases. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2012