October 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3466) Selectivity is over estimated in joins with multiple predicates.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3466?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3466. --------------------------------- > Selectivity is over estimated in joins with multiple predicates. > ------------------------------------------------------------------ > > Key: TEIID-3466 > URL: https://issues.jboss.org/browse/TEIID-3466 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > Selectivity is over estimated in joins with multiple predicates. This is partial due to optional predicates discovered during copy criteria and partially due to always using the independent estimate of selectivity. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3460) Alternative approach to map roles for a Teiid user via ldap login module instead of RoleMappingLoginModule(ie.with out using properties file )

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3460?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3460. --------------------------------- > Alternative approach to map roles for a Teiid user via ldap login module instead of RoleMappingLoginModule(ie.with out using properties file ) > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-3460 > URL: https://issues.jboss.org/browse/TEIID-3460 > Project: Teiid > Issue Type: Feature Request > Components: LDAP Connector > Affects Versions: 8.7 > Reporter: Anu Saji > Assignee: Steven Hawkins > > For the following ldap based login module > ~~~ > <login-module code="org.jboss.security.auth.spi.LdapExtLoginModule" flag="optional" > > <module-option name="java.naming.provider.url"><hostname></module-option> > <module-option name="java.naming.security.protocol">ssl</module-option> > <module-option name="realm">admin</module-option> > <module-option name="bindDN"><username></module-option> > <module-option name="bindCredential"><password></module-option> > <module-option name="baseFilter">(uid={0})</module-option> > <module-option name="baseCtxDN">ou=people,dc=gene,dc=com</module-option> > <module-option name="roleFilter">(uniquemember={1})</module-option> > <module-option name="roleAttributeID">cn</module-option> > <module-option name="rolesCtxDN">ou=Groups,ou=ESB,ou=Applications,dc=gene,dc=com</module-option> > <module-option name="roleAttributeIsDN">false</module-option> > <module-option name="roleRecursion">2</module-option> > <module-option name="searchScope">ONELEVEL_SCOPE</module-option> > <module-option name="java.naming.referral">follow</module-option> > <module-option name="searchTimeLimit">10000</module-option> > </login-module> > <login-module code="org.jboss.security.auth.spi.LdapExtLoginModule" flag="optional" > > <module-option name="java.naming.provider.url"><hostname></module-option> > <module-option name="java.naming.security.protocol">ssl</module-option> > <module-option name="realm">admin</module-option> > <module-option name="bindDN"><username></module-option> > <module-option name="bindCredential"><password></module-option> > <module-option name="baseFilter">(cn={0})</module-option> > <module-option name="baseCtxDN">ou=Apps,ou=ESB,ou=Applications,dc=gene,dc=com</module-option> > <module-option name="roleFilter">(uniquemember={1})</module-option> > <module-option name="roleAttributeID">cn</module-option> > <module-option name="rolesCtxDN">ou=Groups,ou=ESB,ou=Applications,dc=gene,dc=com</module-option> > <module-option name="roleAttributeIsDN">false</module-option> > <module-option name="roleRecursion">2</module-option> > <module-option name="searchScope">ONELEVEL_SCOPE</module-option> > <module-option name="java.naming.referral">follow</module-option> > <module-option name="searchTimeLimit">10000</module-option> > </login-module> >  > <login-module code="org.jboss.security.auth.spi.RoleMappingLoginModule" flag="optional"> > <module-option name="rolesProperties">props/ldap-eds-rolemapping.properties</module-option> > </login-module> > ~~~ > Is there a way around not using the RoleMappingLoginModule (to avaoid usage of properties file ) > Instead use something similar to the declaration in a "web.xml" towards role mapping like below ? > ~~~ > <auth-constraint> > <role-name>TeiidAdmin</role-name> > </auth-constraint> > > ... > <security-role> > <role-name>TeiidAdmin</role-name> > </security-role> > ~~~ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3482) Multi-source joins should still be partitioned even if not fully pushed

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3482?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3482. --------------------------------- > Multi-source joins should still be partitioned even if not fully pushed > ----------------------------------------------------------------------- > > Key: TEIID-3482 > URL: https://issues.jboss.org/browse/TEIID-3482 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > A deficiency in join planning with multi-source is that partitioning only occurs if the join is pushed. If not pushed then we'll union the results and process a join across all of the results. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3452) Better highlighting in the query plan when an identified possible issue is seen

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3452?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3452. --------------------------------- > Better highlighting in the query plan when an identified possible issue is seen > ------------------------------------------------------------------------------- > > Key: TEIID-3452 > URL: https://issues.jboss.org/browse/TEIID-3452 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 8.11 > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 8.11 > > > Looking a query plan that's printed in the server log, I see the following line: > "LOW Relational Planner Negation is not supported by source People - People.Person.id < 2 was not pushed" > Can the words "LOW Relational Planner Negation" be rephrased? > The word "LOW" used in the context of the criteria not being pushed down would seem to me to be a possible CRITICAL issue to performance. And I'm not sure most users will claim to know what Relational Planner Negation means and what its implying on an error message. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3476) Order by on query with union or union all orders parts independently

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3476?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3476. --------------------------------- > Order by on query with union or union all orders parts independently > -------------------------------------------------------------------- > > Key: TEIID-3476 > URL: https://issues.jboss.org/browse/TEIID-3476 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Fix For: 8.11 > > Attachments: debugplan_orderbyproblem.txt > > > I have this query that consists of a UNION ALL of 2 select queries that have a group by statement. I'd like to sort the whole result on the column aliased admtime. However this results in an IndexOutOfBoundsException. > select gd.patientid as admissionid,gd.PatGroup as patgroup,wr.Abbreviation as ward,gd.AdmissionTime as admtime, dd.DischargeTime as distime, 'wh' as origin > from wh_P_GeneralData gd > join wh_P_DischargeData dd on gd.patientid = dd.patientid > join prod_S_WardRef wr on wr.WardID = gd.WardID > where gd.patientid in ( > select patientid > from wh_P_PharmaRec pr > where pr.PharmaID = 1002463 and > bitand(pr.Status, 2) <> 2 > group by patientid > ) > group by gd.patientid,gd.PatGroup,wr.Abbreviation,gd.AdmissionTime, dd.DischargeTime > UNION ALL > select gd.patientid,gd.PatGroup,wr.Abbreviation,gd.AdmissionTime, dd.DischargeTime , 'prod' > from prod_P_GeneralData gd > join prod_P_DischargeData dd on gd.patientid = dd.patientid > join prod_S_WardRef wr on wr.WardID = gd.WardID > where gd.patientid in ( > select patientid > from prod_P_PharmaRec pr > where pr.PharmaID = 1002463 and > bitand(pr.Status, 2) <> 2 > group by patientid > ) > and gd.Status >= 4 and gd.status <> 5 > group by gd.patientid,gd.PatGroup,wr.Abbreviation,gd.AdmissionTime, dd.DischargeTime > order by admtime > java.lang.IndexOutOfBoundsException: Index: 6, Size: 6 > at java.util.ArrayList.rangeCheck(ArrayList.java:604) [rt.jar:1.7.0_25] > at java.util.ArrayList.get(ArrayList.java:382) [rt.jar:1.7.0_25] > at org.teiid.query.optimizer.relational.rules.NewCalculateCostUtil.setColStatEstimates(NewCalculateCostUtil.java:411) [teiid-engine-8.9.1.jar:8.9.1] > at org.teiid.query.optimizer.relational.rules.NewCalculateCostUtil.setCardinalityEstimate(NewCalculateCostUtil.java:313) [teiid-engine-8.9.1.jar:8.9.1] > at org.teiid.query.optimizer.relational.rules.NewCalculateCostUtil.estimateSetOpCost(NewCalculateCostUtil.java:252) [teiid-engine-8.9.1.jar:8.9.1] > at org.teiid.query.optimizer.relational.rules.NewCalculateCostUtil.computeNodeCost(NewCalculateCostUtil.java:204) [teiid-engine-8.9.1.jar:8.9.1] > at org.teiid.query.optimizer.relational.rules.NewCalculateCostUtil.updateCardinality(NewCalculateCostUtil.java:136) [teiid-engine-8.9.1.jar:8.9.1] > at org.teiid.query.optimizer.relational.rules.NewCalculateCostUtil.updateCardinality(NewCalculateCostUtil.java:133) [teiid-engine-8.9.1.jar:8.9.1] > at org.teiid.query.optimizer.relational.rules.NewCalculateCostUtil.updateCardinality(NewCalculateCostUtil.java:133) [teiid-engine-8.9.1.jar:8.9.1] > at org.teiid.query.optimizer.relational.rules.NewCalculateCostUtil.computeCostForTree(NewCalculateCostUtil.java:122) [teiid-engine-8.9.1.jar:8.9.1] > at org.teiid.query.optimizer.relational.rules.RuleCalculateCost.execute(RuleCalculateCost.java:50) [teiid-engine-8.9.1.jar:8.9.1] > at org.teiid.query.optimizer.relational.RelationalPlanner.executeRules(RelationalPlanner.java:739) [teiid-engine-8.9.1.jar:8.9.1] > at org.teiid.query.optimizer.relational.RelationalPlanner.optimize(RelationalPlanner.java:221) [teiid-engine-8.9.1.jar:8.9.1] > at org.teiid.query.optimizer.QueryOptimizer.optimizePlan(QueryOptimizer.java:159) [teiid-engine-8.9.1.jar:8.9.1] > at org.teiid.dqp.internal.process.Request.generatePlan(Request.java:411) [teiid-engine-8.9.1.jar:8.9.1] > at org.teiid.dqp.internal.process.Request.processRequest(Request.java:438) [teiid-engine-8.9.1.jar:8.9.1] > at org.teiid.dqp.internal.process.RequestWorkItem.processNew(RequestWorkItem.java:614) [teiid-engine-8.9.1.jar:8.9.1] > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:320) [teiid-engine-8.9.1.jar:8.9.1] > at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) [teiid-engine-8.9.1.jar:8.9.1] > at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:259) [teiid-engine-8.9.1.jar:8.9.1] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.9.1.jar:8.9.1] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.9.1.jar:8.9.1] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.9.1.jar:8.9.1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > I then changed the query to this form: > select * > from ( > previous query > ) v > order by admtime > In this case there is no error but the ordering seemed to have happened for each part of the select statement independently. So the collection of columns with origin 'prod' is sorted and the collection of rows with 'wh' as origin are sorted independently and then unioned toghether. > I've attached the debug log -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3166) Allow allowDiskUse setting in MongoDB translator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3166?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3166. --------------------------------- > Allow allowDiskUse setting in MongoDB translator > ------------------------------------------------ > > Key: TEIID-3166 > URL: https://issues.jboss.org/browse/TEIID-3166 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Harrison Gentry > Assignee: Ramesh Reddy > Priority: Minor > Labels: CR1 > Fix For: 8.9, 8.11 > > > When querying a MongoDB, steps of computation are limited to 100MiB. Querying large databases can easily exceed this limit, so usually allowDiskUse:true is passed in the aggregate query: > http://docs.mongodb.org/manual/reference/command/aggregate/ > In Teiid, however, there is currently no way to specify this with SQL. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3479) Typo in SecurityHelper method neogitiateGssLogin

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3479?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3479. --------------------------------- > Typo in SecurityHelper method neogitiateGssLogin > ------------------------------------------------ > > Key: TEIID-3479 > URL: https://issues.jboss.org/browse/TEIID-3479 > Project: Teiid > Issue Type: Bug > Components: Embedded > Affects Versions: 8.11 > Reporter: Jaime Meritt > Assignee: Steven Hawkins > Priority: Trivial > Fix For: 8.11 > > > There is a typo in the new method neogitiateGssLogin in the SecurityHelper interface. Definitely a nit but good to fix before GA and it proliferates -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3102) Provide a facility to restrict OData access to defined VDB

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3102?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3102. --------------------------------- > Provide a facility to restrict OData access to defined VDB > ----------------------------------------------------------- > > Key: TEIID-3102 > URL: https://issues.jboss.org/browse/TEIID-3102 > Project: Teiid > Issue Type: Enhancement > Components: OData > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Beta1 > Fix For: 8.7.1, 8.9 > > > The current OData interface in the Teiid provides one context for the web-application, thus restricting additional security/per VDB. > The alternative proposed is restrict the current web-app to single VDB, then provide a mechanism to alter the context and any necessary security domain stuff. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3469) Incorrect DDL Schema when importing from Teiid Data Source Connection using Informix translator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3469?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3469. --------------------------------- > Incorrect DDL Schema when importing from Teiid Data Source Connection using Informix translator > ----------------------------------------------------------------------------------------------- > > Key: TEIID-3469 > URL: https://issues.jboss.org/browse/TEIID-3469 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.0 > Reporter: Bruno Machado > Assignee: Steven Hawkins > Priority: Minor > Labels: ddl, designer, informix, schema, teiid > Fix For: 8.11 > > > When importing from Teiid Data Source Connection using an Informix Translator, an incorrect schema DDL is set as "catalog"."schema"."table-name" instead of "catalog":"schema"."table-name", the delimiter between catalog and schema is set to '.' but Informix uses ':'. > The '.' character must be replaced by a ':' between catalog and schema name when importing from Teiid Data Source Connection using Informix translator. > useCatalogName attribute could be set to false as a workaround to this and ignore the occurance of "catalog". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3371) Upgrade Teiid with EAP 6.4 Alpha

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3371?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3371. --------------------------------- > Upgrade Teiid with EAP 6.4 Alpha > -------------------------------- > > Key: TEIID-3371 > URL: https://issues.jboss.org/browse/TEIID-3371 > Project: Teiid > Issue Type: Enhancement > Components: Build/Kits > Affects Versions: 8.11 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Labels: Beta2 > Fix For: 8.11 > > Attachments: diff.txt, status.txt > > > Upgrade all the Teiid projects to be built based on EAP 6.4 Alpha. Currently, this would align with jboss-integration-platform-bom 6.0.0.CR25 and EAP Alpha version 7.5.0.Final-redhat-17. Note, 7.5.0.Final-redhat-17 is the version in the EAP kit, but only CR25 bom is available. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2015