March 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3782) OData V4: Support system options over the operation based collections

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3782?page=com.atlassian.jira.plugin... ] Work on TEIID-3782 started by Ramesh Reddy. ------------------------------------------- > OData V4: Support system options over the operation based collections > --------------------------------------------------------------------- > > Key: TEIID-3782 > URL: https://issues.jboss.org/browse/TEIID-3782 > Project: Teiid > Issue Type: Sub-task > Components: OData > Affects Versions: 8.11 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.12.x > > > Currently the system options like $top, $skip, $filter are not supported on results returned from Functions/Actions. Per OData specification this should be supported. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4090) Issue with entitysets/properties ending in auth or token

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4090?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4090: ------------------------------------- I am going to move these endpoints under different context, and adjust the "teiid-web-security" project accordingly. > Issue with entitysets/properties ending in auth or token > -------------------------------------------------------- > > Key: TEIID-4090 > URL: https://issues.jboss.org/browse/TEIID-4090 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.12 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 9.0, 8.12.5 > > > To handle oauth, we are check for uri.endsWith("auth") || uri.endsWith("token") - however valid uris can end with those characters as well. An ioexception will be thrown instead of seeing the expected results - we also need to not simply throw an ioexception in ODataServlet as there is no server log of the exception and the client sees a 500 error. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4090) Issue with entitysets/properties ending in auth or token

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4090?page=com.atlassian.jira.plugin... ] Work on TEIID-4090 started by Ramesh Reddy. ------------------------------------------- > Issue with entitysets/properties ending in auth or token > -------------------------------------------------------- > > Key: TEIID-4090 > URL: https://issues.jboss.org/browse/TEIID-4090 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.12 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 9.0, 8.12.5 > > > To handle oauth, we are check for uri.endsWith("auth") || uri.endsWith("token") - however valid uris can end with those characters as well. An ioexception will be thrown instead of seeing the expected results - we also need to not simply throw an ioexception in ODataServlet as there is no server log of the exception and the client sees a 500 error. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3962) remove invalid character handling from Teiid odata4 logic

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3962?page=com.atlassian.jira.plugin... ] Work on TEIID-3962 started by Ramesh Reddy. ------------------------------------------- > remove invalid character handling from Teiid odata4 logic > --------------------------------------------------------- > > Key: TEIID-3962 > URL: https://issues.jboss.org/browse/TEIID-3962 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > > Since we now have a better influence over the odata framework, we should remove the replacement character logic from Teiid and let that be handled by the serializers - as the current handling is intended for XML but will affect both JSON and XML results. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4107) HSQL Syntax error when Teiid sends it a join query with no parenthesis

by Gabriel Steinberg (JIRA)

Gabriel Steinberg created TEIID-4107: ---------------------------------------- Summary: HSQL Syntax error when Teiid sends it a join query with no parenthesis Key: TEIID-4107 URL: https://issues.jboss.org/browse/TEIID-4107 Project: Teiid Issue Type: Feature Request Components: JDBC Connector Reporter: Gabriel Steinberg Assignee: Steven Hawkins The query SELECT R_NAME FROM region LEFT OUTER JOIN (customer INNER JOIN nation ON C_NATIONKEY = N_NATIONKEY) ON R_REGIONKEY = N_REGIONKEY When run against an HSQL DB causes a syntax error because the query passed to HSQL contains no parenthesis, and HSQL cannot handle it, as described in https://developer.jboss.org/message/953580?et=watches.email.thread#953580. As Steve points out there, this was solved for H2 in https://issues.jboss.org/browse/TEIID-3549. H2 and HSQL come from the same project, they split at some point in time, and I suspect they still share a lot of code. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3480) External Materialization status

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3480?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3480: --------------------------------------- I don't think we do want a status table for external. It would be better to have a status procedure (see the first comment). We have a table for the internal since we directly control all of that state. As for bringing internal/external closer together that has incrementally been addressed with respect to to some of the management functionality and extension metadata - but still needs to be done for the system procedures. If we have single status procedure to cover both internal and external that would be a good start. > External Materialization status > ------------------------------- > > Key: TEIID-3480 > URL: https://issues.jboss.org/browse/TEIID-3480 > Project: Teiid > Issue Type: Enhancement > Components: Server > Affects Versions: 8.4 > Reporter: Ramesh Reddy > Assignee: Kylin Soong > Fix For: 9.0 > > > When external materialization is configured with "STATUS" table, then Teiid should expose those stats over CLI and in the web-console. Currently the internal materialization does show status, need to expand to the external matviews. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

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

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3878?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3878: --------------------------------------- Have you been able to revisit this on a later 9.0 or 8.13? If possible could you provide a reproducing vdb as I couldn't seem to quite get there. > 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 > Fix For: 9.0 > > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4106) Rename and align infinispan translators/resource-adapters for their purpose

