April 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2916) HIVE2: Teiid didn't translate the SQL correctly for numeric field

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2916?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2916: ------------------------------------- Ok, we need to introduce Impala translator and fix there. > HIVE2: Teiid didn't translate the SQL correctly for numeric field > ------------------------------------------------------------------ > > Key: TEIID-2916 > URL: https://issues.jboss.org/browse/TEIID-2916 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7 > Environment: HIVE2 with Teiid > Reporter: Ivan Chan > Assignee: Steven Hawkins > Labels: Teiid > > Teiid didn't translate the SQL correctly for numeric field. It uses identifier "decimal" in the SQL which is not supported by the driver. > Original Query: > select "store_sales", > "store_state", > "store_country" > from "Impala"."sales_new" > where "store_sales" between 1.5 and 10 > limit 1000 > After Translation (Teiid): > SELECT g_0.store_sales AS c_0, g_0.store_state AS c_ > 1, g_0.store_country AS c_2 FROM sales_new g_0 WHERE cast(g_0.store_sales AS > decimal) >= 1.5 AND cast(g_0.store_sales AS decimal) <= 10 LIMIT 1000 > "decimal" is not supported identifier in HIVE driver: > Encountered: IDENTIFIER > Expected: BIGINT, BOOLEAN, DATE, DATETIME, REAL, FLOAT, INTEGER, SMALLINT, > STRING, TIMESTAMP, TINYINT -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2916) HIVE2: Teiid didn't translate the SQL correctly for numeric field

by Ivan Chan (JIRA)

