August 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3064) Sybase metadata loading fails

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3064?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3064: ------------------------------------ I vote to leave teiid as is, and work to improve the usability in tooling (i.e., Designer). > Sybase metadata loading fails > ----------------------------- > > Key: TEIID-3064 > URL: https://issues.jboss.org/browse/TEIID-3064 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.7 > Reporter: Filip Elias > Assignee: Steven Hawkins > Attachments: server.log > > > Sybase metadata loading fails[1] when deploying dynamic vdb. > The problem is in JDBCMetdataProcessor.getForeignKeys. Method loads FKs from all tables, but it fails when it tries to load FKs from table sysquerymetrics. The problem seems to be that sysquerymetrics is not a system table, it is a view. > [1] Reason:TEIID11010 com.sybase.jdbc4.jdbc.SybSQLException: No such object or user exists in the database. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3064) Sybase metadata loading fails

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3064?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3064: --------------------------------------- Is everyone good with resoling by adding a doc note about needing to set a schema or exclude certain system tables? > Sybase metadata loading fails > ----------------------------- > > Key: TEIID-3064 > URL: https://issues.jboss.org/browse/TEIID-3064 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.7 > Reporter: Filip Elias > Assignee: Steven Hawkins > Attachments: server.log > > > Sybase metadata loading fails[1] when deploying dynamic vdb. > The problem is in JDBCMetdataProcessor.getForeignKeys. Method loads FKs from all tables, but it fails when it tries to load FKs from table sysquerymetrics. The problem seems to be that sysquerymetrics is not a system table, it is a view. > [1] Reason:TEIID11010 com.sybase.jdbc4.jdbc.SybSQLException: No such object or user exists in the database. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3067) External Materialization Management Issues

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-3067: ----------------------------------- Summary: External Materialization Management Issues Key: TEIID-3067 URL: https://issues.jboss.org/browse/TEIID-3067 Project: Teiid Issue Type: Bug Security Level: Public (Everyone can see) Components: Server Affects Versions: 8.5 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.7.1, 8.9 Couple issues 1) Based on https://docs.jboss.org/author/display/TEIID/External+Materialization document, the property teiid_rel:MATVIEW_STAGE_TABLE needs to be optional, however it is been coded as required. 2) If an exception occurs during the loadMatview, the status table is set to "FailedLoad" however the exception is not logged to know the source of the issue. This needs to logged. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3057) Kerberos ODBC connection on Teiid 8.8.0

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3057?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3057. --------------------------------- Labels: Alpha1 (was: ) Fix Version/s: 8.7.1 8.9 Resolution: Done Added null check to avoid the NPE. When delegation is in effect it will have the non-null object. IMO, the confusion raised from LogonResult properties generic map and Hastable usage in the ODBC where it does not allow null inserts. > Kerberos ODBC connection on Teiid 8.8.0 > --------------------------------------- > > Key: TEIID-3057 > URL: https://issues.jboss.org/browse/TEIID-3057 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ODBC > Affects Versions: 8.8 > Environment: Teiid 8.8.0 > EAP 6.1.1 > Reporter: Cristiano Nicolai > Assignee: Ramesh Reddy > Priority: Blocker > Labels: Alpha1 > Fix For: 8.7.1, 8.9 > > > After upgrading from version 8.7.0.Final to version 8.8.0.Final connections via ODBC using Kerberos/GSS stopped working. > When I try to connect with the new version, on the server I get the following error: > > 12:24:31,755 ERROR [org.teiid.ODBC] (New I/O worker #2) TEIID40015 Unexpected error occurred: java.lang.NullPointerException > at java.util.Hashtable.put(Hashtable.java:514) [rt.jar:1.7.0_55] > at org.teiid.odbc.ODBCServerRemoteImpl.logon(ODBCServerRemoteImpl.java:244) [teiid-runtime-8.8.0.Final.jar:8.8.0.Final] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_55] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_55] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_55] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_55] > at org.teiid.transport.ODBCClientInstance.processMessage(ODBCClientInstance.java:127) [teiid-runtime-8.8.0.Final.jar:8.8.0.Final] > at org.teiid.transport.ODBCClientInstance.receivedMessage(ODBCClientInstance.java:116) [teiid-runtime-8.8.0.Final.jar:8.8.0.Final] > at org.teiid.transport.SSLAwareChannelHandler.messageReceived(SSLAwareChannelHandler.java:211) [teiid-runtime-8.8.0.Final.jar:8.8.0.Final] > > From the client I get the following message: psql: duplicate GSS authentication request -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3057) Kerberos ODBC connection on Teiid 8.8.0

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3057?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-3057: -------------------------------- Component/s: ODBC > Kerberos ODBC connection on Teiid 8.8.0 > --------------------------------------- > > Key: TEIID-3057 > URL: https://issues.jboss.org/browse/TEIID-3057 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ODBC > Affects Versions: 8.8 > Environment: Teiid 8.8.0 > EAP 6.1.1 > Reporter: Cristiano Nicolai > Assignee: Ramesh Reddy > Priority: Blocker > > After upgrading from version 8.7.0.Final to version 8.8.0.Final connections via ODBC using Kerberos/GSS stopped working. > When I try to connect with the new version, on the server I get the following error: > > 12:24:31,755 ERROR [org.teiid.ODBC] (New I/O worker #2) TEIID40015 Unexpected error occurred: java.lang.NullPointerException > at java.util.Hashtable.put(Hashtable.java:514) [rt.jar:1.7.0_55] > at org.teiid.odbc.ODBCServerRemoteImpl.logon(ODBCServerRemoteImpl.java:244) [teiid-runtime-8.8.0.Final.jar:8.8.0.Final] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_55] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_55] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_55] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_55] > at org.teiid.transport.ODBCClientInstance.processMessage(ODBCClientInstance.java:127) [teiid-runtime-8.8.0.Final.jar:8.8.0.Final] > at org.teiid.transport.ODBCClientInstance.receivedMessage(ODBCClientInstance.java:116) [teiid-runtime-8.8.0.Final.jar:8.8.0.Final] > at org.teiid.transport.SSLAwareChannelHandler.messageReceived(SSLAwareChannelHandler.java:211) [teiid-runtime-8.8.0.Final.jar:8.8.0.Final] > > From the client I get the following message: psql: duplicate GSS authentication request -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3065) SOLR: NPE When issued query with SORT

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3065?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3065. --------------------------------- Labels: Alpaha1 (was: ) Resolution: Done Captured the alias name to expression references to correctly reflect in the SOLR query > SOLR: NPE When issued query with SORT > ------------------------------------- > > Key: TEIID-3065 > URL: https://issues.jboss.org/browse/TEIID-3065 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.6 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Alpaha1 > Fix For: 8.7.1, 8.9 > > > A query like > select id as c_0 from index order by c_0 > ends in exception > {code} > 14:39:41,152 ERROR [org.teiid.CONNECTOR] (Worker5_QueryProcessorQueue306) Connector worker process failed for atomic-request=1IQ9x3qmpUQr.13.4.9: java.lang.NullPointerException > at org.teiid.translator.solr.SolrSQLHierarchyVistor.visit(SolrSQLHierarchyVistor.java:70) > at org.teiid.language.ColumnReference.acceptVisitor(ColumnReference.java:72) [teiid-api-8.7.1.redhat-1.jar:8.7.1.redhat-1] > at org.teiid.language.visitor.AbstractLanguageVisitor.visitNode(AbstractLanguageVisitor.java:51) [teiid-api-8.7.1.redhat-1.jar:8.7.1.redhat-1] > at org.teiid.translator.solr.SolrSQLHierarchyVistor.visit(SolrSQLHierarchyVistor.java:248) > at org.teiid.language.SortSpecification.acceptVisitor(SortSpecification.java:53) [teiid-api-8.7.1.redhat-1.jar:8.7.1.redhat-1] > at org.teiid.language.visitor.AbstractLanguageVisitor.visitNode(AbstractLanguageVisitor.java:51) [teiid-api-8.7.1.redhat-1.jar:8.7.1.redhat-1] > at org.teiid.language.visitor.AbstractLanguageVisitor.visitNodes(AbstractLanguageVisitor.java:63) [teiid-api-8.7.1.redhat-1.jar:8.7.1.redhat-1] > at org.teiid.translator.solr.SolrSQLHierarchyVistor.visit(SolrSQLHierarchyVistor.java:243) > at org.teiid.language.OrderBy.acceptVisitor(OrderBy.java:45) [teiid-api-8.7.1.redhat-1.jar:8.7.1.redhat-1] > at org.teiid.language.visitor.AbstractLanguageVisitor.visitNode(AbstractLanguageVisitor.java:51) [teiid-api-8.7.1.redhat-1.jar:8.7.1.redhat-1] > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3066) SOLR: Provide count(*) capability natively by translator

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3066?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3066. --------------------------------- Labels: Alpha1 (was: ) Resolution: Done Implemented as described in the article mentioned > SOLR: Provide count(*) capability natively by translator > -------------------------------------------------------- > > Key: TEIID-3066 > URL: https://issues.jboss.org/browse/TEIID-3066 > Project: Teiid > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.7 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Alpha1 > Fix For: 8.7.1, 8.9 > > > count(*) capability currently supported by counting each row in the engine, this needs to be natively supported. The suggested implementation path can use information from below link > http://stackoverflow.com/questions/5050746/solr-solrj-how-can-i-determine... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3066) SOLR: Provide count(*) capability natively by translator

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-3066: ----------------------------------- Summary: SOLR: Provide count(*) capability natively by translator Key: TEIID-3066 URL: https://issues.jboss.org/browse/TEIID-3066 Project: Teiid Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Misc. Connectors Affects Versions: 8.7 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.7.1, 8.9 count(*) capability currently supported by counting each row in the engine, this needs to be natively supported. The suggested implementation path can use information from below link http://stackoverflow.com/questions/5050746/solr-solrj-how-can-i-determine... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3065) SOLR: NPE When issued query with SORT

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-3065: ----------------------------------- Summary: SOLR: NPE When issued query with SORT Key: TEIID-3065 URL: https://issues.jboss.org/browse/TEIID-3065 Project: Teiid Issue Type: Bug Security Level: Public (Everyone can see) Components: Misc. Connectors Affects Versions: 8.6 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.7.1, 8.9 A query like select id as c_0 from index order by c_0 ends in exception {code} 14:39:41,152 ERROR [org.teiid.CONNECTOR] (Worker5_QueryProcessorQueue306) Connector worker process failed for atomic-request=1IQ9x3qmpUQr.13.4.9: java.lang.NullPointerException at org.teiid.translator.solr.SolrSQLHierarchyVistor.visit(SolrSQLHierarchyVistor.java:70) at org.teiid.language.ColumnReference.acceptVisitor(ColumnReference.java:72) [teiid-api-8.7.1.redhat-1.jar:8.7.1.redhat-1] at org.teiid.language.visitor.AbstractLanguageVisitor.visitNode(AbstractLanguageVisitor.java:51) [teiid-api-8.7.1.redhat-1.jar:8.7.1.redhat-1] at org.teiid.translator.solr.SolrSQLHierarchyVistor.visit(SolrSQLHierarchyVistor.java:248) at org.teiid.language.SortSpecification.acceptVisitor(SortSpecification.java:53) [teiid-api-8.7.1.redhat-1.jar:8.7.1.redhat-1] at org.teiid.language.visitor.AbstractLanguageVisitor.visitNode(AbstractLanguageVisitor.java:51) [teiid-api-8.7.1.redhat-1.jar:8.7.1.redhat-1] at org.teiid.language.visitor.AbstractLanguageVisitor.visitNodes(AbstractLanguageVisitor.java:63) [teiid-api-8.7.1.redhat-1.jar:8.7.1.redhat-1] at org.teiid.translator.solr.SolrSQLHierarchyVistor.visit(SolrSQLHierarchyVistor.java:243) at org.teiid.language.OrderBy.acceptVisitor(OrderBy.java:45) [teiid-api-8.7.1.redhat-1.jar:8.7.1.redhat-1] at org.teiid.language.visitor.AbstractLanguageVisitor.visitNode(AbstractLanguageVisitor.java:51) [teiid-api-8.7.1.redhat-1.jar:8.7.1.redhat-1] {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3062) Apply LIMIT 1 optimization for DISTINCT in UNION situations

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3062?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3062. ----------------------------------- Fix Version/s: 8.9 Resolution: Done I thought this would be aligned with the fix for TEIID-3063, but it turned out to be easier to just relax the logic related to the partitioned union optimization, such that we'll still decompose even when there are constants. > Apply LIMIT 1 optimization for DISTINCT in UNION situations > ----------------------------------------------------------- > > Key: TEIID-3062 > URL: https://issues.jboss.org/browse/TEIID-3062 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Query Engine > Affects Versions: 8.1 > Reporter: Mark Addleman > Assignee: Steven Hawkins > Fix For: 8.9 > > > The translator does not support select expressions. Query: > SELECT DISTINCT DATAMART_NAME AS c_9, '_constant_' AS c_10 FROM (SELECT datamart_name FROM > ( > SELECT 'DATACOM Datamart' AS DATAMART_NAME FROM SECURITY_DM_DATACOM_DEV_R140_CA31_CMGRD1.VIEWOBJACCESS > UNION ALL > SELECT 'DB2 D91A Datamart' AS DATAMART_NAME FROM SECURITY_DM_DB2_D91APTIB_CMGRD1.VIEWOBJACCESS > ) AS t > ) a > Final part of plan: > OPTIMIZATION COMPLETE: > PROCESSOR PLAN: > SortNode(0) output=[datamart_name AS c_9, '_constant_' AS c_10] [DUP_REMOVE] > ProjectNode(1) output=[datamart_name AS c_9, '_constant_' AS c_10] [datamart_name AS c_9, '_constant_' AS c_10] > UnionAllNode(2) output=[datamart_name] > AccessNode(3) output=['DATACOM Datamart' AS DATAMART_NAME] SELECT 'DATACOM Datamart' FROM SECURITY_DM_DATACOM_DEV_R140_CA31_CMGRD1.VIEWOBJACCESS AS g_0 > AccessNode(4) output=['DB2 D91A Datamart' AS DATAMART_NAME] SELECT 'DB2 D91A Datamart' FROM SECURITY_DM_DB2_D91APTIB_CMGRD1.VIEWOBJACCESS AS g_0 > Expected LIMIT 1 in the access nodes. Comment from Steven: "More than likely we are not checking across a union for this optimization." > See https://community.jboss.org/message/883460 for more details and complete plan -- 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