June 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Resolved: (TEIID-966) User (principal) name in MetaMatrix should be consistently the same string

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-966?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins resolved TEIID-966. --------------------------------- Fix Version/s: 7.0 (was: 7.1) Resolution: Done With all of the teiid/security changes there is only one server side representation of the username. > User (principal) name in MetaMatrix should be consistently the same string > -------------------------------------------------------------------------- > > Key: TEIID-966 > URL: https://jira.jboss.org/browse/TEIID-966 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 7.0 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 7.0 > > > The issue has to do with the way we represent a user's name. Customer uses LDAP for a membership domain. Sometimes, the user's name is their cn, followed by "@" plus the domain name, e.g.: > username@LDAP > Sometimes, it's simply the user name. e.g.: > username > This name is recorded in the audit logs, used throughout Console, and perhaps most importantly, is the name returned by the USER() system function. > The problem is that we use the return value of USER() to record information about who is doing things. Later, we make comparisons against this info to control access, etc. This comparison often fails, even though we may be comparing the same identity, due to this inconsistency. > Workaround for the USER() function: build in special logic within each procedure to strip out the @LDAP if it is present. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIID-250) Enable Axis data compression in SFDC Connector, per SFDC API guidelines

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-250?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins commented on TEIID-250: ------------------------------------- Is this still relevant now that we are using CXF? > Enable Axis data compression in SFDC Connector, per SFDC API guidelines > ----------------------------------------------------------------------- > > Key: TEIID-250 > URL: https://jira.jboss.org/browse/TEIID-250 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector > Affects Versions: 6.0.0 > Environment: MetaMatrix 5.5.2 with patch 0037/SFDC GA connector > Reporter: Greg Haber > Assignee: John Doyle > Fix For: 7.1 > > > The SFDC doc includes a set of performance guidelines for using their API (http://blog.sforce.com/sforce/2005/04/performance_tip.html). One of the guidelines: > Use compression, unless you have an OC45 connection into the back of your machine, compression will help reduce transmission times, the Sforce API supports gzip and deflate compression for both request and response. > does not look like it has been implemented in our connector. In theory, this will be a big optimization when returning large data sets, as is the case at Genentech. This is also a trivial optimization to implement, so we should at least try this out and see what the impact is. > The process for enabling this is described on http://wiki.apexdevnet.com/index.php/Compression_with_Axis_1.3 - essentially, you subclass the SforceServiceLocator class in the salesforce.jar to set a few Axis-specific properties (complete code for subclass is at the link), and then in our connector (in ConnectionImpl) we call this subclass instead of calling the SforceServiceLocator directly, as we are doing today. > This is a very low hanging fruit with a big upside - please implement soon. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-93) when a fairly complex query is pushed down to the XML-HTTP Connector, it fails

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-93?page=com.atlassian.jira.plugin.sys... ] Steve Hawkins resolved TEIID-93. -------------------------------- Fix Version/s: 7.0 (was: 7.1) Resolution: Out of Date This functionality has been replaced with XMLTABLE, which doesn't need to process criteria. > when a fairly complex query is pushed down to the XML-HTTP Connector, it fails > ------------------------------------------------------------------------------ > > Key: TEIID-93 > URL: https://jira.jboss.org/browse/TEIID-93 > Project: Teiid > Issue Type: Bug > Components: XML Connector > Affects Versions: 8.x > Reporter: Steven Hawkins > Fix For: 7.0 > > > Defect Tracker #25059: when a fairly complex query is pushed down to the XML-HTTP > Connector, it fails > Need a lot more information. > OK, here's how to reproduce this issue (which we hit at Citi). Use the attached model project set in 5.5.1RC2 Designer, and use the response.xml attached with your standard xmltool.war tester. Then issue the following query from Designer: > >> > >> select H_RelationshipID, H_RelationshipName, H_HHID, H_TeamLeadName, H_TeamLeadID, H_MemberFirstName, H_MemberLastName, H_MemberAcctID, H_MemberFCName, H_MemberFCNum, H_HHLeadInd, H_MemberType, H_MemberRole, H_clientId, A_ADDR_TYPE, A_ADDR_SUB_TYPE, A_ADDR_SUB_NAME, A_ADDR_LINE1, A_ADDR_LINE2, A_ADDR_LINE3, A_ADDR_LINE4, A_ADDR_LINE5, A_ADDR_LINE6, A_ADDR_FLAG1, A_ADDR_FLAG2, A_ADDR_FLAG3, A_ADDR_FLAG4, A_ADDR_FLAG5, A_ADDR_FLAG6, A_CITY, A_ZIP, A_STATE_CODE, A_POSTAL_CODE, A_COUNTRY, A_ALTA_TYPE, A_EFF_DATE, A_EXP_DATE from "RPXMLTest"."CustRelnDataWS.WS.RetrieveCustRelnData.relnDataSingleTable" where A_ADDR_TYPE IN ('BA','AA') AND ((A_ADDR_TYPE IN('AA')) AND(NVL(A_ALTA_TYPE,'') = '')) > >> > >> This plans to the following source query being pushed to the connector: > >> > >> SELECT A_ALTA_TYPE, H_RelationshipID, H_RelationshipName, H_HHID, H_TeamLeadName, H_TeamLeadID, H_MemberFirstName, H_MemberLastName, H_MemberAcctID, H_MemberFCName, H_MemberFCNum, H_HHLeadInd, H_MemberType, H_MemberRole, H_clientId, A_ADDR_TYPE, A_ADDR_SUB_TYPE, A_ADDR_SUB_NAME, A_ADDR_LINE1, A_ADDR_LINE2, A_ADDR_LINE3, A_ADDR_LINE4, A_ADDR_LINE5, A_ADDR_LINE6, A_ADDR_FLAG1, A_ADDR_FLAG2, A_ADDR_FLAG3, A_ADDR_FLAG4, A_ADDR_FLAG5, A_ADDR_FLAG6, A_CITY, A_ZIP, A_STATE_CODE, A_POSTAL_CODE, A_COUNTRY, A_EFF_DATE, A_EXP_DATE FROM RPXMLTest.CustRelnDataWS.WS.RetrieveCustRelnData.relnDataSingleTable WHERE (A_ADDR_TYPE IN ('BA', 'AA')) AND (A_ADDR_TYPE = 'AA') > >> > >> Now, the criteria here says that A_ADDR_TYPE needs to be in the set of 'AA', 'BA', AND needs to be equal to 'AA'. So really only those "rows" where A_ADDR_TYPE='AA' should be returned. But instead the connector returns all rows where A_ADDR_TYPE is 'AA' or 'BA'. > >> > > > > This seems like it could be a defect in the way we hande IN criteria. Was there ever a case or defect on this? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Closed: (TEIID-244) Salesforce Connector should offer the abilty to query about object deletions.

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-244?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins closed TEIID-244. ------------------------------- > Salesforce Connector should offer the abilty to query about object deletions. > ----------------------------------------------------------------------------- > > Key: TEIID-244 > URL: https://jira.jboss.org/browse/TEIID-244 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector > Affects Versions: 6.0.0 > Reporter: John Doyle > Assignee: John Doyle > Fix For: 6.1.0 > > > Genentech wants to materialize lots of SalesForce data in Oracle, to speed up their reporting query times. It makes a significant difference because SFDC does not support joins, whereas Oracle does. Wanting the best of both worlds, they also want the data to be as fresh as possible -- ideally, the mat views would be no more than 10 minutes out-of-sync with the live data. > The amount of data in SalesForce already takes 20+ minutes to cache, and it will slowly grow over time. So, the current materialization process will not meet the cache coherence (freshness) requirement, since the data will be stale by the time the staging table is populated and swapped in. > How would you speed it up? > .......response.... > I actually put together a custom materialization script > (attached,with doc and sample config file) for Credit Suisse for doing > these sorts of partial refreshes. It is Oracle-specific, but since > that is what you are doing too it should work for you too. > However, the use case at Credit Suisse was for doing these partial > refreshes nightly, with full refreshes done weekly. There is (just as > with our standard materialization scripts) a short period (when the > table names are being swapped) when the materialization won't be stable > (queries could fail or return unexpected results). I don't know if > that makes it not suitable for doing 10 minute refreshes. > I would recommend instead using the materialization only for historical > data (from overnight materialization run), and unioning it to the live > data for the newer stuff. That is, query SFDC only for data where > createdDate or LastModifiedDate = today, and union that with the > current data. Two issues you'd need to deal with in your logic: > -if the same record is retrieved from both sources (meaning it was an > existing record that had been modified today), the historical record > should be discarded in favor of the live one. > -deleted records - how to detect records that were deleted today? If > you could ask SFDC exactly what was deleted today that would be great, > but that is probably wishful thinking. So failing that you would need > to ask SFDC for the keys for all live records, and then discard from > the historical data any records with keys not on that list. Or, you > could just live with having the deleted records in the view for an > extra day... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1085) AdminShell (Groovy) shows connectionName even after that connection has been disconnected

