April 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2941) Add documentation that explains expected usage patterns

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2941?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2941: ------------------------------------ Demonstrating in a quick start would be good. But shouldn't there be something documented that leads them to it? > Add documentation that explains expected usage patterns > ------------------------------------------------------- > > Key: TEIID-2941 > URL: https://issues.jboss.org/browse/TEIID-2941 > Project: Teiid > Issue Type: Enhancement > Components: Documentation > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Optional > > Would like to see documentation added to explains certain data source usage patterns for which cannot be explained just by using the data source. Example is: > How to access a JSON REST service: > You read JSON using file or web service translator, then use the JSONToXML function, to convert to XML, then use the XMLTABLE function to parse. > This isn't straight forward in the documentation to a novice. -- 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

1
0
0 / 0

[JBoss JIRA] (TEIID-2937) Change Apache POI version to 3.10

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2937?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2937: ------------------------------------- Van, the integration BOM defines the version as 3.10, which is wrong. That version is not available anywhere. It should have been 3.10-FINAL. Can you work the team to correct it? > Change Apache POI version to 3.10 > --------------------------------- > > Key: TEIID-2937 > URL: https://issues.jboss.org/browse/TEIID-2937 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.7 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Fix For: 8.7.1, 8.8 > > > Upgrade the Apache POI version used in accessing Excel file to use POI 3.10. -- 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

1
0
0 / 0

[JBoss JIRA] (TEIID-2937) Change Apache POI version to 3.10

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2937?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2937: --------------------------------------- It looks like the BOM references 3.10, but should reference 3.10-FINAL. Once that update is made, it looks like we have some additional steps as the unit tests fail. > Change Apache POI version to 3.10 > --------------------------------- > > Key: TEIID-2937 > URL: https://issues.jboss.org/browse/TEIID-2937 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.7 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Fix For: 8.7.1, 8.8 > > > Upgrade the Apache POI version used in accessing Excel file to use POI 3.10. -- 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

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 resolved TEIID-2916. --------------------------------- Labels: Teiid alpha1 (was: Teiid) Resolution: Done Removed support for data type "decimal", "blob", "object" so that the CAST will not be used with decimal data type if numeric field needs conversion. "double" will be used instead. > 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: Sub-task > Components: Misc. Connectors > Affects Versions: 8.6 > Environment: HIVE2 with Teiid > Reporter: Ivan Chan > Assignee: Ramesh Reddy > Labels: Teiid, alpha1 > Fix For: 8.7.1, 8.8 > > > 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

1
0
0 / 0

[JBoss JIRA] (TEIID-2647) Add an impala translator

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2647?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2647. --------------------------------- Labels: alpha1 (was: ) Resolution: Done Added a new impala translator which derives from same code base as the hive translator. Modifications from Hive translator are * data type support * function support * removed few capabilities like enhanced aggregation functions, array support * added capabilities for having clause, with clause, row offset Looked through Cloudera's SQL reference once for any more features to implemented, but they JOIN capability seems to be similar to Hive. Any other issues will be dealt as individual separate issues in terms of capabilities missing or different. > Add an impala translator > ------------------------ > > Key: TEIID-2647 > URL: https://issues.jboss.org/browse/TEIID-2647 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Labels: alpha1 > Fix For: 8.7.1, 8.8 > > > Impala offers an alternative to Hive SQL access: > http://blog.cloudera.com/blog/2012/10/cloudera-impala-real-time-queries-i... -- 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

1
0
0 / 0

[JBoss JIRA] (TEIID-2941) Add documentation that explains expected usage patterns

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2941?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2941: --------------------------------------- Van can you add this as a quick start? > Add documentation that explains expected usage patterns > ------------------------------------------------------- > > Key: TEIID-2941 > URL: https://issues.jboss.org/browse/TEIID-2941 > Project: Teiid > Issue Type: Enhancement > Components: Documentation > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Optional > > Would like to see documentation added to explains certain data source usage patterns for which cannot be explained just by using the data source. Example is: > How to access a JSON REST service: > You read JSON using file or web service translator, then use the JSONToXML function, to convert to XML, then use the XMLTABLE function to parse. > This isn't straight forward in the documentation to a novice. -- 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

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 updated TEIID-2916: -------------------------------- Fix Version/s: 8.8 > 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: Sub-task > Components: Misc. Connectors > Affects Versions: 8.6 > Environment: HIVE2 with Teiid > Reporter: Ivan Chan > Labels: Teiid > Fix For: 8.7.1, 8.8 > > > 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

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 reassigned TEIID-2916: ----------------------------------- Assignee: Ramesh Reddy > 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: Sub-task > Components: Misc. Connectors > Affects Versions: 8.6 > Environment: HIVE2 with Teiid > Reporter: Ivan Chan > Assignee: Ramesh Reddy > Labels: Teiid > Fix For: 8.7.1, 8.8 > > > 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

1
0
0 / 0

[JBoss JIRA] (TEIID-2647) Add an impala translator

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2647?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2647: -------------------------------- Fix Version/s: 8.8 > Add an impala translator > ------------------------ > > Key: TEIID-2647 > URL: https://issues.jboss.org/browse/TEIID-2647 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 8.7.1, 8.8 > > > Impala offers an alternative to Hive SQL access: > http://blog.cloudera.com/blog/2012/10/cloudera-impala-real-time-queries-i... -- 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

1
0
0 / 0

[JBoss JIRA] (TEIID-2940) SQL naming issue with several layers of inline views

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2940?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2940. ----------------------------------- Resolution: Done Corrected the alias generator to use the inline view names prior to aliasing to correct the upper layers. > SQL naming issue with several layers of inline views > ---------------------------------------------------- > > Key: TEIID-2940 > URL: https://issues.jboss.org/browse/TEIID-2940 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.8 > > > Several layers of inline views in a source query can cause the alias generation logic to use improper names for higher level symbols resulting in invalid source sql. -- 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

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2014