March 2015 - teiid-issues - Jboss List Archives

[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 commented on TEIID-3279: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1180107|https://bugzilla.redhat.com/show_bug.cgi?id=1180107] from NEW to MODIFIED > 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: Ramesh Reddy > Labels: Beta1 > Fix For: 8.7.1, 8.10 > > > 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

1
0
0 / 0

[JBoss JIRA] (TEIID-3401) OData layer generates incorrect alias names in orderby

by Sanjeev Gour (JIRA)

[ https://issues.jboss.org/browse/TEIID-3401?page=com.atlassian.jira.plugin... ] Sanjeev Gour commented on TEIID-3401: ------------------------------------- Hi Steve- I have not been able to recreate this issue with H2 or the other data source where I was facing the problem. Possibly, it is some specific scenario which I missed to notice. This issue can be closed for now and if I get the scenario, I will open a new one. Thanks. > OData layer generates incorrect alias names in orderby > ------------------------------------------------------ > > Key: TEIID-3401 > URL: https://issues.jboss.org/browse/TEIID-3401 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Sanjeev Gour > Assignee: Steven Hawkins > Fix For: 8.7 > > > When a table has large number of columns, a request like the following http://localhost:8080/odata/VDB.1/objectName generates a query like SELECT col1 as c_1, col2 as c2.....col23 as c_23...col35 as c_35 ..FROM objectName ORDER BY "c_0", "c_1", "c_2", "c_3", "c_2"3, "c_3"5. Here c_0, c_1, c_2, c_3, c_23, c_35 happen to be the primary key columns. As seen in the query, the quotes around the column alias are incorrect for c_23 and c_35 which results into an invalid query. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3396) Redis Connector

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3396?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3396: --------------------------------------- Thanks. Just add a comment here when things seem complete and you've done the CLA. > Redis Connector > ---------------- > > Key: TEIID-3396 > URL: https://issues.jboss.org/browse/TEIID-3396 > Project: Teiid > Issue Type: Enhancement > Components: Connector API > Affects Versions: 8.11 > Reporter: Devin Pinkston > Assignee: Steven Hawkins > Priority: Minor > > Resource Adapter and Translator for Redis store (http://redis.io/) > Using Jedis client (https://github.com/xetorthio/jedis) > https://github.com/pinkdevelops/teiid -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3404) Teiid DatabaseAppender JPA perisist Command log consume high CPU

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3404?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3404: ------------------------------------- I did not wanted to use JDBC as there are enough database specific issues, we need to provide plugins for each source. JPA seemed lot simpler and even can create the tables on the fly. Is batching possible in JPA? if yes, may be we can use it. This mechanism using EJB with JPA, we need to see if this a EJB pooling issue or what is contributing to the high CPU. The thing I do not like about it is there is no further management we offer on it, like archiving, log rotations or viewing or searching, nor I would like to go into that space, that is where below solutions come in.. What would be interesting is move on to new log management systems like http://logstash.net/ http://www.fluentd.org/ https://cwiki.apache.org/confluence/display/FLUME/Home (written in java) http://kafka.apache.org/ I am sure for most of them they may already support the Log4J appenders, we should research into these as separate issue. > Teiid DatabaseAppender JPA perisist Command log consume high CPU > ---------------------------------------------------------------- > > Key: TEIID-3404 > URL: https://issues.jboss.org/browse/TEIID-3404 > Project: Teiid > Issue Type: Bug > Components: Tools > Affects Versions: 8.7.1 > Environment: * DV 6.1 > * dynamicvdb-datafederation quickstart > Reporter: Kylin Soong > Assignee: Kylin Soong > > I have 4 - 5 concurrent client query to Portfolio VDB, this cause log DatabaseAppender JPA perisist Command log thread consume high CPU. In my test, one log threads always swallow high CPU, if the concurrent client query more than 10, it swallow 100% cpu. > [1] have detailed reproduce steps, including thread dumps. > [1] https://github.com/kylinsoong/teiid-samples/tree/master/command-logging-h... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3401) OData layer generates incorrect alias names in orderby

by Sanjeev Gour (JIRA)

[ https://issues.jboss.org/browse/TEIID-3401?page=com.atlassian.jira.plugin... ] Sanjeev Gour commented on TEIID-3401: ------------------------------------- I will try and locate area of problem. By web service translator, I didn't mean the WS translator, it is a custom translator. > OData layer generates incorrect alias names in orderby > ------------------------------------------------------ > > Key: TEIID-3401 > URL: https://issues.jboss.org/browse/TEIID-3401 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Sanjeev Gour > Assignee: Steven Hawkins > Fix For: 8.7 > > > When a table has large number of columns, a request like the following http://localhost:8080/odata/VDB.1/objectName generates a query like SELECT col1 as c_1, col2 as c2.....col23 as c_23...col35 as c_35 ..FROM objectName ORDER BY "c_0", "c_1", "c_2", "c_3", "c_2"3, "c_3"5. Here c_0, c_1, c_2, c_3, c_23, c_35 happen to be the primary key columns. As seen in the query, the quotes around the column alias are incorrect for c_23 and c_35 which results into an invalid query. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3401) OData layer generates incorrect alias names in orderby

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3401?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3401: --------------------------------------- > Do you have any idea if any translator property or the way metadata is generated will affect the query generation behaviour The order by behavior will vary by translator. For most the expectation is that the engine will use aliases in the select clause, which will then be referenced in the order by. > but with the web service translator the alias name is enclosed in quotes causing the problem. The web service translator? The ws translator only supports procedures. > Also, if you can point to the location where the url is converted to sql, I can possibly debug and see what is going wrong. Ideally you'd first seem at what layer an issue is occurring. From the top down with the odata path you have: Odata URL -> Teiid SQL query (odata layer) Teiid SQL query planning -> processor plan (engine) Pushdown query -> source specific query (translator) With logging you should be able to see when things become invalid. With debugging, you can see the OData layer issue queries in org.teiid.odata.LocalClient. Then see the pushdown queries in org.teiid.dqp.internal.datamgr.DataManagerImpl.registerRequest, then see the source specific in whatever translator you are using. > OData layer generates incorrect alias names in orderby > ------------------------------------------------------ > > Key: TEIID-3401 > URL: https://issues.jboss.org/browse/TEIID-3401 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Sanjeev Gour > Assignee: Steven Hawkins > Fix For: 8.7 > > > When a table has large number of columns, a request like the following http://localhost:8080/odata/VDB.1/objectName generates a query like SELECT col1 as c_1, col2 as c2.....col23 as c_23...col35 as c_35 ..FROM objectName ORDER BY "c_0", "c_1", "c_2", "c_3", "c_2"3, "c_3"5. Here c_0, c_1, c_2, c_3, c_23, c_35 happen to be the primary key columns. As seen in the query, the quotes around the column alias are incorrect for c_23 and c_35 which results into an invalid query. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3401) OData layer generates incorrect alias names in orderby

by Sanjeev Gour (JIRA)

[ https://issues.jboss.org/browse/TEIID-3401?page=com.atlassian.jira.plugin... ] Sanjeev Gour commented on TEIID-3401: ------------------------------------- Also, if you can point to the location where the url is converted to sql, I can possibly debug and see what is going wrong. > OData layer generates incorrect alias names in orderby > ------------------------------------------------------ > > Key: TEIID-3401 > URL: https://issues.jboss.org/browse/TEIID-3401 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Sanjeev Gour > Assignee: Steven Hawkins > Fix For: 8.7 > > > When a table has large number of columns, a request like the following http://localhost:8080/odata/VDB.1/objectName generates a query like SELECT col1 as c_1, col2 as c2.....col23 as c_23...col35 as c_35 ..FROM objectName ORDER BY "c_0", "c_1", "c_2", "c_3", "c_2"3, "c_3"5. Here c_0, c_1, c_2, c_3, c_23, c_35 happen to be the primary key columns. As seen in the query, the quotes around the column alias are incorrect for c_23 and c_35 which results into an invalid query. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3401) OData layer generates incorrect alias names in orderby

by Sanjeev Gour (JIRA)

[ https://issues.jboss.org/browse/TEIID-3401?page=com.atlassian.jira.plugin... ] Sanjeev Gour commented on TEIID-3401: ------------------------------------- I will try and see if I can create it easily. I tried with H2 but the query it generated was correct. My original problem is with a custom translator which reads the metadata from a csv file in the getMatada method. Do you have any idea if any translator property or the way metadata is generated will affect the query generation behaviour. With H2, there are no double quotes around the alias name in the order by but with the web service translator the alias name is enclosed in quotes causing the problem. > OData layer generates incorrect alias names in orderby > ------------------------------------------------------ > > Key: TEIID-3401 > URL: https://issues.jboss.org/browse/TEIID-3401 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Sanjeev Gour > Assignee: Steven Hawkins > Fix For: 8.7 > > > When a table has large number of columns, a request like the following http://localhost:8080/odata/VDB.1/objectName generates a query like SELECT col1 as c_1, col2 as c2.....col23 as c_23...col35 as c_35 ..FROM objectName ORDER BY "c_0", "c_1", "c_2", "c_3", "c_2"3, "c_3"5. Here c_0, c_1, c_2, c_3, c_23, c_35 happen to be the primary key columns. As seen in the query, the quotes around the column alias are incorrect for c_23 and c_35 which results into an invalid query. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3404) Teiid DatabaseAppender JPA perisist Command log consume high CPU

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3404?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3404: ------------------------------------ This was driven by a customer. And H2 is NOT recommended for production, and is configurable at installation time. Also, the teiid-dashboard has a new logging workspace that is made available when the logging database used. > Teiid DatabaseAppender JPA perisist Command log consume high CPU > ---------------------------------------------------------------- > > Key: TEIID-3404 > URL: https://issues.jboss.org/browse/TEIID-3404 > Project: Teiid > Issue Type: Bug > Components: Tools > Affects Versions: 8.7.1 > Environment: * DV 6.1 > * dynamicvdb-datafederation quickstart > Reporter: Kylin Soong > Assignee: Kylin Soong > > I have 4 - 5 concurrent client query to Portfolio VDB, this cause log DatabaseAppender JPA perisist Command log thread consume high CPU. In my test, one log threads always swallow high CPU, if the concurrent client query more than 10, it swallow 100% cpu. > [1] have detailed reproduce steps, including thread dumps. > [1] https://github.com/kylinsoong/teiid-samples/tree/master/command-logging-h... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3324) Boolean fields with null are evaluated to false

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3324?page=com.atlassian.jira.plugin... ] Steven Hawkins reopened TEIID-3324: ----------------------------------- > Boolean fields with null are evaluated to false > ----------------------------------------------- > > Key: TEIID-3324 > URL: https://issues.jboss.org/browse/TEIID-3324 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 7.1 > Reporter: Salvatore R > Assignee: Steven Hawkins > Fix For: 8.10 > > > I have a source table defined as follows (e.g. in PostgreSQL): > {code:sql} > CREATE TABLE public.test > ( > id integer, > iscustomer boolean > ) > {code} > and the table contains these rows: > {code:sql} > insert into public.test values(1, null); > insert into public.test values(2, true); > insert into public.test values(3, false); > {code} > > When I try to get data from this table in Teiid, the "null" value is evaluated as false: > ||id||iscustomer|| > |1|false| > |2|true| > |3|false| -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2015