[ https://issues.jboss.org/browse/TEIID-2916?page=com.atlassian.jira.plugin... ] Ivan Chan commented on TEIID-2916: ---------------------------------- And yes, it works for HIVE2 server. > HIVE2: Teiid didn't translate the SQL correctly for numeric field > ------------------------------------------------------------------ > > Key: TEIID-2916 > URL: https://issues.jboss.org/browse/TEIID-2916 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7 > Environment: HIVE2 with Teiid > Reporter: Ivan Chan > Assignee: Steven Hawkins > Labels: Teiid > > Teiid didn't translate the SQL correctly for numeric field. It uses identifier "decimal" in the SQL which is not supported by the driver. > Original Query: > select "store_sales", > "store_state", > "store_country" > from "Impala"."sales_new" > where "store_sales" between 1.5 and 10 > limit 1000 > After Translation (Teiid): > SELECT g_0.store_sales AS c_0, g_0.store_state AS c_ > 1, g_0.store_country AS c_2 FROM sales_new g_0 WHERE cast(g_0.store_sales AS > decimal) >= 1.5 AND cast(g_0.store_sales AS decimal) <= 10 LIMIT 1000 > "decimal" is not supported identifier in HIVE driver: > Encountered: IDENTIFIER > Expected: BIGINT, BOOLEAN, DATE, DATETIME, REAL, FLOAT, INTEGER, SMALLINT, > STRING, TIMESTAMP, TINYINT -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2916) HIVE2: Teiid didn't translate the SQL correctly for numeric field

by Ivan Chan (JIRA)

[ https://issues.jboss.org/browse/TEIID-2916?page=com.atlassian.jira.plugin... ] Ivan Chan commented on TEIID-2916: ---------------------------------- Impala Server. And I can try it with Hive2 Server, too. I will let u know ASAP. > HIVE2: Teiid didn't translate the SQL correctly for numeric field > ------------------------------------------------------------------ > > Key: TEIID-2916 > URL: https://issues.jboss.org/browse/TEIID-2916 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7 > Environment: HIVE2 with Teiid > Reporter: Ivan Chan > Assignee: Steven Hawkins > Labels: Teiid > > Teiid didn't translate the SQL correctly for numeric field. It uses identifier "decimal" in the SQL which is not supported by the driver. > Original Query: > select "store_sales", > "store_state", > "store_country" > from "Impala"."sales_new" > where "store_sales" between 1.5 and 10 > limit 1000 > After Translation (Teiid): > SELECT g_0.store_sales AS c_0, g_0.store_state AS c_ > 1, g_0.store_country AS c_2 FROM sales_new g_0 WHERE cast(g_0.store_sales AS > decimal) >= 1.5 AND cast(g_0.store_sales AS decimal) <= 10 LIMIT 1000 > "decimal" is not supported identifier in HIVE driver: > Encountered: IDENTIFIER > Expected: BIGINT, BOOLEAN, DATE, DATETIME, REAL, FLOAT, INTEGER, SMALLINT, > STRING, TIMESTAMP, TINYINT -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2916) HIVE2: Teiid didn't translate the SQL correctly for numeric field

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2916?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2916: ------------------------------------- Is this on Impala Server or Hive Server? Can you also try on Hive Server? We are thinking to separate the translator for each of them. > HIVE2: Teiid didn't translate the SQL correctly for numeric field > ------------------------------------------------------------------ > > Key: TEIID-2916 > URL: https://issues.jboss.org/browse/TEIID-2916 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7 > Environment: HIVE2 with Teiid > Reporter: Ivan Chan > Assignee: Steven Hawkins > Labels: Teiid > > Teiid didn't translate the SQL correctly for numeric field. It uses identifier "decimal" in the SQL which is not supported by the driver. > Original Query: > select "store_sales", > "store_state", > "store_country" > from "Impala"."sales_new" > where "store_sales" between 1.5 and 10 > limit 1000 > After Translation (Teiid): > SELECT g_0.store_sales AS c_0, g_0.store_state AS c_ > 1, g_0.store_country AS c_2 FROM sales_new g_0 WHERE cast(g_0.store_sales AS > decimal) >= 1.5 AND cast(g_0.store_sales AS decimal) <= 10 LIMIT 1000 > "decimal" is not supported identifier in HIVE driver: > Encountered: IDENTIFIER > Expected: BIGINT, BOOLEAN, DATE, DATETIME, REAL, FLOAT, INTEGER, SMALLINT, > STRING, TIMESTAMP, TINYINT -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2917) Cassandra: update to cassandra driver to version 2.X

by Ivan Chan (JIRA)

Ivan Chan created TEIID-2917: -------------------------------- Summary: Cassandra: update to cassandra driver to version 2.X Key: TEIID-2917 URL: https://issues.jboss.org/browse/TEIID-2917 Project: Teiid Issue Type: Enhancement Components: JDBC Driver Affects Versions: 8.7 Environment: Teiid with Cassandra Reporter: Ivan Chan Assignee: Steven Hawkins The current cassandra driver is 2.X and API has been changed in this new driver. However, Teiid is using Cassandra driver 1.0.4. It will be nice if you guys can upgrade your cassandra driver version 2.X in the next release. Thanks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2916) HIVE2: Teiid didn't translate the SQL correctly for numeric field

by Ivan Chan (JIRA)

Ivan Chan created TEIID-2916: -------------------------------- Summary: HIVE2: Teiid didn't translate the SQL correctly for numeric field Key: TEIID-2916 URL: https://issues.jboss.org/browse/TEIID-2916 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.7 Environment: HIVE2 with Teiid Reporter: Ivan Chan Assignee: Steven Hawkins Teiid didn't translate the SQL correctly for numeric field. It uses identifier "decimal" in the SQL which is not supported by the driver. Original Query: select "store_sales", "store_state", "store_country" from "Impala"."sales_new" where "store_sales" between 1.5 and 10 limit 1000 After Translation (Teiid): SELECT g_0.store_sales AS c_0, g_0.store_state AS c_ 1, g_0.store_country AS c_2 FROM sales_new g_0 WHERE cast(g_0.store_sales AS decimal) >= 1.5 AND cast(g_0.store_sales AS decimal) <= 10 LIMIT 1000 "decimal" is not supported identifier in HIVE driver: Encountered: IDENTIFIER Expected: BIGINT, BOOLEAN, DATE, DATETIME, REAL, FLOAT, INTEGER, SMALLINT, STRING, TIMESTAMP, TINYINT -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1070) Create Amazon SimpleDB Connector

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-1070?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-1070: ------------------------------------- I think the assumption made here can be modified. It was assumed that every domain's item is multi-valued attribute, thus trying to return concatenated string to represent the multiple values. I suggest, we flip that assumption, where when scanning domain's first item, if we find that item has multi-valued create it as string[], otherwise as plain string. This will save from creating these concat of strings in select and insert etc. Also note that when the item is multi-valued, the calling semantics are little different, you have to use "every" or "intersection" keyword, as defined here http://docs.aws.amazon.com/AmazonSimpleDB/latest/DeveloperGuide/UsingSele..., I do not think I saw that in the code. * IN criteria support should be added, as it is supported in the query syntax * SORT support should be added * COUNT STAR support can be added The one question I have is how to support "update" of array values in Teiid? I do not think Teiid supports that yet, does it? > Create Amazon SimpleDB Connector > --------------------------------- > > Key: TEIID-1070 > URL: https://issues.jboss.org/browse/TEIID-1070 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: John Doyle > Assignee: Ramesh Reddy > Fix For: 8.7 > > > We need connectivity to Amazon SimpleDB. This should be accomplished through a dedicated connector. > Simple DB presents a few challenges as a Teiid source as it is more like a spreadsheet than a database. Simple DB "Domains' are like individual worksheets and contain any number of items. Items however can have any number of attributes, and the attributes do not have to be the same for ever item. So in a single Domain you can have an item with the attributes Size and Color, and another item with the attributes Color and ExpirationDate. This presents both modeling issues and SQL execution issues. None of them are insurmountable, but users will have to understand the issues and design their integration around them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2709) Quickstart - drools-integration uses drools 5 instead of drools 6

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2709?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2709: ------------------------------------ This quick start needs a different approach, because when trying to use drools 6, it requires soo many dependencies. That it almost seems better to design this quick start based on Teiid being deployed to drools installed server. When drools 5 was used, it used the jar-with-dependencies jar, but now with the use of modules, it will require a lot of setup. So now taking the approach of installing drools. > Quickstart - drools-integration uses drools 5 instead of drools 6 > ------------------------------------------------------------------- > > Key: TEIID-2709 > URL: https://issues.jboss.org/browse/TEIID-2709 > Project: Teiid > Issue Type: Enhancement > Components: Quick Starts > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > > The drools-integration quick start uses drools 5, instead of drools 6. > And its not a matter of swapping out the versions due to api changes drools 6. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2709) Quickstart - drools-integration uses drools 5 instead of drools 6

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2709?page=com.atlassian.jira.plugin... ] Work on TEIID-2709 stopped by Van Halbert. > Quickstart - drools-integration uses drools 5 instead of drools 6 > ------------------------------------------------------------------- > > Key: TEIID-2709 > URL: https://issues.jboss.org/browse/TEIID-2709 > Project: Teiid > Issue Type: Enhancement > Components: Quick Starts > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > > The drools-integration quick start uses drools 5, instead of drools 6. > And its not a matter of swapping out the versions due to api changes drools 6. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2914) Infinispan Connector didn't have the advanced searching option exposed

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2914?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2914: ------------------------------------ Its easy to remove, but is it the better option. I was thinking, that in this case, the resource adapter is like a jdbc driver, you ask it what's its capabilities are. The configuration of the resource adapter is there, then why not add what it supports too. The translator will check for the capability from the Cache (i.e., cache wrapper) and then performs the appropriate type of query. I really think, the function of querying (e.g. by key, lucene or DSL) should be moved into the cache wrapper, so the translator doesn't need to control how its performed. And with the addition of DSL support and the dependencies on google protobuf's, if we don't segment this more, there will be no separation between the translator and resource adapter. > Infinispan Connector didn't have the advanced searching option exposed > ---------------------------------------------------------------------- > > Key: TEIID-2914 > URL: https://issues.jboss.org/browse/TEIID-2914 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7, 8.7.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > > The advanced searching option (i.e, lucene searching) that is defined in the .rar was not being picked up in the connector. > Also, it was incorrectly defined on the translator, because the translator cannot override how the cache is configured. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2014