January 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3909) Add support for odata geospatial handling

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3909?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3909: --------------------------------------- Are you sure? All the classes are there. > Add support for odata geospatial handling > ----------------------------------------- > > Key: TEIID-3909 > URL: https://issues.jboss.org/browse/TEIID-3909 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > We should use the Edm.Geometry type for the Teiid geometry type (we can also use system metadata to see if it's appropriate to use a geometry subtype) along with any geospatial operations that odata and Teiid support. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3909) Add support for odata geospatial handling

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3909?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3909: ------------------------------------- Geo types are not supported by Olingo framework either. We need to do the contribution, if want to want head that way. > Add support for odata geospatial handling > ----------------------------------------- > > Key: TEIID-3909 > URL: https://issues.jboss.org/browse/TEIID-3909 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > We should use the Edm.Geometry type for the Teiid geometry type (we can also use system metadata to see if it's appropriate to use a geometry subtype) along with any geospatial operations that odata and Teiid support. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3909) Add support for odata geospatial handling

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3909?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3909: --------------------------------------- It looks like I'll restrict this initially to consuming odata4. Producing isn't an easy change until we expand our type model or odata allows for a functional generic type. Also the text format is ewkt compatible - just with geometry prepended. > Add support for odata geospatial handling > ----------------------------------------- > > Key: TEIID-3909 > URL: https://issues.jboss.org/browse/TEIID-3909 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > We should use the Edm.Geometry type for the Teiid geometry type (we can also use system metadata to see if it's appropriate to use a geometry subtype) along with any geospatial operations that odata and Teiid support. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3919) Add support for using Security mapping modules in security domain for teiid

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3919?page=com.atlassian.jira.plugin... ] Van Halbert reassigned TEIID-3919: ---------------------------------- Assignee: Steven Hawkins (was: Van Halbert) > Add support for using Security mapping modules in security domain for teiid > --------------------------------------------------------------------------- > > Key: TEIID-3919 > URL: https://issues.jboss.org/browse/TEIID-3919 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > Currently we only use the RoleMapping login module for role mapping in the teiid security domain. Can we have the code call the mapping module as well - https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-appli... > See https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-appli... for the full list of available mapping modules. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3920) Remove databasetimezone property from odata4 translator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3920?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3920: ---------------------------------- Description: The databasetimezone execution property is not used - and not needed since all date/time information needs to be in gmt or with an explicit timezone. This is a candidate for 8.12.5 as well. was: The databasetimezone execution property is not used - and not needed since all date/time information needs to be in gmt. This is a candidate for 8.12.5 as well. After looking at the source though, I'm not so sure about this. EdmDate and EdmTimeOfDay both assume GMT for incoming string values - however when the convert from Java objects to string they use the local/default Calendar. This seems like it could be a bug since it is asymmetric behavior. I can't find any spec reference on this either. > Remove databasetimezone property from odata4 translator > ------------------------------------------------------- > > Key: TEIID-3920 > URL: https://issues.jboss.org/browse/TEIID-3920 > Project: Teiid > Issue Type: Quality Risk > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.13 > > > The databasetimezone execution property is not used - and not needed since all date/time information needs to be in gmt or with an explicit timezone. > This is a candidate for 8.12.5 as well. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3920) Remove databasetimezone property from odata4 translator

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3920: ------------------------------------- Summary: Remove databasetimezone property from odata4 translator Key: TEIID-3920 URL: https://issues.jboss.org/browse/TEIID-3920 Project: Teiid Issue Type: Quality Risk Components: Misc. Connectors Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.13 The databasetimezone execution property is not used - and not needed since all date/time information needs to be in gmt. This is a candidate for 8.12.5 as well. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3919) Add support for using Security mapping modules in security domain for teiid

by Debbie Steigner (JIRA)

