[JBoss JIRA] (TEIID-2985) odbc script reader does not handle extra statement delimiters
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2985?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2985:
----------------------------------
Issue Type: Bug (was: Feature Request)
> odbc script reader does not handle extra statement delimiters
> -------------------------------------------------------------
>
> Key: TEIID-2985
> URL: https://issues.jboss.org/browse/TEIID-2985
> Project: Teiid
> Issue Type: Bug
> Components: ODBC
> Affects Versions: 7.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.7.1, 8.8
>
>
> If sent the block of statements:
> BEGIN;declare "SQL_CUR0x1e4ba50" cursor with hold for select * from pg_proc;;fetch 1 in "SQL_CUR0x1e4ba50"
> We'll stop processing at the extra ; after the declare.
> In older branches such as 7.7 we'll attempt to process an empty sql statement, which will throw an exception.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (TEIID-2984) MongoDB: Usage of function "mod()" in SQL query throws an exception
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-2984?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-2984:
-------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1104758
> MongoDB: Usage of function "mod()" in SQL query throws an exception
> -------------------------------------------------------------------
>
> Key: TEIID-2984
> URL: https://issues.jboss.org/browse/TEIID-2984
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.4.1
> Reporter: Filip Elias
> Assignee: Steven Hawkins
> Attachments: server.log
>
>
> Exception[1] is thrown when function modulo(mod) is used in SQL query.
> Sample query:
> SELECT LongNum, 11, MOD(LongNum, 11) FROM BQT1.SmallA ORDER BY LONGNUM
> Server log is in the attachment.
> [1] 16:36:59,645 ERROR [org.teiid.CONNECTOR] (Worker10_QueryProcessorQueue71) Connector worker process failed for atomic-request=hRCP8hHjrmZb.25.0.13: com.mongodb.CommandFailureException: { "serverUsed" : "localhost/127.0.0.1:27017" , "errmsg" : "exception: disallowed field type Array in object expression (at 'mod')" , "code" : 15992 , "ok" : 0.0}
> at com.mongodb.CommandResult.getException(CommandResult.java:71)
> at com.mongodb.CommandResult.throwOnError(CommandResult.java:110)
> at com.mongodb.DBCollection.aggregate(DBCollection.java:1308)
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (TEIID-2984) MongoDB: Usage of function "mod()" in SQL query throws an exception
by Filip Elias (JIRA)
[ https://issues.jboss.org/browse/TEIID-2984?page=com.atlassian.jira.plugin... ]
Filip Elias updated TEIID-2984:
-------------------------------
Attachment: server.log
> MongoDB: Usage of function "mod()" in SQL query throws an exception
> -------------------------------------------------------------------
>
> Key: TEIID-2984
> URL: https://issues.jboss.org/browse/TEIID-2984
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.4.1
> Reporter: Filip Elias
> Assignee: Steven Hawkins
> Attachments: server.log
>
>
> Exception[1] is thrown when function modulo(mod) is used in SQL query.
> Sample query:
> SELECT LongNum, 11, MOD(LongNum, 11) FROM BQT1.SmallA ORDER BY LONGNUM
> Server log is in the attachment.
> [1] 16:36:59,645 ERROR [org.teiid.CONNECTOR] (Worker10_QueryProcessorQueue71) Connector worker process failed for atomic-request=hRCP8hHjrmZb.25.0.13: com.mongodb.CommandFailureException: { "serverUsed" : "localhost/127.0.0.1:27017" , "errmsg" : "exception: disallowed field type Array in object expression (at 'mod')" , "code" : 15992 , "ok" : 0.0}
> at com.mongodb.CommandResult.getException(CommandResult.java:71)
> at com.mongodb.CommandResult.throwOnError(CommandResult.java:110)
> at com.mongodb.DBCollection.aggregate(DBCollection.java:1308)
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (TEIID-2984) MongoDB: Usage of function "mod()" in SQL query throws an exception
by Filip Elias (JIRA)
Filip Elias created TEIID-2984:
----------------------------------
Summary: MongoDB: Usage of function "mod()" in SQL query throws an exception
Key: TEIID-2984
URL: https://issues.jboss.org/browse/TEIID-2984
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 8.4.1
Reporter: Filip Elias
Assignee: Steven Hawkins
Exception[1] is thrown when function modulo(mod) is used in SQL query.
Sample query:
SELECT LongNum, 11, MOD(LongNum, 11) FROM BQT1.SmallA ORDER BY LONGNUM
Server log is in the attachment.
[1] 16:36:59,645 ERROR [org.teiid.CONNECTOR] (Worker10_QueryProcessorQueue71) Connector worker process failed for atomic-request=hRCP8hHjrmZb.25.0.13: com.mongodb.CommandFailureException: { "serverUsed" : "localhost/127.0.0.1:27017" , "errmsg" : "exception: disallowed field type Array in object expression (at 'mod')" , "code" : 15992 , "ok" : 0.0}
at com.mongodb.CommandResult.getException(CommandResult.java:71)
at com.mongodb.CommandResult.throwOnError(CommandResult.java:110)
at com.mongodb.DBCollection.aggregate(DBCollection.java:1308)
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (TEIID-2983) MongoDB: Function "count()" returns sum instead of number of rows
by Van Halbert (JIRA)
Van Halbert created TEIID-2983:
----------------------------------
Summary: MongoDB: Function "count()" returns sum instead of number of rows
Key: TEIID-2983
URL: https://issues.jboss.org/browse/TEIID-2983
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 8.7.1
Reporter: Van Halbert
Assignee: Steven Hawkins
Function "count()" returns sum of rows instead of number of rows
Query [1] returns sum of values of all rows of IntKey column.
Query [2] correctly returns number of rows
[1] SELECT COUNT(IntKey) FROM BQT1.SmallA
[2] SELECT COUNT(*) FROM BQT1.SmallA
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (TEIID-2982) Allow to change visibility to a model from imported vdb
by Kenichi Takemura (JIRA)
Kenichi Takemura created TEIID-2982:
---------------------------------------
Summary: Allow to change visibility to a model from imported vdb
Key: TEIID-2982
URL: https://issues.jboss.org/browse/TEIID-2982
Project: Teiid
Issue Type: Feature Request
Affects Versions: 8.7
Reporter: Kenichi Takemura
Assignee: Steven Hawkins
When a new vdb uses import-vdb, changing(override) visibility to a model from imported vdb would need to hide non-related model to the new vdb.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[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 commented on TEIID-2981:
---------------------------------------
Two things come to mind. The first is that it would be simple to expose a config property for the servlet to toggle the result set cache mode on the local connections - but this would lack fine grained controls.
The other is that procedure caching may be viable for you - https://docs.jboss.org/author/display/TEIID/Results+Caching but is currently limited to 256 cache entries per procedure. However that could be made a configurable option as well.
> 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, OData,
>
> 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.2.3#6260)
10 years, 7 months