September 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3692) Impala/Hive string literals

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3692?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3692: --------------------------------- Fix Version/s: 8.7.5 > Impala/Hive string literals > --------------------------- > > Key: TEIID-3692 > URL: https://issues.jboss.org/browse/TEIID-3692 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Don Krapohl > Assignee: Steven Hawkins > Fix For: 8.12, 8.11.4, 8.7.5 > > > The Hive/Impala logic does not account for the source using c-style strings and will currently for string literals in the source sql use ansi style instead. Bind values are unaffected. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3698) non-selectable columns will cause OData failures

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3698?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3698: --------------------------------- Fix Version/s: 8.7.5 > non-selectable columns will cause OData failures > ------------------------------------------------ > > Key: TEIID-3698 > URL: https://issues.jboss.org/browse/TEIID-3698 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 8.12, 8.7.5 > > > An odata table/view with a non-selectable column will return an error if it is returned as an odata entity without the $select option to exclude the non-selectable column. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3628) Server socket setting issues

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3628?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3628: --------------------------------- Fix Version/s: 8.7.5 > Server socket setting issues > ---------------------------- > > Key: TEIID-3628 > URL: https://issues.jboss.org/browse/TEIID-3628 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12, 8.11.3, 8.7.5 > > > The bootstrap settings need to be for the child rather than the parent. Also we should enable tcpNoDelay so that small messages are immediately sent. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3635) Auto configuration of buffermanager values can be incorrect

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3635?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3635: --------------------------------- Fix Version/s: 8.7.5 > Auto configuration of buffermanager values can be incorrect > ----------------------------------------------------------- > > Key: TEIID-3635 > URL: https://issues.jboss.org/browse/TEIID-3635 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.12, 8.11.3, 8.7.5 > > > If the heap size is significantly larger than 2 gb, such that the auto computed value for the max reserve is larger than 2 gb and the memory buffer size is also auto calculated, then the computed values for max reserve and max memory buffer can be significantly different than expected. At worst this results in the max memory buffer size of 0, which just default the buffer to being accessible by a single thread. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3662) IN predicate against a materialized/temp table index without an order by returns wrong results

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3662?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3662: --------------------------------- Fix Version/s: 8.7.5 > IN predicate against a materialized/temp table index without an order by returns wrong results > ---------------------------------------------------------------------------------------------- > > Key: TEIID-3662 > URL: https://issues.jboss.org/browse/TEIID-3662 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7 > Reporter: Tom Arnold > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 8.7.1.6_2, 8.12, 8.11.3, 8.7.5 > > > Seeing strange behavior when doing a simple select from {{SPATIAL_REF_SYS}}. > This works as expected: > {code} > select srid, proj4text from spatial_ref_sys where srid in (3875,4326); > srid | proj4text > ------+---------------------------------------------------------------------------------------------------------------- > 3875 | +proj=tmerc +lat_0=0 +lon_0=21 +k=1 +x_0=21500000 +y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs > 4326 | +proj=longlat +datum=WGS84 +no_defs > (2 rows) > {code} > Swapping the values in the IN causes only one row to be returned. > {code} > select srid, proj4text from spatial_ref_sys where srid in (4326,3875); > srid | proj4text > ------+------------------------------------- > 4326 | +proj=longlat +datum=WGS84 +no_defs > (1 row) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3671) filter on child table not working

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3671?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3671: --------------------------------- Fix Version/s: 8.7.5 > filter on child table not working > --------------------------------- > > Key: TEIID-3671 > URL: https://issues.jboss.org/browse/TEIID-3671 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Prashanthi Kairuppala > Assignee: Johnathon Lee > Priority: Critical > Fix For: 8.12, 8.11.4, 8.7.5 > > Attachments: parent_childTables.PNG > > > > Please find the screenshot attached which has id as a foreign key. when i give the url - //localhost:8080/odata/testVDB/sales('13')/sales_uk?$format=json, i get the results from sales_uk table which are having id=13. > > Now i am trying to apply a filter on this url, i am supposed to get results which are having id=13 and satisfy the filter condition, but this url blindly returns me data from sales_uk table which satisfy the filter condition. URL- //localhost:8080/odata/testVDB/sales('13')/sales_uk?$format=json&$filter=DISCOUNT eq '22' > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3483) Add an option to use DatabaseMetaData for hive/impala import

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3483?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3483: --------------------------------- Fix Version/s: 8.7.5 > Add an option to use DatabaseMetaData for hive/impala import > ------------------------------------------------------------ > > Key: TEIID-3483 > URL: https://issues.jboss.org/browse/TEIID-3483 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11, 8.7.5 > > > With minor modifications I've confirmed that hive .13 + can do an import using the standard databasemetadata logic. Also hive .12 with a .13 server seems to have an issue with the describe table statement such that the column types are null. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3640) Improper initialization when memory buffer size is over 2 GB.

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3640?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3640: --------------------------------- Fix Version/s: 8.7.5 > Improper initialization when memory buffer size is over 2 GB. > ------------------------------------------------------------- > > Key: TEIID-3640 > URL: https://issues.jboss.org/browse/TEIID-3640 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.12, 8.11.3, 8.7.5 > > > When the memory buffer size is over 2 GB, the initialization will not be correct as the number of segments is determined by a number that has been narrowed to an int. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2981) Add an OData query parameter that caches the resultset

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2981?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-2981: --------------------------------- Fix Version/s: 8.7.5 > Add an OData query parameter that caches the resultset > ------------------------------------------------------ > > Key: TEIID-2981 > URL: https://issues.jboss.org/browse/TEIID-2981 > Project: Teiid > Issue Type: Feature Request > Components: OData > Affects Versions: 8.7 > Reporter: John Muller > Assignee: Steven Hawkins > Priority: Minor > Labels: Caching > Fix For: 8.8, 8.7.5 > > > The Teiid caching guide indicates that the /*+ cache */ SQL hint is neccessary in order to cache results [1] . We would like two features added to the OData support: (1) to have a query parameter that basically injects the hint into the SQL statement run against the VDB and (2) a configuration setting that turns on OData resultset caching for all result sets smaller than some size (perhaps 256 as the default) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2981) Add an OData query parameter that caches the resultset

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2981?page=com.atlassian.jira.plugin... ] Johnathon Lee closed TEIID-2981. -------------------------------- Resolution: Done > Add an OData query parameter that caches the resultset > ------------------------------------------------------ > > Key: TEIID-2981 > URL: https://issues.jboss.org/browse/TEIID-2981 > Project: Teiid > Issue Type: Feature Request > Components: OData > Affects Versions: 8.7 > Reporter: John Muller > Assignee: Steven Hawkins > Priority: Minor > Labels: Caching > Fix For: 8.7.5, 8.8 > > > The Teiid caching guide indicates that the /*+ cache */ SQL hint is neccessary in order to cache results [1] . We would like two features added to the OData support: (1) to have a query parameter that basically injects the hint into the SQL statement run against the VDB and (2) a configuration setting that turns on OData resultset caching for all result sets smaller than some size (perhaps 256 as the default) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2015