[ https://issues.jboss.org/browse/TEIID-3919?page=com.atlassian.jira.plugin... ] Debbie Steigner moved JBDVPL-306 to TEIID-3919: ----------------------------------------------- Project: Teiid (was: JBoss DV Planning) Key: TEIID-3919 (was: JBDVPL-306) Issue Type: Feature Request (was: Requirement) Workflow: classic default workflow (was: CDW v1) Component/s: Server (was: Security) > Add support for using Security mapping modules in security domain for teiid > --------------------------------------------------------------------------- > > Key: TEIID-3919 > URL: https://issues.jboss.org/browse/TEIID-3919 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Debbie Steigner > Assignee: Van Halbert > > Currently we only use the RoleMapping login module for role mapping in the teiid security domain. Can we have the code call the mapping module as well - https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-appli... > See https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-appli... for the full list of available mapping modules. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3917) Allow partial projection of window functions

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3917?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3917. ----------------------------------- Resolution: Done Added support with check prior to the creation of the processing plan node to filter expressions that have already been pushed. > Allow partial projection of window functions > -------------------------------------------- > > Key: TEIID-3917 > URL: https://issues.jboss.org/browse/TEIID-3917 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > Currently the pushProjection check in RuleAssignOutputElements does not consider projected columns from a node that has window functions. This should be relaxed so that more can be pushed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3878) java.lang.Integer cannot be cast to java.math.BigDecimal

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3878?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3878: ------------------------------------- You either use * web-console and go the models tab, and click the DDL on the model. * using the AdminShell, you can issue "getSchema" call to get DDL > java.lang.Integer cannot be cast to java.math.BigDecimal > -------------------------------------------------------- > > Key: TEIID-3878 > URL: https://issues.jboss.org/browse/TEIID-3878 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.11.3 > Reporter: Mark Tawk > Assignee: Steven Hawkins > Priority: Critical > Attachments: TEIID-3878.sql > > > I'm using Teiid 8.11.3 with oracle translator. > I have an aggregated query using teiid materialized views with the following simplified criteria: > (CASE WHEN ( "table1"."field1" = 1 ) THEN "table2"."yearfield" ELSE null END IN (2014) ) > The above criteria is reproducing a ClassCastException Integer cannot be cast to BigDecimal > if I change the criteria to the following, it passes without a problem: > ("table2"."yearfield" IN (2014) ) > Here is the error stack: > java.lang.ClassCastException: java.lang.Integer cannot be cast to java.math.BigDecimal > at java.math.BigDecimal.compareTo(BigDecimal.java:219) > at org.teiid.query.sql.symbol.Constant$2.compare(Constant.java:99) > at org.teiid.query.eval.Evaluator.compare(Evaluator.java:581) > at org.teiid.query.eval.Evaluator.evaluate(Evaluator.java:322) > at org.teiid.query.eval.Evaluator.internalEvaluateTVL(Evaluator.java:236) > at org.teiid.query.eval.Evaluator.evaluateTVL(Evaluator.java:225) > at org.teiid.query.eval.Evaluator.evaluate(Evaluator.java:219) > at org.teiid.query.processor.relational.JoinNode.matchesCriteria(JoinNode.java:353) > at org.teiid.query.processor.relational.EnhancedSortMergeJoinStrategy.process(EnhancedSortMergeJoinStrategy.java:460) > at org.teiid.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:227) > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) > at org.teiid.query.processor.BatchCollector$BatchProducerTupleSource.nextTuple(BatchCollector.java:94) > at org.teiid.query.processor.relational.GroupingNode.groupSortPhase(GroupingNode.java:490) > at org.teiid.query.processor.relational.GroupingNode.nextBatchDirect(GroupingNode.java:366) > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) > at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:148) > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) > at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:145) > at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151) > at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146) > at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:457) > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:339) > at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) > at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:267) > at org.teiid.dqp.internal.process.DQPCore.executeRequest(DQPCore.java:306) > at org.teiid.dqp.internal.process.DQPCore.executeRequest(DQPCore.java:238) > at sun.reflect.GeneratedMethodAccessor260.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.teiid.transport.LocalServerConnection$1$1.call(LocalServerConnection.java:175) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:260) > at org.teiid.transport.LocalServerConnection$1.invoke(LocalServerConnection.java:173) > at com.sun.proxy.$Proxy31.executeRequest(Unknown Source) > at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:667) > at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:533) > at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:1068) > at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:320) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3878) java.lang.Integer cannot be cast to java.math.BigDecimal

by Mark Tawk (JIRA)

[ https://issues.jboss.org/browse/TEIID-3878?page=com.atlassian.jira.plugin... ] Mark Tawk commented on TEIID-3878: ---------------------------------- I guess the problem is related to the materialized view CEProductdetailsView. Because i tried to connect via a new model to the 3 tables and the same query executes without a problem. Can you please tell me the way to get the Teiid DDL of the view and its tables? > java.lang.Integer cannot be cast to java.math.BigDecimal > -------------------------------------------------------- > > Key: TEIID-3878 > URL: https://issues.jboss.org/browse/TEIID-3878 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.11.3 > Reporter: Mark Tawk > Assignee: Steven Hawkins > Priority: Critical > Attachments: TEIID-3878.sql > > > I'm using Teiid 8.11.3 with oracle translator. > I have an aggregated query using teiid materialized views with the following simplified criteria: > (CASE WHEN ( "table1"."field1" = 1 ) THEN "table2"."yearfield" ELSE null END IN (2014) ) > The above criteria is reproducing a ClassCastException Integer cannot be cast to BigDecimal > if I change the criteria to the following, it passes without a problem: > ("table2"."yearfield" IN (2014) ) > Here is the error stack: > java.lang.ClassCastException: java.lang.Integer cannot be cast to java.math.BigDecimal > at java.math.BigDecimal.compareTo(BigDecimal.java:219) > at org.teiid.query.sql.symbol.Constant$2.compare(Constant.java:99) > at org.teiid.query.eval.Evaluator.compare(Evaluator.java:581) > at org.teiid.query.eval.Evaluator.evaluate(Evaluator.java:322) > at org.teiid.query.eval.Evaluator.internalEvaluateTVL(Evaluator.java:236) > at org.teiid.query.eval.Evaluator.evaluateTVL(Evaluator.java:225) > at org.teiid.query.eval.Evaluator.evaluate(Evaluator.java:219) > at org.teiid.query.processor.relational.JoinNode.matchesCriteria(JoinNode.java:353) > at org.teiid.query.processor.relational.EnhancedSortMergeJoinStrategy.process(EnhancedSortMergeJoinStrategy.java:460) > at org.teiid.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:227) > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) > at org.teiid.query.processor.BatchCollector$BatchProducerTupleSource.nextTuple(BatchCollector.java:94) > at org.teiid.query.processor.relational.GroupingNode.groupSortPhase(GroupingNode.java:490) > at org.teiid.query.processor.relational.GroupingNode.nextBatchDirect(GroupingNode.java:366) > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) > at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:148) > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) > at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:145) > at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151) > at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146) > at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:457) > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:339) > at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) > at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:267) > at org.teiid.dqp.internal.process.DQPCore.executeRequest(DQPCore.java:306) > at org.teiid.dqp.internal.process.DQPCore.executeRequest(DQPCore.java:238) > at sun.reflect.GeneratedMethodAccessor260.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.teiid.transport.LocalServerConnection$1$1.call(LocalServerConnection.java:175) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:260) > at org.teiid.transport.LocalServerConnection$1.invoke(LocalServerConnection.java:173) > at com.sun.proxy.$Proxy31.executeRequest(Unknown Source) > at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:667) > at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:533) > at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:1068) > at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:320) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2016