by Van Halbert (JIRA)

Van Halbert created TEIID-4106: ---------------------------------- Summary: Rename and align infinispan translators/resource-adapters for their purpose Key: TEIID-4106 URL: https://issues.jboss.org/browse/TEIID-4106 Project: Teiid Issue Type: Enhancement Components: Misc. Connectors Affects Versions: 9.x Reporter: Van Halbert Assignee: Steven Hawkins The infinispan-cache and infinispan-cache-dsl translators need to be renamed and aligned for what their purpose is. Because using "dsl" as part of the name is confusing, because both translators now support querying using JDG DSL language. infinispan-cache: - rename to infinispan-cache-library-mode (or leave as infinispan-cache and it be assume library mode) - deprecate the access to remote-cache because the other infinispan-cache-dsl translator provides this feature. - this will enable the cleaning of the documentation to be specific to library mode infinispan-cache-dsl: - rename to infinispan-cache-hot-rod (or something other than "dsl") because this all about remote cache access using hot rod client -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4106) Rename and align infinispan translators/resource-adapters for their purpose

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4106?page=com.atlassian.jira.plugin... ] Van Halbert reassigned TEIID-4106: ---------------------------------- Assignee: Van Halbert (was: Steven Hawkins) > Rename and align infinispan translators/resource-adapters for their purpose > ---------------------------------------------------------------------------- > > Key: TEIID-4106 > URL: https://issues.jboss.org/browse/TEIID-4106 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Van Halbert > > The infinispan-cache and infinispan-cache-dsl translators need to be renamed and aligned for what their purpose is. Because using "dsl" as part of the name is confusing, because both translators now support querying using JDG DSL language. > infinispan-cache: > - rename to infinispan-cache-library-mode (or leave as infinispan-cache and it be assume library mode) > - deprecate the access to remote-cache because the other infinispan-cache-dsl translator provides this feature. > - this will enable the cleaning of the documentation to be specific to library mode > infinispan-cache-dsl: > - rename to infinispan-cache-hot-rod (or something other than "dsl") because this all about remote cache access using hot rod client -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4106) Rename and align infinispan translators/resource-adapters for their purpose

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4106?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4106: ------------------------------- Description: The infinispan-cache and infinispan-cache-dsl translators/resource-adapters need to be renamed and aligned for what their purpose is. Because using "dsl" as part of the name is confusing, because both translators now support querying using JDG DSL language. infinispan-cache: - rename to infinispan-cache-library-mode (or leave as infinispan-cache and it be assume library mode) - deprecate the access to remote-cache because the other infinispan-cache-dsl translator provides this feature. - this will enable the cleaning of the documentation to be specific to library mode infinispan-cache-dsl: - rename to infinispan-cache-hot-rod (or something other than "dsl") because this all about remote cache access using hot rod client was: The infinispan-cache and infinispan-cache-dsl translators need to be renamed and aligned for what their purpose is. Because using "dsl" as part of the name is confusing, because both translators now support querying using JDG DSL language. infinispan-cache: - rename to infinispan-cache-library-mode (or leave as infinispan-cache and it be assume library mode) - deprecate the access to remote-cache because the other infinispan-cache-dsl translator provides this feature. - this will enable the cleaning of the documentation to be specific to library mode infinispan-cache-dsl: - rename to infinispan-cache-hot-rod (or something other than "dsl") because this all about remote cache access using hot rod client > Rename and align infinispan translators/resource-adapters for their purpose > ---------------------------------------------------------------------------- > > Key: TEIID-4106 > URL: https://issues.jboss.org/browse/TEIID-4106 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Van Halbert > > The infinispan-cache and infinispan-cache-dsl translators/resource-adapters need to be renamed and aligned for what their purpose is. Because using "dsl" as part of the name is confusing, because both translators now support querying using JDG DSL language. > infinispan-cache: > - rename to infinispan-cache-library-mode (or leave as infinispan-cache and it be assume library mode) > - deprecate the access to remote-cache because the other infinispan-cache-dsl translator provides this feature. > - this will enable the cleaning of the documentation to be specific to library mode > infinispan-cache-dsl: > - rename to infinispan-cache-hot-rod (or something other than "dsl") because this all about remote cache access using hot rod client -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2016