[JBoss JIRA] (TEIID-2988) MongoDB: Function substring - starting index and number of arguments
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-2988?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-2988:
------------------------------------------------
Filip Elias <felias(a)redhat.com> changed the Status of [bug 1105101|https://bugzilla.redhat.com/show_bug.cgi?id=1105101] from MODIFIED to ASSIGNED
> MongoDB: Function substring - starting index and number of arguments
> --------------------------------------------------------------------
>
> Key: TEIID-2988
> URL: https://issues.jboss.org/browse/TEIID-2988
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.4.1
> Reporter: Filip Elias
> Assignee: Ramesh Reddy
> Labels: Beta1
> Fix For: 8.8, 8.7.1
>
>
> Two minor bugs in function substring()
> Mongo's function $substr takes only 3 arguments so this query fails:
> {code}
> SELECT intkey, SUBSTRING(BQT1.SmallA.stringkey, 1) FROM BQT1.SmallA ORDER BY intkey
> {code}
> {code}
> Exception:13:18:48,220 ERROR [org.teiid.CONNECTOR] (Worker38_QueryProcessorQueue345) Connector worker process failed for atomic-request=omsmHP0o16Sa.40.0.86: com.mongodb.CommandFailureException: { "serverUsed" : "localhost/127.0.0.1:27017" , "errmsg" : "exception: the $substr operator requires 3 operand(s)" , "code" : 16020 , "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)
> {code}
> Generated mongo command:
> {code}
> { aggregate: "smalla", pipeline: [ { $project: { c_0: "$INTKEY", c_1: { $substr: [ "$STRINGKEY", 1 ] } } }, { $sort: { c_0: 1 } } ] }
> {code}
> Mongo's $substr function second argument represents number of bytes to skip, not the starting index. The function substring(StringKey,1,1) returns the second letter, but it should return the first letter.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 7 months
[JBoss JIRA] (TEIID-3229) Inappropriate pushdown of a must pushdown function
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3229?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3229.
-----------------------------------
Resolution: Done
Added a check to make sure there is no intervening grouping node.
> Inappropriate pushdown of a must pushdown function
> --------------------------------------------------
>
> Key: TEIID-3229
> URL: https://issues.jboss.org/browse/TEIID-3229
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.6
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.7.1, 8.10
>
>
> If a must push down function is used over a grouping that is not pushed, then an invalid symbol will be created and cause an invalid source query and or a class cast exception.
> For example:
> select some_funct(c1) from tbl group by c1
> where the translator does not support grouping.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 7 months
[JBoss JIRA] (TEIID-991) Request for support of Sybase IQ as a supported data source
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-991?page=com.atlassian.jira.plugin.... ]
Steven Hawkins resolved TEIID-991.
----------------------------------
Assignee: Steven Hawkins
Fix Version/s: (was: Open To Community)
Resolution: Done
Added the initial form of the sybase iq translator (which could be applicable to sqlanywhere as well, but those version numbers are different). Added a release not and updated the docs.
> Request for support of Sybase IQ as a supported data source
> -----------------------------------------------------------
>
> Key: TEIID-991
> URL: https://issues.jboss.org/browse/TEIID-991
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Reporter: Marc Shirley
> Assignee: Steven Hawkins
> Fix For: 8.10
>
>
> Per client:
> We'd like the ability to have a built-in connector type for Sybase IQ,
> just the same as Sybase ASE We have been getting inquiries and we've
> had to decline one project because we didn't support Sybase IQ out of
> the box. We foresee that Sybase IQ will be getting some play within
> important Data Warehouses and Data Marts within the firm.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 7 months
[JBoss JIRA] (TEIID-3230) Sybase translator changes
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3230:
-------------------------------------
Summary: Sybase translator changes
Key: TEIID-3230
URL: https://issues.jboss.org/browse/TEIID-3230
Project: Teiid
Issue Type: Quality Risk
Components: Misc. Connectors
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.10
The logic for supporting date formats is in the code, but not exposed via a capability. Also the type mapping in the translator should account for when time is supported as a type.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 7 months
[JBoss JIRA] (TEIID-3229) Inappropriate pushdown of a must pushdown function
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3229:
-------------------------------------
Summary: Inappropriate pushdown of a must pushdown function
Key: TEIID-3229
URL: https://issues.jboss.org/browse/TEIID-3229
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.6
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.7.1, 8.10
If a must push down function is used over a grouping that is not pushed, then an invalid symbol will be created and cause an invalid source query and or a class cast exception.
For example:
select some_funct(c1) from tbl group by c1
where the translator does not support grouping.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 7 months
[JBoss JIRA] (TEIID-3229) Inappropriate pushdown of a must pushdown function
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3229?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3229:
----------------------------------
Issue Type: Bug (was: Feature Request)
> Inappropriate pushdown of a must pushdown function
> --------------------------------------------------
>
> Key: TEIID-3229
> URL: https://issues.jboss.org/browse/TEIID-3229
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.6
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.7.1, 8.10
>
>
> If a must push down function is used over a grouping that is not pushed, then an invalid symbol will be created and cause an invalid source query and or a class cast exception.
> For example:
> select some_funct(c1) from tbl group by c1
> where the translator does not support grouping.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 7 months
[JBoss JIRA] (TEIID-3228) SOLR: Date and Timestamp parsing is incorrect
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3228?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-3228.
---------------------------------
Labels: Alpaha1 (was: )
Fix Version/s: 8.7.1
8.10
Resolution: Done
The code is fixed to account "dd" instead of "DD". Unfortunately there was test case for this, but it was testing for Jan 06, which is 6th day of the year no matter how you were looking at it. Fixed the testcase too.
> SOLR: Date and Timestamp parsing is incorrect
> ---------------------------------------------
>
> Key: TEIID-3228
> URL: https://issues.jboss.org/browse/TEIID-3228
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.7
> Reporter: Filip Elias
> Assignee: Ramesh Reddy
> Labels: Alpaha1
> Fix For: 8.7.1, 8.10
>
>
> SolrSQLHierarchyVisitor uses incorrect Date and Timestamp pattern.
> The pattern for Date is yyyy-MM-DD, but it should be yyyy-MM-dd.
> DD represents day in year, not day in month
> Similar issue occurs for Timestamp.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 7 months