April 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2939) Issues with applying row based security

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2939?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2939: ---------------------------------- Description: If a view over a left outer join has a row condition and is used in a simple aggregation: select count\(*) from vw Then a null pointer exception will occur when considering optional joins. If intervening criteria is added: select count\(*) from vw where ... we can get past the initial error, but will fail in initializing the join node with an assertion error. Both of these have the same root issue, which is our attempt to make the logic selective about when assign output elements is run, which leads to the output elements not being in place when later needed. was: If a view over a left outer join has a row condition and is used in a simple aggregation: select count(*) from vw Then a null pointer exception will occur when considering optional joins. If intervening criteria is added: select count(*) from vw where ... we can get past the initial error, but will fail in initializing the join node with an assertion error. Both of these have the same root issue, which is our attempt to make the logic selective about when assign output elements is run, which leads to the output elements not being in place when later needed. > Issues with applying row based security > --------------------------------------- > > Key: TEIID-2939 > URL: https://issues.jboss.org/browse/TEIID-2939 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.8 > > > If a view over a left outer join has a row condition and is used in a simple aggregation: > select count\(*) from vw > Then a null pointer exception will occur when considering optional joins. > If intervening criteria is added: > select count\(*) from vw where ... > we can get past the initial error, but will fail in initializing the join node with an assertion error. Both of these have the same root issue, which is our attempt to make the logic selective about when assign output elements is run, which leads to the output elements not being in place when later needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2939) Issues with applying row based security

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2939: ------------------------------------- Summary: Issues with applying row based security Key: TEIID-2939 URL: https://issues.jboss.org/browse/TEIID-2939 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.4 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.7.1, 8.8 If a view over a left outer join has a row condition and is used in a simple aggregation: select count(*) from vw Then a null pointer exception will occur when considering optional joins. If intervening criteria is added: select count(*) from vw where ... we can get past the initial error, but will fail in initializing the join node with an assertion error. Both of these have the same root issue, which is our attempt to make the logic selective about when assign output elements is run, which leads to the output elements not being in place when later needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2938) Provide ability to write command and audit logging to database

by Van Halbert (JIRA)

Van Halbert created TEIID-2938: ---------------------------------- Summary: Provide ability to write command and audit logging to database Key: TEIID-2938 URL: https://issues.jboss.org/browse/TEIID-2938 Project: Teiid Issue Type: Feature Request Components: Server Affects Versions: 8.7 Reporter: Van Halbert Assignee: Steven Hawkins Provide ability for command logging and audit logging to write to the database. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2937) Change Apache POI version to 3.10

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2937?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2937: ------------------------------------- Upgraded the version in the 8.8 branch, keeping the 8.7.1 open until the BOM is updated > Change Apache POI version to 3.10 > --------------------------------- > > Key: TEIID-2937 > URL: https://issues.jboss.org/browse/TEIID-2937 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.7 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Fix For: 8.7.1, 8.8 > > > Upgrade the Apache POI version used in accessing Excel file to use POI 3.10. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2937) Change Apache POI version to 3.10

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2937?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2937: -------------------------------- Fix Version/s: 8.7.1 8.8 (was: 8.7) > Change Apache POI version to 3.10 > --------------------------------- > > Key: TEIID-2937 > URL: https://issues.jboss.org/browse/TEIID-2937 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.7 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Fix For: 8.7.1, 8.8 > > > Upgrade the Apache POI version used in accessing Excel file to use POI 3.10. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2893) Add support for EAP 6.3

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2893?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2893. --------------------------------- Resolution: Done Upgraded the library versions to based upon EAP 6.3. In order to build one would require access to the EAP 6.3 maven repo in their maven settings.xml file. > Add support for EAP 6.3 > ----------------------- > > Key: TEIID-2893 > URL: https://issues.jboss.org/browse/TEIID-2893 > Project: Teiid > Issue Type: Feature Request > Components: Build/Kits, Server > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 8.7.1 > > > Add support for EAP 6.2 or 6.3. The final version will not be known until EAP 6.3 release date is known. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2937) Change Apache POI version to 3.10

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2937?page=com.atlassian.jira.plugin... ] Van Halbert edited comment on TEIID-2937 at 4/28/14 10:12 AM: -------------------------------------------------------------- Yes, they've updated the bom to use that version. Do we need to push back and ask for 3.9? was (Author: van.halbert): Yes, they've updated the bom to use that version. > Change Apache POI version to 3.10 > --------------------------------- > > Key: TEIID-2937 > URL: https://issues.jboss.org/browse/TEIID-2937 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.7 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Fix For: 8.7 > > > Upgrade the Apache POI version used in accessing Excel file to use POI 3.10. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2937) Change Apache POI version to 3.10

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2937?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2937: ------------------------------------ Yes, they've updated the bom to use that version. > Change Apache POI version to 3.10 > --------------------------------- > > Key: TEIID-2937 > URL: https://issues.jboss.org/browse/TEIID-2937 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.7 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Fix For: 8.7 > > > Upgrade the Apache POI version used in accessing Excel file to use POI 3.10. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2937) Change Apache POI version to 3.10

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2937?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-2937: ----------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > Change Apache POI version to 3.10 > --------------------------------- > > Key: TEIID-2937 > URL: https://issues.jboss.org/browse/TEIID-2937 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.7 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Fix For: 8.7 > > > Upgrade the Apache POI version used in accessing Excel file to use POI 3.10. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2936) Combining multiple 'in' criteria can prevent pushing criteria to database

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2936?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2936. ----------------------------------- Fix Version/s: 8.8 Resolution: Done Allowing the optimizer to push and then split large in's (into multiple predicates, not queries) by also considering the max dependent sets. However in some circumstances this may lead to source queries with too many bind values. We'll address that scenario later if needed with more bookkeeping. > Combining multiple 'in' criteria can prevent pushing criteria to database > ------------------------------------------------------------------------- > > Key: TEIID-2936 > URL: https://issues.jboss.org/browse/TEIID-2936 > Project: Teiid > Issue Type: Feature Request > Affects Versions: 8.7 > Reporter: Mike Higgins > Assignee: Steven Hawkins > Fix For: 8.8 > > > When two 'in' criteria containing constant values on the same field are combined with an 'or', Teiid will combine the two into a single 'in' operation. > Since Oracle (for example) has a 1000 item limit on the 'in' values, if the resulting combined list contains more than 1000 values, it can no longer be pushed down into Oracle for execution. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2014