[JBoss JIRA] (TEIID-3171) NullPointerException in LogonImpl when Credential Delegate is not enabled
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3171?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3171.
---------------------------------
> NullPointerException in LogonImpl when Credential Delegate is not enabled
> -------------------------------------------------------------------------
>
> Key: TEIID-3171
> URL: https://issues.jboss.org/browse/TEIID-3171
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.8
> Reporter: Cristiano Nicolai
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 8.7.1, 8.9
>
>
> When trying to connect via JDBC using GSS authentication, the follwing exception is thrown if Credential Delegation is not enabled. Via ODBC, same setup works fine.
> 2014-10-14 11:22:35,199 INFO [org.teiid.SECURITY] (New I/O worker #4:) TEIID40017 Unexpected exception for session null: java.lang.NullPointerException
> at java.util.Hashtable.put(Hashtable.java:514)
> at org.teiid.transport.LogonImpl.neogitiateGssLogin(LogonImpl.java:197)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.teiid.transport.ServerWorkItem.run(ServerWorkItem.java:87)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274)
> at org.teiid.transport.SocketClientInstance.processMessagePacket(SocketClientInstance.java:207)
> at org.teiid.transport.SocketClientInstance.receivedMessage(SocketClientInstance.java:193)
> at org.teiid.transport.SSLAwareChannelHandler.messageReceived(SSLAwareChannelHandler.java:211)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 11 months
[JBoss JIRA] (TEIID-3086) Exception with unclear message
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3086?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3086.
---------------------------------
> Exception with unclear message
> ------------------------------
>
> Key: TEIID-3086
> URL: https://issues.jboss.org/browse/TEIID-3086
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.7
> Environment: OS: Fedora 20
> architecture: x86_64
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
> Attachments: exception-stack-trace, full-server.log, server.log
>
>
> Description of problem:
> Unexpected exception. Returned exception indicates that query failed but there is no reason in message.
> Actual results:
> TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 Source: 4200 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT cast(g_0.bytenum AS tinyint) AS c_0, abs(cast(g_0.bytenum AS tinyint)) AS c_1 FROM smallb AS g_0 ORDER BY c_0]
> Expected results:
> Remote java.sql.SQLException: Specified cursor is not known to the server.
> Additional info:
> server log and exception stack trace in attachment
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 11 months
[JBoss JIRA] (TEIID-3148) Teiid exception with vdb from flat file containing utf8 non-ascii character
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3148?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3148.
---------------------------------
> Teiid exception with vdb from flat file containing utf8 non-ascii character
> ---------------------------------------------------------------------------
>
> Key: TEIID-3148
> URL: https://issues.jboss.org/browse/TEIID-3148
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1
> Environment: Windows OS
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
>
> This issue is Windows OS specific. When trying to parse text csv file in utf8 which contains non-ascii characters an exception occurs. When the non-ascii characters are removed, everything passes well. On RHEL or Solaris this issue doesn't occur.
> TEIID30020 Processing exception for request rgzZ3dn9tVMX.0 'TEIID30179 Text parse error: Could not read data in file:/w:/workspace/JDV6_1_BQT-jstastny/jdk/java17_default/label/Win2k8_x86/eap/standalone/deployments/TextEmployeeTest-files/EmpData.txt'. Originally TeiidProcessingException 'Input length = 1' CoderResult.java:278.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 11 months
[JBoss JIRA] (TEIID-2892) OData buffers ALL rows from resultset before returning the first batch
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2892?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2892.
---------------------------------
> OData buffers ALL rows from resultset before returning the first batch
> ----------------------------------------------------------------------
>
> Key: TEIID-2892
> URL: https://issues.jboss.org/browse/TEIID-2892
> Project: Teiid
> Issue Type: Quality Risk
> Components: OData
> Affects Versions: 8.4.1
> Environment: Tested with Jboss DV 6.0.0. GA (enterprise edition) on Apple OSX 10.9.2 and Oracle Java VM 1.7.0_51.
> Reporter: Patrick Deenen
> Assignee: Steven Hawkins
> Attachments: logfiles.zip
>
>
> OData doesn’t batch internally opposed to JDBC which does. E.g. when in JDBC a query is done with a large result, only the first 2048 rows are physically fetched from the source database and only the first 200 rows (depending on client application) are returned. But when the same query is executed by the use of Odata ALL rows in the result set are physically fetched by DV and stored in the buffer. Even with the default Odata fetch batch size of 256. This makes the Odata interface very inefficient for large query results where one only is interessed in the first 256 rows.
> Attached you can find two log files which show the problem.
> The Odata query used is:
> http://localhost:8080/odata/PMA/EVENT_FACT?$filter=event_fact_id%20ge%207...
> Which is identical to the JDBC query used:
> select * from event_fact where event_fact_id between 747000000 and 747200000;
> In both cases the result contains 200.000 rows
> ODATA log information analysis (log file ’server start + odata batch 256.log’):
> row 4543 - 4657 - Start query
> row 4658 - 9030 - Read ALL results from result set and store them in buffer
> row 9031 - 9035 - Close DB connection
> row 9036 - 14647 - Clean buffers and create response?
> row 14648 - 14661 - return first batch and close connection
> JDBC log information analysis (log file ’server start + jdbc.log’):
> row 4925 - 5112 - Start query
> row 5113 - 5166 - Read ONLY the first 2048 results from result set and store them in buffer and return response
> row 5157 - 5214 - Close DB connection
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 11 months
[JBoss JIRA] (TEIID-2802) HIVE2: got Invalid table alias or column reference when running UNION ALL query on HIVE2
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2802?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2802.
---------------------------------
> HIVE2: got Invalid table alias or column reference when running UNION ALL query on HIVE2
> -----------------------------------------------------------------------------------------
>
> Key: TEIID-2802
> URL: https://issues.jboss.org/browse/TEIID-2802
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.6
> Environment: TEIID with HIVE2
> Reporter: Ivan Chan
> Assignee: Steven Hawkins
> Labels: teiid
> Fix For: 8.7
>
>
> If I tried to combine 2 tables from a same HIVE2 data source using UNION ALL, I got "Invalid table alias or column reference" error.
> Query that I submitted to Teiid originally:
> select "name"
> from (Select * from hive2.opportunities_small UNION ALL Select * from
> hive2.opportunities) "query"
> group by "name"
> order by "name"
> Query that Teiid generated:
> SELECT v_0.c_0 FROM (SELECT c_0 FROM (SELECT g_1.name AS c_0 FROM
> opportunities_small g_1 UNION ALL SELECT g_0.name AS c_0 FROM opportunities
> g_0) X__) v_0 GROUP BY v_0.c_0 ORDER BY v_0.c_0
> Error:
> Invalid table alias or column reference 'v_0': (possible column names are: c_0)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 11 months