December 2011 - teiid-issues - Jboss List Archives

[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, 7 months

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, 7 months

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, 7 months

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 months

7
16
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, 7 months

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, 7 months

5
4
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, 7 months

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, 7 months

5
4
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, 7 months

3
4
0 / 0

[JBoss JIRA] (TEIID-1864) TIMESTAMPADD of SQL_TSI_FRAC_SECOND fails for Sybase 15 with JConnect 6.0.5 driver

by Paul Nittel (Created) (JIRA)

TIMESTAMPADD of SQL_TSI_FRAC_SECOND fails for Sybase 15 with JConnect 6.0.5 driver ---------------------------------------------------------------------------------- Key: TEIID-1864 URL: https://issues.jboss.org/browse/TEIID-1864 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.6 Reporter: Paul Nittel Assignee: Steven Hawkins Executing this query: SELECT intkey, timestampvalue, TIMESTAMPADD(SQL_TSI_FRAC_SECOND,123,TIMESTAMPVALUE) FROM BQT1.SMALLA WHERE INTKEY < 10 ORDER BY INTKEY errors in the following fashion: [JDBCExecutionException] 0: Error Code:0 Message:'JZ0SI: A static function escape timestampaddsql_tsi_frac_second was used which is not supported by this server.' error executing statement(s): [Prepared Values: [] SQL: SELECT g_0.IntKey AS c_0, g_0.TimestampValue AS c_1, {fn timestampadd(SQL_TSI_FRAC_SECOND, 123, g_0.TimestampValue)} AS c_2 FROM SmallA g_0 WHERE g_0.IntKey < 10 ORDER BY c_0] 1 [SQLException]JZ0SI: A static function escape timestampaddsql_tsi_frac_second was used which is not supported by this server. at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:90) at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:272) at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:342) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:138) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:135) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:118) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:232) at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:118) at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:288) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: java.sql.SQLException: JZ0SI: A static function escape timestampaddsql_tsi_frac_second was used which is not supported by this server. at com.sybase.jdbc3.jdbc.ErrorMessage.raiseError(Unknown Source) at com.sybase.jdbc3.jdbc.SybStatement.processEscapes(Unknown Source) at com.sybase.jdbc3.jdbc.SybStatement.doEscapeProcessing(Unknown Source) at com.sybase.jdbc3.jdbc.SybPreparedStatement.<init>(Unknown Source) at com.sybase.jdbc3.jdbc.SybConnection.a(Unknown Source) at com.sybase.jdbc3.jdbc.SybConnection.prepareStatement(Unknown Source) at com.sybase.jdbc3.jdbc.SybConnection.prepareStatement(Unknown Source) at com.sybase.jdbc3.jdbc.SybConnection.prepareStatement(Unknown Source) at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.doPrepareStatement(BaseWrapperManagedConnection.java:465) at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.prepareStatement(BaseWrapperManagedConnection.java:460) at org.jboss.resource.adapter.jdbc.WrappedConnection.prepareStatement(WrappedConnection.java:243) at org.teiid.translator.jdbc.JDBCBaseExecution.getPreparedStatement(JDBCBaseExecution.java:172) at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:84) ... 13 more Executing the same query using the JTDS 1.2.5 driver works correctly. -- 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 months

5
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2011