by Paul Nittel (JIRA)

AdminShell (Groovy) shows connectionName even after that connection has been disconnected ----------------------------------------------------------------------------------------- Key: TEIID-1085 URL: https://jira.jboss.org/jira/browse/TEIID-1085 Project: Teiid Issue Type: Bug Environment: Fedora 12, OpenJDK Runtime Environment (IcedTea6 1.7.1) (fedora-37.b17.fc12-i386) OpenJDK Server VM (build 14.0-b16, mixed mode) Teiid from 5/5/2010 Reporter: Paul Nittel Assignee: Steven Hawkins Attachments: TestAdmin.groovy 1 - Create a named connection 2 - getVDBs() 3 - Create an new connection 4 - Use the first 5 - disconnect 6 - getAllConnections() - still shows the one you disconnected. Try the attached groovy script. -- 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

14 years, 6 months

2
4
0 / 0

[JBoss JIRA] Closed: (TEIID-315) Add JDBC Connector developers guide

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-315?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins closed TEIID-315. ------------------------------- > Add JDBC Connector developers guide > ----------------------------------- > > Key: TEIID-315 > URL: https://jira.jboss.org/browse/TEIID-315 > Project: Teiid > Issue Type: Sub-task > Components: Documentation > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 7.0 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Closed: (TEIID-963) Need to add XPath 2.0 support for services in and out of MM

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-963?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins closed TEIID-963. ------------------------------- > Need to add XPath 2.0 support for services in and out of MM > ----------------------------------------------------------- > > Key: TEIID-963 > URL: https://jira.jboss.org/browse/TEIID-963 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Debbie Steigner > Fix For: 7.0 > > > If we are using different versions of the lib for out-the-top and > in-the-bottom then I think we should definitely address it. If you can > confirm this, can we please get it logged as an enhancement with > semi-high priority? > We need to support XPath 2.0 for both in and out services. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1119) Trying to add new functions to be supported by a new connector and the Connector developers guide refers to the JDBCCapabilities class, which doesn't exist anymore. Have the steps changed to add a new scalar function?

