April 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-472) Teiid Embedded unable to login to JDBC data sources requiring username/password

by Paul Nittel (JIRA)

Teiid Embedded unable to login to JDBC data sources requiring username/password ------------------------------------------------------------------------------- Key: TEIID-472 URL: https://jira.jboss.org/jira/browse/TEIID-472 Project: Teiid Issue Type: Bug Components: Embedded Affects Versions: 6.0.0 Environment: fedora 10, Teiid Designer 040709, Teiid 6.0.0 Reporter: Paul Nittel Assignee: Steven Hawkins I took the PartsSupplier_VDB from the Designer and tried to use it in Teiid Embedded. Using a simple JDBC query tool, I was unable to login to the data sources (Oracle and SQL Server). Working with Ramesh, we found we could edit the configuration.def inside the VDB and edit the mm-encrypted password to plain text and it would work. As an alternative, we could use the configuration.xml file from the Designer and that worked. Ramesh will fill in the technical details... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
8
0 / 0

[JBoss JIRA] Created: (TEIID-440) Capture the vendor SQLSTATE code, if the connector connection fails

by Ramesh Reddy (JIRA)

Capture the vendor SQLSTATE code, if the connector connection fails ------------------------------------------------------------------- Key: TEIID-440 URL: https://jira.jboss.org/jira/browse/TEIID-440 Project: Teiid Issue Type: Feature Request Components: Misc. Connectors Affects Versions: 6.0.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Priority: Trivial Fix For: 6.1.0 Currently when the JDBC connector fails to make the connection, we correctly unroll the SQLException, but do not provide the SQLSTATE code on to the wrapping exception's description, so that it is visible in the Teiid's logs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
2
0 / 0

[JBoss JIRA] Reopened: (TEIID-428) System Property Changes - Not showing up in Audit Log and System Log has entry but doesn't state what property was changed

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-428?page=com.atlassian.jira.plug... ] Steven Hawkins reopened TEIID-428: ---------------------------------- reopenning to change system logs to audit logs > System Property Changes - Not showing up in Audit Log and System Log has entry but doesn't state what property was changed > -------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-428 > URL: https://jira.jboss.org/jira/browse/TEIID-428 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 6.0.0 > Environment: Windows client running against Windows server > Reporter: Warren Gibson > Assignee: Steven Hawkins > Priority: Optional > Fix For: 6.1.0 > > Attachments: log.rtf > > > I changed 4 System Properties and found no entries in the Audit log but entries did show up in the System Log. However the entries in the System log does not specify which property was changed. Changes to System Properties should show up in Audit Log. This is one example. See attachment for other examples: > My action - Encryption - Unchecked Client Side Password. > Log: > Mar 06, 2009 14:07:47.500 [SocketWorkerQueue_Worker_52|0] ERROR <AUDIT_ADMIN|0> Administrator [ssmith@NewLDAP], session [7512] requesting access which requires role [Admin.SystemAdmin] to method [ConfigurationAdminAPIImpl.executeTransaction([Set ConfigurationID Next Startup; new value = false, previous value = true])]. > Mar 06, 2009 14:07:47.500 [SocketWorkerQueue_Worker_52|0] ERROR <AUDIT_ADMIN|0> Administrator [ssmith@NewLDAP], session [7512] granted access to method [ConfigurationAdminAPIImpl.executeTransaction([Set ConfigurationID Next Startup; new value = false, previous value = true])]. > Mar 06, 2009 14:07:47.515 [SocketWorkerQueue_Worker_52|0] INFO <CONFIG|0> Completed execution of actions. > Mar 06, 2009 14:07:47.546 [SocketWorkerQueue_Worker_52|0] INFO <CONFIG|0> Configuration Next Startup document written successfully to stream. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Work started: (TEIID-521) Prepared statement methods addBatch() and clearBatch() can cause NullPointerException

by Larry O'Leary (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-521?page=com.atlassian.jira.plug... ] Work on TEIID-521 started by Larry O'Leary. > Prepared statement methods addBatch() and clearBatch() can cause NullPointerException > ------------------------------------------------------------------------------------- > > Key: TEIID-521 > URL: https://jira.jboss.org/jira/browse/TEIID-521 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 6.0.0 > Reporter: Larry O'Leary > Assignee: Larry O'Leary > Fix For: 6.1.0 > > Attachments: TestMMPreparedStatement.java > > > When attempting to debug an unrelated issue I discovered that the batch processing methods on a prepared statement can result in a NullPointerException depending on when the methods are called. > For example: > java.lang.NullPointerException > at com.metamatrix.jdbc.MMStatement.clearBatch(MMStatement.java:274) > at com.metamatrix.jdbc.TestPreparedStatementBatchedUpdate.testInserts(TestPreparedStatementBatchedUpdate.java:102) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at junit.framework.TestCase.runTest(TestCase.java:154) > at junit.framework.TestCase.runBare(TestCase.java:127) > at junit.framework.TestResult$1.protect(TestResult.java:106) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at junit.framework.TestResult.run(TestResult.java:109) > at junit.framework.TestCase.run(TestCase.java:118) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) > Is a result of calling clearBatch() on a statement after it was done executing a batched update. It appears this is simply a need of NOT calling clearBatch() at the wrong time but I feel that we should gracefully handle this situation as a clearBatch() call may appear in a try/catch/finally block. > The same goes for addBatch() if no parameters have been set. Not sure if we should actually throw an exception in such a case or not as it makes no sense to call addBatch() with no parameters defined but it would also make sense that we would not throw a nasty NPE in such a case. > I have only seen this on R050502 and R050503 and have not looked at R050504c or Teiid. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-539) Add UnitTest coverage for BetweenCriteria to be rewritten as CompoundCriteria

