October 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1733) Update the Salesforce translator to the latest API, version 22

by Mark Drilling (JIRA)

Update the Salesforce translator to the latest API, version 22 -------------------------------------------------------------- Key: TEIID-1733 URL: https://issues.jboss.org/browse/TEIID-1733 Project: Teiid Issue Type: Feature Request Components: Connector API Affects Versions: 7.4 Reporter: Mark Drilling Assignee: Ramesh Reddy The salesforce translator is currently on V17 of the API. It should be upgraded to the latest (currently V22). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
8
0 / 0

[JBoss JIRA] (TEIID-1785) EDS cross join attempting to join on mismatching datatypes

by Steven Hawkins (Resolved) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1785?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-1785. ----------------------------------- Resolution: Duplicate Issue Dup of TEIID-1778 > EDS cross join attempting to join on mismatching datatypes > ---------------------------------------------------------- > > Key: TEIID-1785 > URL: https://issues.jboss.org/browse/TEIID-1785 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.4.1 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > When running a query which appears to be attempting a cross join, from looking at the query plan. This is resulting in an error and stack trace, pointing to the merge join implementation trying to convert from integer to string. > This is when we provide one item to filter on, so it appears EDS is selecting the number 1 to indicate if it is present, and I think this is what it's trying to join to. When providing more than one thing to filter on, so EDS selects the book ID, the query runs. > Good and bad query plans are attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1794) Teiid Plugin shows zero for all metrics except Session Count

by Ted Jones (Issue Comment Edited) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1794?page=com.atlassian.jira.plugin... ] Ted Jones edited comment on TEIID-1794 at 10/25/11 2:26 PM: ------------------------------------------------------------ Corrected ClassCastException as well as corrected incorrect field names for operations (Requests, Long Running Requests). Also corrected parameter order for "Terminate Request" operation. was (Author: tejones): Corrected ClassCastException as well as corrected incorrect field names for operations (Requests, Long Running Requests). Also corrected and parameter order for "Terminate Request" operation. > Teiid Plugin shows zero for all metrics except Session Count > ------------------------------------------------------------ > > Key: TEIID-1794 > URL: https://issues.jboss.org/browse/TEIID-1794 > Project: Teiid > Issue Type: Bug > Components: Jopr Plugin > Affects Versions: 7.4.1 > Reporter: Debbie Steigner > Assignee: Ted Jones > Priority: Critical > > Using either JON or the Admin Console no metrics appear to be collected for Data Services except Session count. All measurements are enable and set to collect every 10 minutes, but nothing happens. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1791) Only the first 1000 items in the IN criteria are being pushed down in the query

by Steven Hawkins (Resolved) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1791?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-1791. ----------------------------------- Assignee: Steven Hawkins Fix Version/s: 7.4.1 7.6 Resolution: Done The issue is that if there is more than 1 source contributing to a dependent join (which means more than 1 processing node - a join of two tables providing values would be a single source) and the first source can be added completely in a single while a latter source needs more than 1 predicate, then only the first predicate of the latter source is added. The fix was to correct when the source index was incremented in DependentCriteriaProcessor. > Only the first 1000 items in the IN criteria are being pushed down in the query > ------------------------------------------------------------------------------- > > Key: TEIID-1791 > URL: https://issues.jboss.org/browse/TEIID-1791 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.4.1 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 7.4.1, 7.6 > > > In the below query, we are expecting a large number of book codes (46987), to be passed from ledgerbookid in t_sdm_ledgerbook into the TSL_FINANCIAL_ACCOUNT_ITEMS_T2 table. We can see from the query plan that it got the correct number of rows. > I understand that Oracle can only take 1000 items in an IN() construct, so EDS will split the criteria into multiple sets of 1000 IN criteria. I have seen this work previously. > It seems that for some reason in this query, possibly the other dependent join or hints, EDS pushes exactly 1000 criteria. Looking at the source specific SQL command in the EDS debug log, which I have attached, I counted the number of question marks in that IN() and it comes to 1000. We have checked that all of these book codes are unique, by doing a select distinct to the source model. > select cc.costcentreid, cc.description , ac.accountdescription, sum(func_amount) > from TSL_FINANCIAL_ACCOUNT_ITEMS_T2 tsl > join t_sdm_glaccount ac on tsl.account_code = ac.accountid > join /*+ MAKEIND */t_sdm_ledgerbook lb on tsl.book_code = lb.ledgerbookid > join /*+ MAKEIND */t_sdm_costcentre cc on lb.parentcostcentreid = cc.costcentreid > join /*+ MAKEIND */t_sdm_desk dsk on cc.parentdeskid = dsk.deskid > join /*+ MAKEIND */t_sdm_businessarea ba on dsk.parentbusinessareaid = ba.businessareaid > join /*+ MAKEIND */t_sdm_division div on ba.parentdivisionid = div.divisionid > where tsl.business_date = '2011-06-29' > and div.divisionid = 'GBM' > and ac.classificationid in (3,4) > group by cc.costcentreid, cc.description, ac.accountdescription; -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1794) Teiid Plugin shows zero for all metrics except Session Count

