[JBoss JIRA] (TEIID-3281) MongoDB: EmptyStackException when joining tables
by Filip Elias (JIRA)
Filip Elias created TEIID-3281:
----------------------------------
Summary: MongoDB: EmptyStackException when joining tables
Key: TEIID-3281
URL: https://issues.jboss.org/browse/TEIID-3281
Project: Teiid
Issue Type: Bug
Components: Connector API
Affects Versions: 8.7
Reporter: Filip Elias
Assignee: Steven Hawkins
Teiid throws java.util.EmptyStackException when joining data from table which has teiid_mongo:MERGE property enabled.
Example:
{code}
insert into customer2 values(1,'Pepa', 'Koukal');
insert into customer2 values(2,'Jan', 'Tlemil');
insert into Address values(1,1,'Pepas Street','Pepas City','Pepas State', 'Pepas zipcode');
insert into Address values(2,2,'Jans Street','Pepa','Jans State', 'Jans zipcode');
{code}
{code}
select a.*,b.* from customer2 a inner join Address b on a.CustomerId=b.CustomerId order by a.customerID
{code}
{code}
Error:
java.util.EmptyStackException
at java.util.Stack.peek(Stack.java:102)
at java.util.Stack.pop(Stack.java:84)
at org.teiid.translator.mongodb.MongoDBSelectVisitor.visit(MongoDBSelectVisitor.java:993)
at org.teiid.language.SortSpecification.acceptVisitor(SortSpecification.java:53)
at org.teiid.language.visitor.AbstractLanguageVisitor.visitNode(AbstractLanguageVisitor.java:51)
at org.teiid.translator.mongodb.MongoDBSelectVisitor.append(MongoDBSelectVisitor.java:112)
{code}
VDB and log are in the attachment.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (TEIID-3276) Data result not correct when joinning subquery over a date field
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3276?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3276:
----------------------------------
Fix Version/s: 8.10
> Data result not correct when joinning subquery over a date field
> ----------------------------------------------------------------
>
> Key: TEIID-3276
> URL: https://issues.jboss.org/browse/TEIID-3276
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 7.7
> Reporter: Mark Tawk
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 8.10
>
>
> Hello,
> I'm using Teiid 8.9.0 To execute the below query and the execution is done without the problem; the issue is that I'm getting different results when executing the same query over mysql
> The original query is much bigger but i tried to simplify it to isolate the problem.
> SELECT DISTINCT
> WEEK(contactcalldetail.startdatetime) AS contactcalldetail_startdatet,
> sessionid_Sub.contactcalldetail_sessionid
> AS contactcalldetail_sessionid
> FROM db_cra_8F_VDB_DSModel.db_cra.contactcalldetail contactcalldetail
> LEFT JOIN /* optional */
> (SELECT COUNT(DISTINCT contactcalldetail_sub.sessionid)
> AS contactcalldetail_sessionid,
> WEEK(contactcalldetail_sub.startdatetime)
> AS contactcalldetail_startdatet
> FROM db_cra_8F_VDB_DSModel.db_cra.contactcalldetail contactcalldetail_sub
> WHERE (((contactcalldetail_sub.contacttype IN (1))))
> AND ((((contactcalldetail_sub.connecttime >= 300))))
> GROUP BY WEEK(contactcalldetail_sub.startdatetime)) sessionid_Sub
> ON (WEEK(contactcalldetail.startdatetime) =
> sessionid_Sub.contactcalldetail_startdatet)
> WHERE (((contactcalldetail.contacttype IN (1))))
> LIMIT 0, 10
> Here is Teiid execution plan :
> <?xml version='1.0' encoding='UTF-8'?><node name="LimitNode"><property name="Output Columns"><value>contactcalldetail_startdatet (integer)</value><value>contactcalldetail_sessionid (integer)</value></property><property name="Statistics"><value>Node Output Rows: 1</value><value>Node Next Batch Process Time: 0</value><value>Node Cumulative Next Batch Process Time: 12</value><value>Node Cumulative Process Time: 0</value><value>Node Next Batch Calls: 3</value><value>Node Blocks: 2</value></property><property name="Cost Estimates"><value>Estimated Node Cardinality: 10.0</value></property><property name="Child 0"><node name="SortNode"><property name="Output Columns"><value>contactcalldetail_startdatet (integer)</value><value>contactcalldetail_sessionid (integer)</value></property><property name="Statistics"><value>Node Output Rows: 1</value><value>Node Next Batch Process Time: 0</value><value>Node Cumulative Next Batch Process Time: 12</value><value>Node Cumulative Process Time: 0</value><value>Node Next Batch Calls: 3</value><value>Node Blocks: 2</value></property><property name="Cost Estimates"><value>Estimated Node Cardinality: -1.0</value></property><property name="Child 0"><node name="ProjectNode"><property name="Output Columns"><value>contactcalldetail_startdatet (integer)</value><value>contactcalldetail_sessionid (integer)</value></property><property name="Statistics"><value>Node Output Rows: 4096</value><value>Node Next Batch Process Time: 0</value><value>Node Cumulative Next Batch Process Time: 13</value><value>Node Cumulative Process Time: 0</value><value>Node Next Batch Calls: 5</value><value>Node Blocks: 3</value></property><property name="Cost Estimates"><value>Estimated Node Cardinality: -1.0</value></property><property name="Child 0"><node name="JoinNode"><property name="Output Columns"><value>startdatetime (timestamp)</value><value>contactcalldetail_sessionid (integer)</value></property><property name="Statistics"><value>Node Output Rows: 4096</value><value>Node Next Batch Process Time: 0</value><value>Node Cumulative Next Batch Process Time: 11</value><value>Node Cumulative Process Time: 0</value><value>Node Next Batch Calls: 5</value><value>Node Blocks: 3</value></property><property name="Cost Estimates"><value>Estimated Node Cardinality: -1.0</value></property><property name="Child 0"><node name="AccessNode"><property name="Output Columns"><value>startdatetime (timestamp)</value><value>expr (integer)</value></property><property name="Statistics"><value>Node Output Rows: 4096</value><value>Node Next Batch Process Time: 0</value><value>Node Cumulative Next Batch Process Time: 0</value><value>Node Cumulative Process Time: 0</value><value>Node Next Batch Calls: 7</value><value>Node Blocks: 5</value></property><property name="Cost Estimates"><value>Estimated Node Cardinality: -1.0</value></property><property name="Query"><value>SELECT DISTINCT g_0.startdatetime AS c_0, WEEK(g_0.startdatetime) AS c_1 FROM db_cra_8F_VDB_DSModel.db_cra.contactcalldetail AS g_0 WHERE g_0.contacttype = 1 ORDER BY c_1</value></property><property name="Model Name"><value>db_cra_8F_VDB_DSModel</value></property></node></property><property name="Child 1"><node name="ProjectNode"><property name="Output Columns"><value>contactcalldetail_startdatet (integer)</value><value>contactcalldetail_sessionid (integer)</value></property><property name="Statistics"><value>Node Output Rows: 3</value><value>Node Next Batch Process Time: 7</value><value>Node Cumulative Next Batch Process Time: 8</value><value>Node Cumulative Process Time: 15</value><value>Node Next Batch Calls: 2</value><value>Node Blocks: 1</value></property><property name="Cost Estimates"><value>Estimated Node Cardinality: -1.0</value></property><property name="Child 0"><node name="GroupingNode"><property name="Output Columns"><value>gcol0 (integer)</value><value>agg0 (integer)</value></property><property name="Statistics"><value>Node Output Rows: 3</value><value>Node Next Batch Process Time: 14</value><value>Node Cumulative Next Batch Process Time: 8</value><value>Node Cumulative Process Time: 15</value><value>Node Next Batch Calls: 2</value><value>Node Blocks: 1</value></property><property name="Cost Estimates"><value>Estimated Node Cardinality: -1.0</value></property><property name="Child 0"><node name="AccessNode"><property name="Output Columns"><value>startdatetime (timestamp)</value><value>sessionid (long)</value></property><property name="Statistics"><value>Node Output Rows: 772</value><value>Node Next Batch Process Time: 9</value><value>Node Cumulative Next Batch Process Time: 1</value><value>Node Cumulative Process Time: 9</value><value>Node Next Batch Calls: 2</value><value>Node Blocks: 1</value></property><property name="Cost Estimates"><value>Estimated Node Cardinality: -1.0</value></property><property name="Query"><value>SELECT g_0.startdatetime, g_0.sessionid FROM db_cra_8F_VDB_DSModel.db_cra.contactcalldetail AS g_0 WHERE (g_0.contacttype = 1) AND (g_0.connecttime >= 300)</value></property><property name="Model Name"><value>db_cra_8F_VDB_DSModel</value></property></node></property><property name="Grouping Columns"><value>WEEK(contactcalldetail_sub.startdatetime)</value></property><property name="Sort Mode"><value>false</value></property></node></property><property name="Select Columns"><value>anon_grp0.gcol0 AS contactcalldetail_startdatet</value><value>anon_grp0.agg0 AS contactcalldetail_sessionid</value></property></node></property><property name="Join Strategy"><value>MERGE JOIN (ALREADY_SORTED/SORT)</value></property><property name="Join Type"><value>LEFT OUTER JOIN</value></property><property name="Join Criteria"><value>WEEK(contactcalldetail.startdatetime)=sessionid_Sub.contactcalldetail_startdatet</value></property></node></property><property name="Select Columns"><value>WEEK(contactcalldetail.startdatetime) AS contactcalldetail_startdatet</value><value>sessionid_Sub.contactcalldetail_sessionid AS contactcalldetail_sessionid</value></property></node></property><property name="Sort Mode"><value>DUP_REMOVE</value></property></node></property><property name="Row Offset"><value>null</value></property><property name="Row Limit"><value>10</value></property></node>
> Here are the 2 JDBC queries executed by Teiid:
> SELECT DISTINCT g_0.`startdatetime` AS c_0, week(g_0.`startdatetime`) AS c_1 FROM `db_cra`.`contactcalldetail` AS g_0 WHERE g_0.`contacttype` = 1 ORDER BY c_1
> SELECT g_0.`startdatetime`, g_0.`sessionid` FROM `db_cra`.`contactcalldetail` AS g_0 WHERE g_0.`contacttype` = 1 AND g_0.`connecttime` >= 300
> Teiid query execution result is :
> week countsession
> 36 null
> 37 328
> 38 384
> mysql execution result:
> week countsession
> 35 328
> 36 384
> 37 60
> You can notice that the week is incremented by one and the count result is scrambled
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (TEIID-3276) Data result not correct when joinning subquery over a date field
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3276?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3276:
----------------------------------
Affects Version/s: 7.7
Component/s: JDBC Connector
Looking at this some more I believe the issue is that the week function is being calculated at both the source and in Teiid.
Teiid effectively has two options for the week calculation:
java default based upon locale (default)
iso8601 - https://docs.jboss.org/author/display/TEIID/System+Properties
MySQL has 8 modes: http://dev.mysql.com/doc/refman/5.5/en/date-and-time-functions.html#funct...
And their default does not correspond to either of Teiid's week calculations.
With Teiid in iso 8601 mode and the mysql translator updated to call week with mode 3, the weeks will match.
Also we should probably make the iso week handling the default for Teiid to make things more consistent.
Another general fix is with how we are handling the week function subexpresion in this situation. Ideally we should not be calculating it in both Teiid and at the source, but we aren't yet going symbolic replacement of subexpressions generally (we did add partial projection pushing, but even that doesn't apply here with the join).
> Data result not correct when joinning subquery over a date field
> ----------------------------------------------------------------
>
> Key: TEIID-3276
> URL: https://issues.jboss.org/browse/TEIID-3276
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 7.7
> Reporter: Mark Tawk
> Assignee: Steven Hawkins
> Priority: Critical
>
> Hello,
> I'm using Teiid 8.9.0 To execute the below query and the execution is done without the problem; the issue is that I'm getting different results when executing the same query over mysql
> The original query is much bigger but i tried to simplify it to isolate the problem.
> SELECT DISTINCT
> WEEK(contactcalldetail.startdatetime) AS contactcalldetail_startdatet,
> sessionid_Sub.contactcalldetail_sessionid
> AS contactcalldetail_sessionid
> FROM db_cra_8F_VDB_DSModel.db_cra.contactcalldetail contactcalldetail
> LEFT JOIN /* optional */
> (SELECT COUNT(DISTINCT contactcalldetail_sub.sessionid)
> AS contactcalldetail_sessionid,
> WEEK(contactcalldetail_sub.startdatetime)
> AS contactcalldetail_startdatet
> FROM db_cra_8F_VDB_DSModel.db_cra.contactcalldetail contactcalldetail_sub
> WHERE (((contactcalldetail_sub.contacttype IN (1))))
> AND ((((contactcalldetail_sub.connecttime >= 300))))
> GROUP BY WEEK(contactcalldetail_sub.startdatetime)) sessionid_Sub
> ON (WEEK(contactcalldetail.startdatetime) =
> sessionid_Sub.contactcalldetail_startdatet)
> WHERE (((contactcalldetail.contacttype IN (1))))
> LIMIT 0, 10
> Here is Teiid execution plan :
> <?xml version='1.0' encoding='UTF-8'?><node name="LimitNode"><property name="Output Columns"><value>contactcalldetail_startdatet (integer)</value><value>contactcalldetail_sessionid (integer)</value></property><property name="Statistics"><value>Node Output Rows: 1</value><value>Node Next Batch Process Time: 0</value><value>Node Cumulative Next Batch Process Time: 12</value><value>Node Cumulative Process Time: 0</value><value>Node Next Batch Calls: 3</value><value>Node Blocks: 2</value></property><property name="Cost Estimates"><value>Estimated Node Cardinality: 10.0</value></property><property name="Child 0"><node name="SortNode"><property name="Output Columns"><value>contactcalldetail_startdatet (integer)</value><value>contactcalldetail_sessionid (integer)</value></property><property name="Statistics"><value>Node Output Rows: 1</value><value>Node Next Batch Process Time: 0</value><value>Node Cumulative Next Batch Process Time: 12</value><value>Node Cumulative Process Time: 0</value><value>Node Next Batch Calls: 3</value><value>Node Blocks: 2</value></property><property name="Cost Estimates"><value>Estimated Node Cardinality: -1.0</value></property><property name="Child 0"><node name="ProjectNode"><property name="Output Columns"><value>contactcalldetail_startdatet (integer)</value><value>contactcalldetail_sessionid (integer)</value></property><property name="Statistics"><value>Node Output Rows: 4096</value><value>Node Next Batch Process Time: 0</value><value>Node Cumulative Next Batch Process Time: 13</value><value>Node Cumulative Process Time: 0</value><value>Node Next Batch Calls: 5</value><value>Node Blocks: 3</value></property><property name="Cost Estimates"><value>Estimated Node Cardinality: -1.0</value></property><property name="Child 0"><node name="JoinNode"><property name="Output Columns"><value>startdatetime (timestamp)</value><value>contactcalldetail_sessionid (integer)</value></property><property name="Statistics"><value>Node Output Rows: 4096</value><value>Node Next Batch Process Time: 0</value><value>Node Cumulative Next Batch Process Time: 11</value><value>Node Cumulative Process Time: 0</value><value>Node Next Batch Calls: 5</value><value>Node Blocks: 3</value></property><property name="Cost Estimates"><value>Estimated Node Cardinality: -1.0</value></property><property name="Child 0"><node name="AccessNode"><property name="Output Columns"><value>startdatetime (timestamp)</value><value>expr (integer)</value></property><property name="Statistics"><value>Node Output Rows: 4096</value><value>Node Next Batch Process Time: 0</value><value>Node Cumulative Next Batch Process Time: 0</value><value>Node Cumulative Process Time: 0</value><value>Node Next Batch Calls: 7</value><value>Node Blocks: 5</value></property><property name="Cost Estimates"><value>Estimated Node Cardinality: -1.0</value></property><property name="Query"><value>SELECT DISTINCT g_0.startdatetime AS c_0, WEEK(g_0.startdatetime) AS c_1 FROM db_cra_8F_VDB_DSModel.db_cra.contactcalldetail AS g_0 WHERE g_0.contacttype = 1 ORDER BY c_1</value></property><property name="Model Name"><value>db_cra_8F_VDB_DSModel</value></property></node></property><property name="Child 1"><node name="ProjectNode"><property name="Output Columns"><value>contactcalldetail_startdatet (integer)</value><value>contactcalldetail_sessionid (integer)</value></property><property name="Statistics"><value>Node Output Rows: 3</value><value>Node Next Batch Process Time: 7</value><value>Node Cumulative Next Batch Process Time: 8</value><value>Node Cumulative Process Time: 15</value><value>Node Next Batch Calls: 2</value><value>Node Blocks: 1</value></property><property name="Cost Estimates"><value>Estimated Node Cardinality: -1.0</value></property><property name="Child 0"><node name="GroupingNode"><property name="Output Columns"><value>gcol0 (integer)</value><value>agg0 (integer)</value></property><property name="Statistics"><value>Node Output Rows: 3</value><value>Node Next Batch Process Time: 14</value><value>Node Cumulative Next Batch Process Time: 8</value><value>Node Cumulative Process Time: 15</value><value>Node Next Batch Calls: 2</value><value>Node Blocks: 1</value></property><property name="Cost Estimates"><value>Estimated Node Cardinality: -1.0</value></property><property name="Child 0"><node name="AccessNode"><property name="Output Columns"><value>startdatetime (timestamp)</value><value>sessionid (long)</value></property><property name="Statistics"><value>Node Output Rows: 772</value><value>Node Next Batch Process Time: 9</value><value>Node Cumulative Next Batch Process Time: 1</value><value>Node Cumulative Process Time: 9</value><value>Node Next Batch Calls: 2</value><value>Node Blocks: 1</value></property><property name="Cost Estimates"><value>Estimated Node Cardinality: -1.0</value></property><property name="Query"><value>SELECT g_0.startdatetime, g_0.sessionid FROM db_cra_8F_VDB_DSModel.db_cra.contactcalldetail AS g_0 WHERE (g_0.contacttype = 1) AND (g_0.connecttime >= 300)</value></property><property name="Model Name"><value>db_cra_8F_VDB_DSModel</value></property></node></property><property name="Grouping Columns"><value>WEEK(contactcalldetail_sub.startdatetime)</value></property><property name="Sort Mode"><value>false</value></property></node></property><property name="Select Columns"><value>anon_grp0.gcol0 AS contactcalldetail_startdatet</value><value>anon_grp0.agg0 AS contactcalldetail_sessionid</value></property></node></property><property name="Join Strategy"><value>MERGE JOIN (ALREADY_SORTED/SORT)</value></property><property name="Join Type"><value>LEFT OUTER JOIN</value></property><property name="Join Criteria"><value>WEEK(contactcalldetail.startdatetime)=sessionid_Sub.contactcalldetail_startdatet</value></property></node></property><property name="Select Columns"><value>WEEK(contactcalldetail.startdatetime) AS contactcalldetail_startdatet</value><value>sessionid_Sub.contactcalldetail_sessionid AS contactcalldetail_sessionid</value></property></node></property><property name="Sort Mode"><value>DUP_REMOVE</value></property></node></property><property name="Row Offset"><value>null</value></property><property name="Row Limit"><value>10</value></property></node>
> Here are the 2 JDBC queries executed by Teiid:
> SELECT DISTINCT g_0.`startdatetime` AS c_0, week(g_0.`startdatetime`) AS c_1 FROM `db_cra`.`contactcalldetail` AS g_0 WHERE g_0.`contacttype` = 1 ORDER BY c_1
> SELECT g_0.`startdatetime`, g_0.`sessionid` FROM `db_cra`.`contactcalldetail` AS g_0 WHERE g_0.`contacttype` = 1 AND g_0.`connecttime` >= 300
> Teiid query execution result is :
> week countsession
> 36 null
> 37 328
> 38 384
> mysql execution result:
> week countsession
> 35 328
> 36 384
> 37 60
> You can notice that the week is incremented by one and the count result is scrambled
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (TEIID-3280) Embedded Teiid | VDB scoped translators
by Shiveeta Mattoo (JIRA)
Shiveeta Mattoo created TEIID-3280:
--------------------------------------
Summary: Embedded Teiid | VDB scoped translators
Key: TEIID-3280
URL: https://issues.jboss.org/browse/TEIID-3280
Project: Teiid
Issue Type: Enhancement
Components: Embedded
Reporter: Shiveeta Mattoo
Assignee: Steven Hawkins
Priority: Minor
- Translator instances, once created are applicable for all VDB deployment invocations.
- Seeking support for VDB scoped translators which could enable configuring properties for translators specific to VDB instances.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (TEIID-3279) SOLR: Error when date, time or timestamp literal is in where clause
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3279?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-3279:
-------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1180107
> SOLR: Error when date,time or timestamp literal is in where clause
> ------------------------------------------------------------------
>
> Key: TEIID-3279
> URL: https://issues.jboss.org/browse/TEIID-3279
> Project: Teiid
> Issue Type: Bug
> Components: Connector API
> Affects Versions: 8.7
> Reporter: Filip Elias
> Assignee: Steven Hawkins
>
> Query fails when time,date or timestamp literal is used in where clause.
> Examples:
> Query:
> {code}select intkey from smalla where timevalue = '11:30:20'{code}
> Error:
> {code}
> '11:30:20'org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: Invalid Date String:'11-30-20'
> at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:491)
> {code}
> Query:
> {code}select intkey from smalla where datevalue = '2002-02-02'{code}
> Error:
> {code}
> org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: Invalid Date String:'11-30-20'
> at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:491)
> {code}
> Query:
> {code}select intkey from smalla where timestampvalue = '2000-01-01 00:00:04'{code}
> Error:
> {code} org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: Invalid Date String:'2000-01-01T00-00-04'
> at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:491)
> {code}
> SOLR supports only timestamps (YYYY-mm-ddThh:mm:ssZ) so date and time types should be converted into timestamp before a query is send to SOLR.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (TEIID-3279) SOLR: Error when date, time or timestamp literal is in where clause
by Filip Elias (JIRA)
Filip Elias created TEIID-3279:
----------------------------------
Summary: SOLR: Error when date,time or timestamp literal is in where clause
Key: TEIID-3279
URL: https://issues.jboss.org/browse/TEIID-3279
Project: Teiid
Issue Type: Bug
Components: Connector API
Affects Versions: 8.7
Reporter: Filip Elias
Assignee: Steven Hawkins
Query fails when time,date or timestamp literal is used in where clause.
Examples:
Query:
{code}select intkey from smalla where timevalue = '11:30:20'{code}
Error:
{code}
'11:30:20'org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: Invalid Date String:'11-30-20'
at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:491)
{code}
Query:
{code}select intkey from smalla where datevalue = '2002-02-02'{code}
Error:
{code}
org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: Invalid Date String:'11-30-20'
at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:491)
{code}
Query:
{code}select intkey from smalla where timestampvalue = '2000-01-01 00:00:04'{code}
Error:
{code} org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: Invalid Date String:'2000-01-01T00-00-04'
at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:491)
{code}
SOLR supports only timestamps (YYYY-mm-ddThh:mm:ssZ) so date and time types should be converted into timestamp before a query is send to SOLR.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (TEIID-2730) Cannot query Sybase database with jconn3.jar
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-2730?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-2730:
------------------------------------------------
Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1028380|https://bugzilla.redhat.com/show_bug.cgi?id=1028380] from ON_QA to VERIFIED
> Cannot query Sybase database with jconn3.jar
> --------------------------------------------
>
> Key: TEIID-2730
> URL: https://issues.jboss.org/browse/TEIID-2730
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.4
> Environment: java oracle 1.7, Teiid 8.4.1-redhat4 in DV 6.0.0.ER3, Teiid Designer 8.3.beta3
> Reporter: Lucie Fabrikova
> Assignee: Steven Hawkins
> Fix For: 8.6
>
> Attachments: bqtHNB.vdb, bqt_HNB.xmi, jconn3.jar
>
>
> In teiid designer, I created a connection profile to Sybase database with URL jdbc:sybase:Tds:vmg07.mw.lab.eng.bos.redhat.com:5000/bqt2 and driver jconn3.jar.
> I created a relational source model from the jdbc connection and VDB with the source model. Then I deployed the VDB and executed query select * from "bqt_HNB"."g1" which resulted in this error message:
> TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 bqt_HNB: 102 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."e1", g_0."e2" FROM "bqt2"."dbo"."g1" g_0]
> Console:
> OPTIMIZATION COMPLETE:
> PROCESSOR PLAN:
> AccessNode(0) output=[bqt_HNB.g1.e1, bqt_HNB.g1.e2] SELECT g_0.e1, g_0.e2 FROM bqt_HNB.g1 AS g_0
> ============================================================================
> 10:55:07,362 INFO [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue1) SybaseExecutionFactory Commit=true;DatabaseProductName=Adaptive Server Enterprise;DatabaseProductVersion=Adaptive Server Enterprise/15.0.3/EBF 16549 ESD#1/P/x86_64/Enterprise Linux/ase1503/2681/64-bit/FBO/Mon Mar 9 04:10:47 2009;DriverMajorVersion=6;DriverMajorVersion=0;DriverName=jConnect (TM) for JDBC (TM);DriverVersion=jConnect (TM) for JDBC(TM)/6.05(Build 26564)/P/EBF16903/JDK14/Sun May 31 1:05:35 2009;IsolationLevel=2
> 10:55:07,555 WARN [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue1) Connector worker process failed for atomic-request=dg2FpIhALlUI.0.0.0: org.teiid.translator.jdbc.JDBCExecutionException: 102 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."e1", g_0."e2" FROM "bqt2"."dbo"."g1" g_0]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:88)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:254) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:444) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:157) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:154) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [rt.jar:1.6.0_45]
> at java.util.concurrent.FutureTask.run(FutureTask.java:138) [rt.jar:1.6.0_45]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:269) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_45]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_45]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45]
> Caused by: com.sybase.jdbc3.jdbc.SybSQLException: Incorrect syntax near 'e1'.
> at com.sybase.jdbc3.tds.Tds.a(Unknown Source)
> at com.sybase.jdbc3.tds.Tds.nextResult(Unknown Source)
> at com.sybase.jdbc3.jdbc.ResultGetter.nextResult(Unknown Source)
> at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source)
> at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source)
> at com.sybase.jdbc3.jdbc.SybStatement.queryLoop(Unknown Source)
> at com.sybase.jdbc3.jdbc.SybStatement.executeQuery(Unknown Source)
> at com.sybase.jdbc3.jdbc.SybPreparedStatement.executeQuery(Unknown Source)
> at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:462)
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:84)
> ... 13 more
> 10:55:07,568 WARN [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue2) TEIID30020 Processing exception for request dg2FpIhALlUI.0 'TEIID30504 bqt_HNB: 102 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."e1", g_0."e2" FROM "bqt2"."dbo"."g1" g_0]'. Originally TeiidProcessingException 'Incorrect syntax near 'e1'.
> ' com.sybase.jdbc3.tds.Tds.a(Unknown Source). Enable more detailed logging to see the entire stacktrace.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (TEIID-2384) Managing Spatial Data Types
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2384?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2384:
---------------------------------------
Added the initial support based upon the work started by Tom Arnold. The approach uses a new geometrytype that is effectively a blob. Then all manipulation is handled through functions (the conversion logic was removed as it's more explicit to use named functions):
ST_ASTEXT
ST_ASBINARY
ST_GEOMFROMTEXT
ST_GEOMFROMBINARY
ST_INTERSECTS
ST_CONTAINS
All of which have implementations in Teiid. Sources are expected to at least support ST_ASBINARY and ST_GEOMFROMBINARY to support conversion into and out of the well known binary format.
Only limited oracle and mysql support was addressed with this commit. We should add as many function methods as supported jts and commonly used by sources. The translators primarily oracle, postgresql, and mysql similarly need updated to add function aliases and functions into the supported list.
We should also look at what could be done to reconcile this approach with the older oracle geospatial support.
> Managing Spatial Data Types
> ---------------------------
>
> Key: TEIID-2384
> URL: https://issues.jboss.org/browse/TEIID-2384
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Affects Versions: 8.2
> Reporter: luca gioppo
> Assignee: Steven Hawkins
> Labels: spatial, types
> Fix For: 8.10
>
>
> It would be useful to be able to consume data from spatial database exposing the VDB as a spatial database to other application (imagine geoserver).
> TEIID could be strategic for merging georeferenced data and make it available to those systems.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (TEIID-2384) Managing Spatial Data Types
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2384?page=com.atlassian.jira.plugin... ]
Steven Hawkins reassigned TEIID-2384:
-------------------------------------
Fix Version/s: 8.10
Assignee: Steven Hawkins
> Managing Spatial Data Types
> ---------------------------
>
> Key: TEIID-2384
> URL: https://issues.jboss.org/browse/TEIID-2384
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Affects Versions: 8.2
> Reporter: luca gioppo
> Assignee: Steven Hawkins
> Labels: spatial, types
> Fix For: 8.10
>
>
> It would be useful to be able to consume data from spatial database exposing the VDB as a spatial database to other application (imagine geoserver).
> TEIID could be strategic for merging georeferenced data and make it available to those systems.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (TEIID-3240) Tranlator archetype creation: -Dversion option sets the version of parent
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3240?page=com.atlassian.jira.plugin... ]
Van Halbert resolved TEIID-3240.
--------------------------------
Resolution: Done
With the fix of TEIID-3274, this will fix this issue. Note, by design the created project is not created so that it has to be built with a Teiid build, but built as an independent project.
> Tranlator archetype creation: -Dversion option sets the version of parent
> -------------------------------------------------------------------------
>
> Key: TEIID-3240
> URL: https://issues.jboss.org/browse/TEIID-3240
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1
> Reporter: Juraj Duráni
> Assignee: Van Halbert
>
> If new translator is created using command line, -Dversion option is set as version of parent project instead of version of actual translator.
> pom file:
> <parent>
> <groupId>org.jboss.teiid</groupId>
> <artifactId>connectors</artifactId>
> <version>0.0.1</version>
> </parent>
> ...
> <groupId>org.jboss.teiid.test.translator</groupId>
> <artifactId>test-translator</artifactId>
> <!--version>0.0.1</version-->
> <packaging>jar</packaging>
> ...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months