August 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3074) NPE When using External Materialization management is use

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-3074: ----------------------------------- Summary: NPE When using External Materialization management is use Key: TEIID-3074 URL: https://issues.jboss.org/browse/TEIID-3074 Project: Teiid Issue Type: Bug Security Level: Public (Everyone can see) Components: Query Engine Affects Versions: 8.5 Reporter: Ramesh Reddy Assignee: Steven Hawkins When I was issuing query that has externalized materialization with management option to true, I am seeing NPE. Tried to see why NPE is occurring was not able to figure out (yet) {code} 14:37:50,269 ERROR [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue8477) 0z97J5OWq7x9 Connector worker process failed for atomic-request=0z97J5OWq7x9.7.1.4220: java.lang.NullPointerException at org.teiid.translator.jdbc.JDBCQueryExecution.next(JDBCQueryExecution.java:338) at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:385) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT] at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:203) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT] at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:301) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT] at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT] at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT] at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_65] at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT] at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT] at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT] at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_65] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_65] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65] {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3044) Add function metadata to system tables / databasemetadata

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3044?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3044: --------------------------------------- A wrinkle here is that system functions and pushdown functions (quasi system functions, since they are under the sys schema) aren't actually children of the schema, but rather managed through a function library. The system functions could possibly be added to the system metadata, but the pushdown functions are dependent upon which translators are in use and thus scoped to the vdb. > Add function metadata to system tables / databasemetadata > --------------------------------------------------------- > > Key: TEIID-3044 > URL: https://issues.jboss.org/browse/TEIID-3044 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JDBC Driver, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.9 > > > We should expose source/system/udf functions via system metadata. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3073) Tableau Connection Issues

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-3073: ----------------------------------- Summary: Tableau Connection Issues Key: TEIID-3073 URL: https://issues.jboss.org/browse/TEIID-3073 Project: Teiid Issue Type: Bug Security Level: Public (Everyone can see) Components: ODBC, Server Reporter: Ramesh Reddy Assignee: Steven Hawkins It has been reported that using Tableu with Teiid ODBC port show the following errors. These need to be investigated and fixed {code} This ODBC driver does not support important capabilities used by Tableau. This unsupported function is required for relative date filters: The date part named 'week' for the date function: DATETRUNC(date_part, date, [start_of_week]) ----- Tableau identified the following warnings for the ODBC data source named 'streamyx_sales (streamyx_sales.streamyx_sales) (TMJDV)': This aggregation is unsupported: Attribute This aggregation is unsupported: Std. Dev This aggregation is unsupported: Std. Dev (Pop.) This aggregation is unsupported: Trunc Week Number This aggregation is unsupported: Variance This aggregation is unsupported: Variance (Pop.) This function is unsupported: % with parameter types 'integer, integer' This function is unsupported: ABS(number) with parameter types 'float' This function is unsupported: ABS(number) with parameter types 'integer' This function is unsupported: ACOS(number) with parameter types 'float' This function is unsupported: ASCII(string) with parameter types 'string' This function is unsupported: ASIN(number) with parameter types 'float' This function is unsupported: ATAN(number) with parameter types 'float' This function is unsupported: ATAN2(y number, x number) with parameter types 'float, float' This function is unsupported: CHAR(integer) with parameter types 'float' This function is unsupported: CHAR(integer) with parameter types 'integer' This function is unsupported: COS(angle) with parameter types 'float' This function is unsupported: COT(angle) with parameter types 'float' This function is unsupported: DATEPART_DAYOFWEEK_INTERNAL with parameter types 'date' This function is unsupported: DATEPART_WEEK_INTERNAL with parameter types 'date' This function is unsupported: DATETIME with parameter types 'integer' This function is unsupported: DEGREES(number) with parameter types 'float' This function is unsupported: EXP(number) with parameter types 'float' This function is unsupported: LN with parameter types 'float' This function is unsupported: LN(number) with parameter types 'float' This function is unsupported: LOG with parameter types 'float' This function is unsupported: LOG(number, [base]) with parameter types 'float' This function is unsupported: PI() This function is unsupported: POWER with parameter types 'float, integer' This function is unsupported: POWER with parameter types 'integer, integer' This function is unsupported: POWER(number,power) with parameter types 'float, integer' This function is unsupported: POWER(number,power) with parameter types 'integer, integer' This function is unsupported: RADIANS(number) with parameter types 'float' This function is unsupported: ROUND(number, [decimals]) with parameter types 'float' This function is unsupported: ROUND(number, [decimals]) with parameter types 'float, integer' This function is unsupported: SIGN(number) with parameter types 'float' This function is unsupported: SIN(angle) with parameter types 'float' This function is unsupported: SPACE with parameter types 'float' This function is unsupported: SPACE(number) with parameter types 'integer' This function is unsupported: SQRT(number) with parameter types 'float' This function is unsupported: SQUARE with parameter types 'float' This function is unsupported: TAN(angle) with parameter types 'float' This function is unsupported: The date part named 'week' for the date function: DATEDIFF(date_part, start_date, end_date, [start_of_week]) This function is unsupported: The date part named 'week' for the date function: DATEDIFF(date_part, start_date, end_date, [start_of_week]) This function is unsupported: The date part named 'week' for the date function: DATENAME(date_part, date, [start_of_week]) This function is unsupported: The date part named 'week' for the date function: DATENAME(date_part, date, [start_of_week]) This function is unsupported: The date part named 'week' for the date function: DATEPART(date_part, date, [start_of_week]) This function is unsupported: The date part named 'week' for the date function: DATEPART(date_part, date, [start_of_week]) This function is unsupported: The date part named 'weekday' for the date function: DATENAME(date_part, date, [start_of_week]) This function is unsupported: The date part named 'weekday' for the date function: DATENAME(date_part, date, [start_of_week]) This function is unsupported: The date part named 'weekday' for the date function: DATEPART(date_part, date, [start_of_week]) This function is unsupported: The date part named 'weekday' for the date function: DATEPART(date_part, date, [start_of_week]) This is unsupported: SELECT ... INTO This is unsupported: Temporary tables {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3041) Add support for xml document models in ddl

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3041?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3041: --------------------------------------- That's a much larger undertaking and of course requires a significant amount of rework in Designer. So well beyond the scope of this issue. We may ultimately resolve this issue as mentioned above as xml document model usage means index metadata. > Add support for xml document models in ddl > ------------------------------------------ > > Key: TEIID-3041 > URL: https://issues.jboss.org/browse/TEIID-3041 > Project: Teiid > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.9 > > > xml document model support was left out of the initial ddl design, but since the feature has not yet been retargeted from designer we should add support. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3041) Add support for xml document models in ddl

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3041?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3041: ------------------------------------- Steve apart from supporting the old XML document model into new DDL enclosure, do you think we need to re-define a way how XML documents can be built using SQLXML or this is just purely a UI exercise to use SQLXML. > Add support for xml document models in ddl > ------------------------------------------ > > Key: TEIID-3041 > URL: https://issues.jboss.org/browse/TEIID-3041 > Project: Teiid > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.9 > > > xml document model support was left out of the initial ddl design, but since the feature has not yet been retargeted from designer we should add support. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3041) Add support for xml document models in ddl

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3041?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3041: --------------------------------------- Until we implement something here the assumption will be that continued document model support will be through the old index metadata as it can easily be mixed into a vdb that also is using ddl. > Add support for xml document models in ddl > ------------------------------------------ > > Key: TEIID-3041 > URL: https://issues.jboss.org/browse/TEIID-3041 > Project: Teiid > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.9 > > > xml document model support was left out of the initial ddl design, but since the feature has not yet been retargeted from designer we should add support. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3044) Add function metadata to system tables / databasemetadata

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3044?page=com.atlassian.jira.plugin... ] Work on TEIID-3044 started by Steven Hawkins. > Add function metadata to system tables / databasemetadata > --------------------------------------------------------- > > Key: TEIID-3044 > URL: https://issues.jboss.org/browse/TEIID-3044 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JDBC Driver, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.9 > > > We should expose source/system/udf functions via system metadata. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3044) Add function metadata to system tables / databasemetadata

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3044?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3044: ---------------------------------- Fix Version/s: 8.9 > Add function metadata to system tables / databasemetadata > --------------------------------------------------------- > > Key: TEIID-3044 > URL: https://issues.jboss.org/browse/TEIID-3044 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JDBC Driver, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.9 > > > We should expose source/system/udf functions via system metadata. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3050) allow for more incremental insert with iterator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3050?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3050. ----------------------------------- Resolution: Done Changed the logic to be aware of whether there is an existing transaction or no txn needed to not perform full buffering. Also in the non-txn scenarios for batch/iterator we'll not perform read/write with some concurrency. > allow for more incremental insert with iterator > ----------------------------------------------- > > Key: TEIID-3050 > URL: https://issues.jboss.org/browse/TEIID-3050 > Project: Teiid > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Misc. Connectors, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.9 > > > The current bulk insert logic assumes that it is avoiding a global transactions by fully reading the results before sending the tuplebuffer iterator to the source for processing, which can then just use a local transaction. However if we are already operating under a transaction or the user doesn't want a transaction (such as with a staging materialized view load) then the insert should happen more incrementally. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3069) Quick Start Can't run against JDV

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3069?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3069: ------------------------------------ As for the "event not found" issue, that's not the quick start that doesn't like it. Its the OS scripting. If you escape the ! like \! it gets pass your issue. > Quick Start Can't run against JDV > --------------------------------- > > Key: TEIID-3069 > URL: https://issues.jboss.org/browse/TEIID-3069 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Quick Starts > Environment: JBoss Data Virtualization 6.0 > JBoss Data Virtualization 6.1 > Reporter: Kylin Soong > Assignee: Van Halbert > > Some Quick Start can't run well against Enterprise JDV, can we have a JDV version quick start? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2014