April 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2804) Aggregate empty filter too broad and may inappropriately filter results

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2804?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2804. --------------------------------- > Aggregate empty filter too broad and may inappropriately filter results > ----------------------------------------------------------------------- > > Key: TEIID-2804 > URL: https://issues.jboss.org/browse/TEIID-2804 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.3 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.4.2, 8.7 > > > This is a regression from TEIID-2253 which consolidated logic in RulePushAggregates to handle multi-source planning. It also inappropriately expanded an empty test (which should only be applied to grouping without a group by) to some cases with group by clauses and in an attempt to broaden pushdown support utilized is not null tests. However the is not null tests are not generally valid as the aggregate could be computed against all null values for example. Depending upon this situations this could result in invalid filtering of results. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2860) Nested query with a with clause projection issue

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2860?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2860. --------------------------------- > Nested query with a with clause projection issue > ------------------------------------------------ > > Key: TEIID-2860 > URL: https://issues.jboss.org/browse/TEIID-2860 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.7 > > > A view or inline view with a with clause is not projected properly, which can lead to serialization and other issues. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2857) Build Error with Teiid POM Dependency

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2857?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2857. --------------------------------- > Build Error with Teiid POM Dependency > ------------------------------------- > > Key: TEIID-2857 > URL: https://issues.jboss.org/browse/TEIID-2857 > Project: Teiid > Issue Type: Bug > Components: Embedded > Affects Versions: 8.6 > Reporter: Ivan Chan > Assignee: Steven Hawkins > Labels: teiid > Fix For: 8.7 > > > In the jboss public maven repository: > https://repository.jboss.org/nexus/content/groups/public > The teiid-parent-8.6.0.Final.pom file has two dependencies which look to be > Teiid build/configuration bugs. > These two issues are causing our source code build to fail. > The pom file is located here: > https://repository.jboss.org/nexus/content/groups/public/org/jboss/teiid/... > In this pom file there are two declared dependencies: > <version.org.jboss.integration-platform>6.0.0-SNAPSHOT</version.org.jboss.integration-platform> > <jbossas-version>7.2.0.Alpha1-redhat-4</jbossas-version> > <dependency> > <groupId>org.jboss.integration-platform</groupId> > <artifactId>jboss-integration-platform-bom</artifactId> > <version>${version.org.jboss.integration-platform}</version> > <scope>import</scope> > <type>pom</type> > </dependency> > <dependency> > <groupId>org.jboss.as</groupId> > <artifactId>jboss-as-parent</artifactId> > <version>${jbossas-version}</version> > <type>pom</type> > <scope>import</scope> > </dependency> > Here are the issues: > 1) Snapshot dependency existing in the 8.6.0-FINAL Release > - jboss-integration-platform-bom/6.0.0-SNAPSHOT > 2) Declared dependency does not exist in the repo repository.jboss.org > - jboss-as-parent/7.2.0.Alpha1-redhat-4 > - We see dependencies only for: > - 7.2.0.Alpha1-SNAPSHOT > - 7.2.0.Fina > I'm not sure why these dependencies are needed when pulling in the Teiid artifacts, but perhaps because the <scope> of > these dependencies is set to "import" (<scope>import</scope>) > Our usage of the repository.jboss.org is to have snapshots disabled. So that is why the 6.0.0-SNAPSHOT fails to be found. > For the 7.2.0.Alpha1-redhat-4 dependency, it does not exist in > repository.jboss.org so this also fails. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2854) bounded-queue-thread-pool silently drops tasks after the queue length is exceeded

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2854?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2854. --------------------------------- > bounded-queue-thread-pool silently drops tasks after the queue length is exceeded > --------------------------------------------------------------------------------- > > Key: TEIID-2854 > URL: https://issues.jboss.org/browse/TEIID-2854 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.5 > Environment: JBoss EAP 6.1.0 Alpha and Teiid 8.5 > Reporter: Rakesh Balguri > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.7 > > > The bounded-queue-thread-pool apparently needs a handoff executor configured otherwise it silently drops tasks after the queue length is exceeded. > See the discussion for more information. > https://community.jboss.org/thread/236744 -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2921) Allow the projection raising (or order pushing) logic to work with non-simple ordering expressions

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2921?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2921: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1087994 > Allow the projection raising (or order pushing) logic to work with non-simple ordering expressions > -------------------------------------------------------------------------------------------------- > > Key: TEIID-2921 > URL: https://issues.jboss.org/browse/TEIID-2921 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 7.7.8 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > Fix For: 8.8 > > > Current logic is written to only support simple ordering expressions. User desires the ability to use non-simple Order By statements (for example: including a case statement) -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2928) Allow for backwards compatibility with multiple security domains per transport

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2928: ------------------------------------- Summary: Allow for backwards compatibility with multiple security domains per transport Key: TEIID-2928 URL: https://issues.jboss.org/browse/TEIID-2928 Project: Teiid Issue Type: Quality Risk Components: Server Affects Versions: 8.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.7.1, 8.8 With TEIID-2863 the ability to assign multiple security domains per transport was removed in favor of a per vdb scheme. However we still need to have it in place for backwards compatibility. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2927) Guard against external entity resolving in OData Atom Feed

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2927?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2927: ---------------------------------- Fix Version/s: 8.7.1 (was: 8.7) Description: OData4j is responsible for parsing the Atom feed. StaxXMLFactoryProvider2 simply creates XMLInputFactories without any options, thus they will perform external entity resolving by default. An issue will need to be opened against OData4j. (was: if applications that expose RESTEasy XML endpoints, add the following snippet to their web.xml file to disable entity expansion in RESTEasy: <context-param> <param-name>resteasy.document.expand.entity.references</param-name> <param-value>false</param-value> </context-param> Note that this <context-param> setting has precedence over <init-param>, and will override a contrary setting in an <init-param> element. However this is not sufficient for OData as OData4j is responsible for parsing the Atom feed. StaxXMLFactoryProvider2 simply creates XMLInputFactories without any options, thus they will perform external entity resolving by default. An issue will need to be opened against OData4j. For SQL/XML, the XMLType input factory needs to disable external entity resolving (via experimentation just setting the relevant property doesn't always work, so like other projects we'll set an XMLResolver, which does work). ) Assignee: (was: Steven Hawkins) > Guard against external entity resolving in OData Atom Feed > ---------------------------------------------------------- > > Key: TEIID-2927 > URL: https://issues.jboss.org/browse/TEIID-2927 > Project: Teiid > Issue Type: Bug > Components: OData, Query Engine > Affects Versions: 7.7, 8.4 > Reporter: Van Halbert > Priority: Critical > Fix For: 8.7.1 > > > OData4j is responsible for parsing the Atom feed. StaxXMLFactoryProvider2 simply creates XMLInputFactories without any options, thus they will perform external entity resolving by default. An issue will need to be opened against OData4j. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2911) Guard against external entity resolving

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2911?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2911. ----------------------------------- Fix Version/s: (was: 8.4.2) Resolution: Partially Completed Marking as partial resolved for 8.7 since everything but the odata changes were checked in. > Guard against external entity resolving > --------------------------------------- > > Key: TEIID-2911 > URL: https://issues.jboss.org/browse/TEIID-2911 > Project: Teiid > Issue Type: Bug > Components: OData, Query Engine > Affects Versions: 7.7, 8.4 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.7 > > Attachments: org.odata4j.stax2.staximpl.StaxXMLFactoryProvider2.diff > > > if applications that expose RESTEasy XML endpoints, add the following snippet to their web.xml file to disable entity expansion in RESTEasy: > <context-param> > <param-name>resteasy.document.expand.entity.references</param-name> > <param-value>false</param-value> > </context-param> > Note that this <context-param> setting has precedence over <init-param>, and will override a contrary setting in an <init-param> element. > However this is not sufficient for OData as OData4j is responsible for parsing the Atom feed. StaxXMLFactoryProvider2 simply creates XMLInputFactories without any options, thus they will perform external entity resolving by default. An issue will need to be opened against OData4j. > For SQL/XML, the XMLType input factory needs to disable external entity resolving (via experimentation just setting the relevant property doesn't always work, so like other projects we'll set an XMLResolver, which does work). -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2927) Guard against external entity resolving in OData Atom Feed

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2927: ------------------------------------- Summary: Guard against external entity resolving in OData Atom Feed Key: TEIID-2927 URL: https://issues.jboss.org/browse/TEIID-2927 Project: Teiid Issue Type: Bug Components: OData, Query Engine Affects Versions: 7.7, 8.4 Reporter: Van Halbert Assignee: Steven Hawkins Priority: Critical Fix For: 8.7 if applications that expose RESTEasy XML endpoints, add the following snippet to their web.xml file to disable entity expansion in RESTEasy: <context-param> <param-name>resteasy.document.expand.entity.references</param-name> <param-value>false</param-value> </context-param> Note that this <context-param> setting has precedence over <init-param>, and will override a contrary setting in an <init-param> element. However this is not sufficient for OData as OData4j is responsible for parsing the Atom feed. StaxXMLFactoryProvider2 simply creates XMLInputFactories without any options, thus they will perform external entity resolving by default. An issue will need to be opened against OData4j. For SQL/XML, the XMLType input factory needs to disable external entity resolving (via experimentation just setting the relevant property doesn't always work, so like other projects we'll set an XMLResolver, which does work). -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2916) HIVE2: Teiid didn't translate the SQL correctly for numeric field

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2916?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2916: ---------------------------------- Fix Version/s: 8.7.1 Affects Version/s: 8.6 (was: 8.8) > HIVE2: Teiid didn't translate the SQL correctly for numeric field > ------------------------------------------------------------------ > > Key: TEIID-2916 > URL: https://issues.jboss.org/browse/TEIID-2916 > Project: Teiid > Issue Type: Sub-task > Components: Misc. Connectors > Affects Versions: 8.6 > Environment: HIVE2 with Teiid > Reporter: Ivan Chan > Labels: Teiid > Fix For: 8.7.1 > > > Teiid didn't translate the SQL correctly for numeric field. It uses identifier "decimal" in the SQL which is not supported by the driver. > Original Query: > select "store_sales", > "store_state", > "store_country" > from "Impala"."sales_new" > where "store_sales" between 1.5 and 10 > limit 1000 > After Translation (Teiid): > SELECT g_0.store_sales AS c_0, g_0.store_state AS c_ > 1, g_0.store_country AS c_2 FROM sales_new g_0 WHERE cast(g_0.store_sales AS > decimal) >= 1.5 AND cast(g_0.store_sales AS decimal) <= 10 LIMIT 1000 > "decimal" is not supported identifier in HIVE driver: > Encountered: IDENTIFIER > Expected: BIGINT, BOOLEAN, DATE, DATETIME, REAL, FLOAT, INTEGER, SMALLINT, > STRING, TIMESTAMP, TINYINT -- 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, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2014