[JBoss JIRA] (TEIID-2981) Add an OData query parameter that caches the resultset
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2981?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2981.
---------------------------------
> Add an OData query parameter that caches the resultset
> ------------------------------------------------------
>
> Key: TEIID-2981
> URL: https://issues.jboss.org/browse/TEIID-2981
> Project: Teiid
> Issue Type: Feature Request
> Components: OData
> Affects Versions: 8.7
> Reporter: John Muller
> Assignee: Steven Hawkins
> Priority: Minor
> Labels: Caching
> Fix For: 8.8
>
>
> The Teiid caching guide indicates that the /*+ cache */ SQL hint is neccessary in order to cache results [1] . We would like two features added to the OData support: (1) to have a query parameter that basically injects the hint into the SQL statement run against the VDB and (2) a configuration setting that turns on OData resultset caching for all result sets smaller than some size (perhaps 256 as the default)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months
[JBoss JIRA] (TEIID-2960) Class cast exception with source batched update command
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2960?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2960.
---------------------------------
> Class cast exception with source batched update command
> -------------------------------------------------------
>
> Key: TEIID-2960
> URL: https://issues.jboss.org/browse/TEIID-2960
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.8, 8.7.1
>
>
> A source batched update command will cause:
> Caused by: java.lang.ClassCastException: org.teiid.query.sql.lang.BatchedUpdateCommand cannot be cast to org.teiid.query.sql.lang.ProcedureContainer
> at org.teiid.dqp.internal.process.DataTierTupleSource.checkForUpdates(DataTierTupleSource.java:223)
> at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:148
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months
[JBoss JIRA] (TEIID-994) Unable to execute Oracle pipelined table function as procedure
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-994?page=com.atlassian.jira.plugin.... ]
Steven Hawkins closed TEIID-994.
--------------------------------
> Unable to execute Oracle pipelined table function as procedure
> --------------------------------------------------------------
>
> Key: TEIID-994
> URL: https://issues.jboss.org/browse/TEIID-994
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors, Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
>
> Oracle pipelined table functions (can be used in Oracle queries as TABLE(...)) that can be put in the FROM clause and used as if they were tables although they are really procedures. We found that we imported this table function, although didn't get it quite right - the result set was wrong, which may just be a deficiency of the JDBC import metadata. We were able to map the proc to a table and execute but when we did we got a PL/SQL error from the db.
> Because this is a proc, we are executing it as a CallableStatement down in the JDBC connector which apparently does not work with DataDirect. I'm not sure how we can detect and do something different but seems like we need to have some metadata (procedure name in source?) that can tell us that this proc needs to be run differently and have the Oracle JDBC Connector deal with this properly.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months
[JBoss JIRA] (TEIID-2919) BigInteger and BigDecimal datatypes are converted into string in MongoDB translator
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2919?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2919.
---------------------------------
> BigInteger and BigDecimal datatypes are converted into string in MongoDB translator
> -------------------------------------------------------------------------------------
>
> Key: TEIID-2919
> URL: https://issues.jboss.org/browse/TEIID-2919
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.4
> Reporter: Filip Elias
> Assignee: Steven Hawkins
> Fix For: 8.8, 8.7.1
>
>
> Description of problem:
> BigInteger and BigDecimal datatypes are converted into string in MongoDB translator (MongoDBExecutionFactory.java). User can't use these datatypes in the WHERE clause.
> For example
> The query:
>
> SELECT IntKey FROM SmallA where BIGINTEGERVALUE > 1
> returns no results because BIGINTEGERVALUE > 1 is converted into
> { "BIGINTEGERVALUE" : { "$gt" : "1"}}
> but is should be
> { "BIGINTEGERVALUE" : { "$gt" : 1}}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months
[JBoss JIRA] (TEIID-3092) error with xml project minimization
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3092?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3092.
---------------------------------
> error with xml project minimization
> -----------------------------------
>
> Key: TEIID-3092
> URL: https://issues.jboss.org/browse/TEIID-3092
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.7.1, 8.9
>
>
> The project minimization logic will not look at the appropriate parent chain for each binding and can result in dropping columns that are used from the query which would be seen at runtime as a value not available from context exception. This became apparent with TEIID-3081 where the map order changed in different vms.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months