by Ted Jones (Resolved) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1794?page=com.atlassian.jira.plugin... ] Ted Jones resolved TEIID-1794. ------------------------------ Resolution: Done > Teiid Plugin shows zero for all metrics except Session Count > ------------------------------------------------------------ > > Key: TEIID-1794 > URL: https://issues.jboss.org/browse/TEIID-1794 > Project: Teiid > Issue Type: Bug > Components: Jopr Plugin > Affects Versions: 7.4.1 > Reporter: Debbie Steigner > Assignee: Ted Jones > Priority: Critical > > Using either JON or the Admin Console no metrics appear to be collected for Data Services except Session count. All measurements are enable and set to collect every 10 minutes, but nothing happens. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1794) Teiid Plugin shows zero for all metrics except Session Count

by Ted Jones (Commented) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1794?page=com.atlassian.jira.plugin... ] Ted Jones commented on TEIID-1794: ---------------------------------- Corrected ClassCastException as well as corrected incorrect field names for operations (Requests, Long Running Requests). Also corrected and parameter order for "Terminate Request" operation. > Teiid Plugin shows zero for all metrics except Session Count > ------------------------------------------------------------ > > Key: TEIID-1794 > URL: https://issues.jboss.org/browse/TEIID-1794 > Project: Teiid > Issue Type: Bug > Components: Jopr Plugin > Affects Versions: 7.4.1 > Reporter: Debbie Steigner > Assignee: Ted Jones > Priority: Critical > > Using either JON or the Admin Console no metrics appear to be collected for Data Services except Session count. All measurements are enable and set to collect every 10 minutes, but nothing happens. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1654) CLONE - EDS - Node returns 0 rows for cached view when other node had it loaded and leaves cluster

by Paul Nittel (Closed) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1654?page=com.atlassian.jira.plugin... ] Paul Nittel closed TEIID-1654. ------------------------------ Tested and closed. > CLONE - EDS - Node returns 0 rows for cached view when other node had it loaded and leaves cluster > -------------------------------------------------------------------------------------------------- > > Key: TEIID-1654 > URL: https://issues.jboss.org/browse/TEIID-1654 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.1 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 7.4.1, 7.5 > > > Using an internal materialized view in EDS 5.1 with CP2, a node which never had a copy of an IMV cache will return 0 rows when it should be querying the source in situations where another node in the cluster had cached the IMV but is no longer in the cluster -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1792) Inefficient plan using cartesian join

by Steven Hawkins (Resolved) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1792?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-1792. ----------------------------------- Assignee: Steven Hawkins Fix Version/s: 7.6 7.4 Resolution: Done The root problem was that cardinality was missing on one of the join tables. The unknown value prevented planning from determining the appropriate plan. A change was made to join region scoring to ensure that in this case we do not issue cross joins of unknown size. In general though it is not good to plan a query with a mixture of known and unknown cardinalities. > Inefficient plan using cartesian join > ------------------------------------- > > Key: TEIID-1792 > URL: https://issues.jboss.org/browse/TEIID-1792 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.4.1 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Priority: Critical > Fix For: 7.6, 7.4 > > > We're trying to write a federated query, and we can't get Teiid to create an optimal plan. It is using a cartesian join, which causes Teiid to take a few hours and run out of memory, when we should be fetching a relatively small number of rows. We have tried using the new MAKEIND hint in 5.2, but Teiid seems to ignore it in this case. > See the SOA jura for more information. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1793) Receive " User <user@teiid-security> is not entitled to action <READ> for 1 or more of the groups/elements/procedures." error on unqualified SQL if data roles are active

by Steven Hawkins (Resolved) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1793?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-1793. ----------------------------------- Fix Version/s: 7.4.1 7.6 Resolution: Done Fixed the authorization validation visitor for non-qualified proc relational queries. > Receive " User <user@teiid-security> is not entitled to action <READ> for 1 or more of the groups/elements/procedures." error on unqualified SQL if data roles are active > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-1793 > URL: https://issues.jboss.org/browse/TEIID-1793 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.4.1 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 7.4.1, 7.6 > > > If you run a query 'SELECT * FROM MyProc' i.e. without a model/schema name, You'll receive the below error if an all Access Data Role is assigned to the VDB. If you remove the Data Role, the query succeeds. > Error: Remote org.teiid.api.exception.query.QueryValidatorException: User <user@teiid-security> is not entitled to action <READ> for 1 or more of the groups/elements/procedures. > SQLState: 50000 > ErrorCode: 0 > The query only succeeds if you fully qualify the proc/table when Data Roles are used. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1793) Receive " User <user@teiid-security> is not entitled to action <READ> for 1 or more of the groups/elements/procedures." error on unqualified SQL if data roles are active

by Steven Hawkins (Commented) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1793?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-1793: --------------------------------------- It this ok to check-in for 7.4.1? > Receive " User <user@teiid-security> is not entitled to action <READ> for 1 or more of the groups/elements/procedures." error on unqualified SQL if data roles are active > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-1793 > URL: https://issues.jboss.org/browse/TEIID-1793 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.4.1 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > If you run a query 'SELECT * FROM MyProc' i.e. without a model/schema name, You'll receive the below error if an all Access Data Role is assigned to the VDB. If you remove the Data Role, the query succeeds. > Error: Remote org.teiid.api.exception.query.QueryValidatorException: User <user@teiid-security> is not entitled to action <READ> for 1 or more of the groups/elements/procedures. > SQLState: 50000 > ErrorCode: 0 > The query only succeeds if you fully qualify the proc/table when Data Roles are used. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2011