by Van Halbert (JIRA)

Trying to add new functions to be supported by a new connector and the Connector developers guide refers to the JDBCCapabilities class, which doesn't exist anymore. Have the steps changed to add a new scalar function? -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: TEIID-1119 URL: https://jira.jboss.org/browse/TEIID-1119 Project: Teiid Issue Type: Bug Components: Documentation Reporter: Van Halbert Assignee: Steve Hawkins Fix For: 7.0 Referring to the Connectors Developers Guide when trying to adding new scalar functions, but the first step says to: Modify the capabilities class to declare support for the function (REQUIRED) and the example shows the JDBCCapabilities class being extended. I don't think the steps are correct. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (TEIID-1032) Change nomenclature of "Connector Binding" to "Connection Factory"

by Ramesh Reddy (JIRA)

Change nomenclature of "Connector Binding" to "Connection Factory" ------------------------------------------------------------------ Key: TEIID-1032 URL: https://jira.jboss.org/jira/browse/TEIID-1032 Project: Teiid Issue Type: Sub-task Components: Build/Kits, Common, Connector API, Documentation Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.0 With the migration of Connectors to the JCA container, using the name "Connector Binding" is different than that of "Connection Factory" usage in the container world. Change all the references in code, pubic api and documentation to reflect the name change -- 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

14 years, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (TEIID-933) AdminShell taking exception to a query that's executing in the Designer

by Paul Nittel (JIRA)

AdminShell taking exception to a query that's executing in the Designer ----------------------------------------------------------------------- Key: TEIID-933 URL: https://jira.jboss.org/jira/browse/TEIID-933 Project: Teiid Issue Type: Bug Components: Tools Affects Versions: 7.0 Environment: Fedora 12, OpenJDK Server VM (build 14.0-b16, mixed mode), Teiid build 1/19/2010 Reporter: Paul Nittel Assignee: Steven Hawkins I'm executing the TPCR quesier and #7 is failing in AdminShell. It does successfully execute in SQL Explorer. The query being executed is: select * from vTpcr.Q07 ORDER BY supp_nation, cust_nation, l_year The transformation behind the query is: SELECT supp_nation, cust_nation, l_year, SUM(volume) AS revenue FROM (SELECT n1.N_NAME AS supp_nation, n2.N_NAME AS cust_nation, YEAR(L_SHIPDATE) AS l_year, (L_EXTENDEDPRICE * (1 - L_DISCOUNT)) AS volume FROM TPCR.SUPPLIER, TPCR.LINEITEM, TPCR.ORDERS, TPCR.CUSTOMER, TPCR.NATION AS n1, TPCR.NATION AS n2 WHERE (S_SUPPKEY = L_SUPPKEY) AND (O_ORDERKEY = L_ORDERKEY) AND (C_CUSTKEY = O_CUSTKEY) AND (S_NATIONKEY = n1.N_NATIONKEY) AND (C_NATIONKEY = n2.N_NATIONKEY) AND (((n1.N_NAME = 'FRANCE') AND (n2.N_NAME = 'GERMANY')) OR ((n1.N_NAME = 'GERMANY') AND (n2.N_NAME = 'FRANCE'))) AND (L_SHIPDATE BETWEEN {ts'1995-01-01 00:00:00.0'} AND {ts'1996-12-31 00:00:00.0'})) AS shipping GROUP BY supp_nation, cust_nation, l_year Executing the transformation query in AdminShell also fails. AdminShell provides this error information: select * from vTpcr.Q07; // Error: // Uncaught Exception: TargetError : at Line: 241 : in file: URL: jar:file:/home/pnittel/Teiid0119/teiid-adminshell-7.0.0-SNAPSHOT/lib/teiid-adminshell-7.0.0-SNAPSHOT.jar!/scripts/jdbc.bsh : throw e ; Called from method: execute : at Line: 4 : in file: <unknown file> : execute ( "select * from vTpcr.Q07" ) Target exception: com.metamatrix.jdbc.MMSQLException: com.metamatrix.api.exception.MetaMatrixComponentException Many files will be attached. -- 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

14 years, 6 months

3
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2010