by Larry O'Leary (JIRA)

Add UnitTest coverage for BetweenCriteria to be rewritten as CompoundCriteria ----------------------------------------------------------------------------- Key: TEIID-539 URL: https://jira.jboss.org/jira/browse/TEIID-539 Project: Teiid Issue Type: Task Components: Query Engine Affects Versions: 6.1.0 Reporter: Larry O'Leary Assignee: Larry O'Leary Priority: Minor Test cases need to be added to cover testing of BETWEEN expressions being rewritten as compound criteria. For example: SELECT SUM(CASE WHEN e2 BETWEEN 3 AND 5 THEN e2 ELSE -1 END) FROM pm1.g1 should become: SELECT SUM(CASE WHEN (e2 >= 3) AND (e2 <= 5) THEN e2 ELSE -1 END) FROM pm1.g1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
2
0 / 0

[JBoss JIRA] Commented: (TEIID-233) Server should support JGroups communication over P2P

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-233?page=com.atlassian.jira.plug... ] Ramesh Reddy commented on TEIID-233: ------------------------------------ To support the all the cluster combinations, the following properties will be added to the configuration (some of previous properties are renamed) # cluster.use_multicast = true Multicast used, false Unicast used # cluster.protocol = TCP or UDP (if unicast) # cluster.unicast.members = comma separated list of cluster hosts if TCP Unicast in use. (Ex: config.name=host.name, config.name=host.name) # If UDP Unicast this refers to single gossip server (ex:host[port]) # cluster.multicast.address = blank address will default to 224.xx.xx.xx where xx is current host IP. # cluster.port= Can be multicast port or TCP Unicast port cluster.use_multicast=false cluster.protocol=TCP cluster.unicast.members= cluster.multicast.address= cluster.port=5555 cluster.name=TEIID-CLUSTER During the installation, the properties are used as following "cluster.use_multicast = true", then multicast is used, then user need to specify 1. cluster.multicast.address=224.xx.xx.xx 2. cluster.port=5555 3. cluster.name=my-cluster-name When the "cluster.use_multicast = false", the Unicast is in use, now use has choice of using TCP or UDP protocols if (cluster.protocol=TCP ) then cluster.port=5555 cluster.unicast.members=specifies all the cluster members end else if (cluster.protocol=UDP ) then cluster.unicast.members= specifies the gossip router information end When "TCP" based clustering is used (default mode) The "cluster.unicast.members" property will be stored in the bootstrap properties. This property can be specified by the user during installation of server as to what are all the cluster members (with their host names), or user can edit this file at a later date manually when they add a new cluster member. If this file is not edited then, discovery is not possible. There are couple methods of discovery is possible, but they all come with certain disadvantages of maintenance of the runtime configuration information. More over that can be add-on to this process at a later date as the requirement arises. > Server should support JGroups communication over P2P > ---------------------------------------------------- > > Key: TEIID-233 > URL: https://jira.jboss.org/jira/browse/TEIID-233 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 6.0.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 6.1.0 > > > Currently Server only supports the JGroups over Multicast we need to support unicast protocol tool, with configuration. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-537) PostgreSQL repository schema is missing the EXCEPTION column?

by Van Halbert (JIRA)

PostgreSQL repository schema is missing the EXCEPTION column? ------------------------------------------------------------- Key: TEIID-537 URL: https://jira.jboss.org/jira/browse/TEIID-537 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 6.1.1 Reporter: Van Halbert Assignee: Van Halbert Fix For: 6.1.1 Simple to reproduce: 1 - Log onto a PostgreSQL-based server (sllxmm03:55701) 2 - Switch to the Log Viewer 3 - Click the Submit button Should get results, but I'm getting the attached exception. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
2
0 / 0

[JBoss JIRA] Resolved: (TEIID-178) Implement sort minimization in process plans

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-178?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-178. ---------------------------------- Resolution: Done Added RulePlanSorts. It chooses the algorithm type for dup removal and combines sorts/dup removal when possible. > Implement sort minimization in process plans > -------------------------------------------- > > Key: TEIID-178 > URL: https://jira.jboss.org/jira/browse/TEIID-178 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Optional > Fix For: 6.1.0 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Sorting for order bys, dub removal, merge joins, and grouping should be minimized after the process plan has been determined. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-175) Asynchronous union results

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-175?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-175. ---------------------------------- Resolution: Done Implemented by modifying the sort algorithm used for duplicate removal. An output list is maintained along with the sorted list. > Asynchronous union results > -------------------------- > > Key: TEIID-175 > URL: https://jira.jboss.org/jira/browse/TEIID-175 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Priority: Optional > Fix For: 6.1.0 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > This is really a request for a dup-removal algorithm that can return results without waiting for all results. This would be generally less efficient than the full-sort approach, so it would be good to base the decision on a hint or costing information. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIID-178) Implement sort minimization in process plans

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-178?page=com.atlassian.jira.plug... ] Steven Hawkins reassigned TEIID-178: ------------------------------------ Assignee: Steven Hawkins > Implement sort minimization in process plans > -------------------------------------------- > > Key: TEIID-178 > URL: https://jira.jboss.org/jira/browse/TEIID-178 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Optional > Fix For: 6.1.0 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Sorting for order bys, dub removal, merge joins, and grouping should be minimized after the process plan has been determined. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2009