August 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3527) Missing ODBC port number in the log during shutdown

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3527?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3527: ------------------------------------------------ Filip Elias <felias(a)redhat.com> changed the Status of [bug 1231613|https://bugzilla.redhat.com/show_bug.cgi?id=1231613] from VERIFIED to CLOSED > Missing ODBC port number in the log during shutdown > --------------------------------------------------- > > Key: TEIID-3527 > URL: https://issues.jboss.org/browse/TEIID-3527 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1.6_2 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Priority: Trivial > Fix For: 8.11 > > > There is missing ODBC port number in the log during shutdown: > INFO [org.teiid.RUNTIME] (MSC service thread 1-1) TEIID50039 Teiid JDBC - Name = jdbc, Host = localhost, Port = 31000 has been shutdown. > INFO [org.teiid.RUNTIME] (MSC service thread 1-3) TEIID50040 Teiid ODBC - Name = localhost, Host = 35432, Port = {2} has been shutdown. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4040) Representation of OData error does not contain error code.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4040?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4040: ------------------------------------------------ Filip Elias <felias(a)redhat.com> changed the Status of [bug 1316470|https://bugzilla.redhat.com/show_bug.cgi?id=1316470] from VERIFIED to CLOSED > Representation of OData error does not contain error code. > ---------------------------------------------------------- > > Key: TEIID-4040 > URL: https://issues.jboss.org/browse/TEIID-4040 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Juraj Duráni > Assignee: Ramesh Reddy > Fix For: 9.0, 8.12.5 > > > JSON: > *URL:* http://localhost:8080/odata4/olingo_basic/Source/SimpleTableView/?$filter... > *Actual result:* \{"error":\{"code":null,"message":"TEIID30492 Non-comparable expression of type object cannot be used in comparison: g4.clobval = ?."\}\} > *Expected result:* "code":30492 > XML (in this case OData returns HTTP status code instead of error code): > *URL:* http://localhost:8080/odata4/olingo_basic/Source/SimpleTableView/?$filter... > *Result:* > {code:xml} > <error> > <code>500</code> > <message>TEIID30492 Non-comparable expression of type object cannot be used in comparison: g1.clobval = ?.</message> > </error> > {code} > *Expected result:* > {code:xml}<code>:30492</code>{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4087) OData - Math function round doesn't accept decimal number as parameter

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4087?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4087: ------------------------------------------------ Filip Elias <felias(a)redhat.com> changed the Status of [bug 1318435|https://bugzilla.redhat.com/show_bug.cgi?id=1318435] from VERIFIED to CLOSED > OData - Math function round doesn't accept decimal number as parameter > ---------------------------------------------------------------------- > > Key: TEIID-4087 > URL: https://issues.jboss.org/browse/TEIID-4087 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Michal Sanitrak > Assignee: Ramesh Reddy > Labels: Alpha3 > Fix For: 9.0, 8.12.5 > > > Reference service which supports OData V4: > *ULR:* http://services.odata.org/V4/Northwind/Northwind.svc/Employees/?$filter=E... > *Result:* Employee with ID 4 > *URL:* http://localhost:8080/odata4/olingo_basic/Source/SimpleTableView/?$filter... > *Actual result:* {"error": {"code": null, "message": "TEIID30558 Error converting parameter number 1 with value \"4,2\" of class java.math.BigDecimal to expected type integer." }} > *Expected result:* Entity with intkey 4 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4090) Issue with entitysets/properties ending in auth or token

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4090?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4090: ------------------------------------------------ Filip Elias <felias(a)redhat.com> changed the Status of [bug 1346025|https://bugzilla.redhat.com/show_bug.cgi?id=1346025] from VERIFIED to CLOSED > Issue with entitysets/properties ending in auth or token > -------------------------------------------------------- > > Key: TEIID-4090 > URL: https://issues.jboss.org/browse/TEIID-4090 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.12 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Blocker > Labels: Final > Fix For: 9.0, 8.12.5 > > > To handle oauth, we are check for uri.endsWith("auth") || uri.endsWith("token") - however valid uris can end with those characters as well. An ioexception will be thrown instead of seeing the expected results - we also need to not simply throw an ioexception in ODataServlet as there is no server log of the exception and the client sees a 500 error. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4038) OData returns bad number of entities with $count and $expand

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4038?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4038: ------------------------------------------------ Filip Elias <felias(a)redhat.com> changed the Status of [bug 1316468|https://bugzilla.redhat.com/show_bug.cgi?id=1316468] from VERIFIED to CLOSED > OData returns bad number of entities with $count and $expand > ------------------------------------------------------------ > > Key: TEIID-4038 > URL: https://issues.jboss.org/browse/TEIID-4038 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Juraj Duráni > Assignee: Ramesh Reddy > Labels: Alpha3 > Fix For: 9.0, 8.12.5 > > > *URL:* http://localhost:8080/odata4/olingo_basic/Source/Customers/?$count=true&$... > *Expected count:* 4 > *Actual count:* 9 > Similar behavior with $filter - http://localhost:8080/odata4/olingo_basic/Source/Customers/?$count=true&$... > OData should return only count of Customer entities. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4114) Expanding logic in the format conversion for parsing and formatting of dates

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4114?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4114: ------------------------------------------------ Filip Elias <felias(a)redhat.com> changed the Status of [bug 1323312|https://bugzilla.redhat.com/show_bug.cgi?id=1323312] from VERIFIED to CLOSED > Expanding logic in the format conversion for parsing and formatting of dates > ---------------------------------------------------------------------------- > > Key: TEIID-4114 > URL: https://issues.jboss.org/browse/TEIID-4114 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.11 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5, 8.7.5.6_2 > > > Java documentation isn't explicit https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html regarding date/time formats. > The format string is not enforced on the parsing side, so any hour format will accept any value. However oracle's behavior is different - if you specify HH vs HH24, then 13-23 is disallowed. > Need to address this by expanding the logic in the format conversion to account for the difference between parsing and formatting. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3816) Informix translator - <> ALL is translated as NOT IN - this statement seem to not work in Infromix

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3816?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3816: ------------------------------------------------ Filip Elias <felias(a)redhat.com> changed the Status of [bug 1279473|https://bugzilla.redhat.com/show_bug.cgi?id=1279473] from VERIFIED to CLOSED > Informix translator - <> ALL is translated as NOT IN - this statement seem to not work in Infromix > -------------------------------------------------------------------------------------------------- > > Key: TEIID-3816 > URL: https://issues.jboss.org/browse/TEIID-3816 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.2.6_2 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > Query: > {code:sql} > SELECT INTKEY, BOOLEANVALUE FROM BQT1.SMALLA WHERE BOOLEANVALUE <> ALL (SELECT BOOLEANVALUE FROM BQT1.SMALLA WHERE INTKEY = 40) > {code} > Source-specific command: > {code:sql} > SELECT g_0.IntKey, g_0.BooleanValue FROM Source.SmallA AS g_0 WHERE g_0.BooleanValue NOT IN (SELECT g_1.BooleanValue FROM Source.SmallA AS g_1 WHERE g_1.IntKey = 40) > {code} > *Note: boolean value for row where Intkey = 40 is false.* > Expected result: > |intkey|booleanvalue| > |1|true| > |...|...| > Actual result: > |intkey|booleanvalue| > |0|false| > |...|...| > This seems to be an Informix issue as neither '<> ALL' nor 'NOT IN' works. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4134) Oracle requires column alias list when using recursive CTE

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4134?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4134: ------------------------------------------------ Filip Elias <felias(a)redhat.com> changed the Status of [bug 1326833|https://bugzilla.redhat.com/show_bug.cgi?id=1326833] from VERIFIED to CLOSED > Oracle requires column alias list when using recursive CTE > ---------------------------------------------------------- > > Key: TEIID-4134 > URL: https://issues.jboss.org/browse/TEIID-4134 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.12.x > Reporter: Andrej Šmigala > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5 > > > Running a recursive common table expression query against an Oracle source removes the columns alias list, which causes {noformat}ORA-32039: recursive WITH clause must have column alias list{noformat} > Note that there might be an issue with some specific versions of Oracle 11g, the columns alias list is required 11.2.0.4, but might not be in 11.2.0.2. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4128) Domain mode - full-ha profile does not disable SSL for ODBC

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4128?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4128: ------------------------------------------------ Filip Elias <felias(a)redhat.com> changed the Status of [bug 1323563|https://bugzilla.redhat.com/show_bug.cgi?id=1323563] from VERIFIED to CLOSED > Domain mode - full-ha profile does not disable SSL for ODBC > ----------------------------------------------------------- > > Key: TEIID-4128 > URL: https://issues.jboss.org/browse/TEIID-4128 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 8.12.5 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.12.5 > > > "full-ha" profile in the domain mode is missing default SSL configuration for ODBC transport: > <ssl mode="disabled"/> > This prevents OOB user:password authentication for ODBC transport. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4283) External Materialization interleaving loads SYSADMIN.loadMatView

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4283?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4283: ------------------------------------------------ Filip Elias <felias(a)redhat.com> changed the Status of [bug 1348466|https://bugzilla.redhat.com/show_bug.cgi?id=1348466] from VERIFIED to CLOSED > External Materialization interleaving loads SYSADMIN.loadMatView > ---------------------------------------------------------------- > > Key: TEIID-4283 > URL: https://issues.jboss.org/browse/TEIID-4283 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.12.5 > Reporter: Jan Stastny > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 9.1, 8.12.5, 9.0.1 > > Attachments: jdg-log.txt > > > There is a possibility of two concurrent loads of single materialized view when using SYSADMIN.loadMatView function. I observed the issue while: > # Waiting for ttl-driven reload and in right time I triggered another load explicitly by invoking the loadMatView function. > # Invoking SYSADMIN.loadMatView function multiple times in quick succession. > The view definition: > {code:sql} > CREATE VIEW external_long_ttl ( > customer_id integer NOT NULL, > total_amount integer > ) OPTIONS (MATERIALIZED 'TRUE', UPDATABLE 'FALSE', > MATERIALIZED_TABLE 'Source.JSTASTNY.dv_matviews_mat_view', > "teiid_rel:ALLOW_MATVIEW_MANAGEMENT" 'true', > "teiid_rel:MATVIEW_STATUS_TABLE" 'Source.JSTASTNY.dv_matviews_statustable', > "teiid_rel:ON_VDB_START_SCRIPT" 'MERGE INTO dv_matviews_check_table(id,vdb_create) SELECT id, vdb_create+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';', > "teiid_rel:ON_VDB_DROP_SCRIPT" 'MERGE INTO dv_matviews_check_table(id,vdb_drop) SELECT id, vdb_drop+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';', > "teiid_rel:MATVIEW_LOAD_SCRIPT" 'INSERT INTO dv_matviews_mat_view_stage(customer_id,total_amount) SELECT CONVERT(c.id,integer) AS customer_id, CONVERT(SUM(o.amount),integer) AS total_amount FROM dv_matviews_customers c INNER JOIN dv_matviews_orders o ON c.id = o.customer_id GROUP BY c.id;', > "teiid_rel:MATVIEW_BEFORE_LOAD_SCRIPT" 'exec Source.native(''truncate table ${db.table.prefix}dv_matviews_mat_view_stage'');MERGE INTO dv_matviews_check_table(id,before_load) SELECT id, before_load+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';', > "teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'exec Source.native(''RENAME TABLE ${db.table.prefix}dv_matviews_mat_view_stage TO ${db.table.prefix}dv_matviews_mat_view_temp'');exec Source.native(''RENAME TABLE ${db.table.prefix}dv_matviews_mat_view TO ${db.table.prefix}dv_matviews_mat_view_stage'');exec Source.native(''RENAME TABLE ${db.table.prefix}dv_matviews_mat_view_temp TO ${db.table.prefix}dv_matviews_mat_view'');MERGE INTO dv_matviews_check_table(id,after_load) SELECT id, after_load+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';', > "teiid_rel:MATVIEW_ONERROR_ACTION" 'WAIT', > "teiid_rel:MATVIEW_TTL" 20000) > AS SELECT CONVERT(c.id,integer) AS customer_id, CONVERT(SUM(o.amount),integer) AS total_amount FROM dv_matviews_customers c INNER JOIN dv_matviews_orders o ON c.id = o.customer_id GROUP BY c.id; > {code} > Query to explicitly load the view: > {code:sql} > exec SYSADMIN.loadMatView(schemaName=>'View',viewname=>'external_long_ttl', invalidate=>'true') > {code} > I attached a log which starts with ttl-driven load, then the explicit load is performed. The issue noticed is in teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT , where primary and staging tables are being swapped. The second load (explicit) can't find the original table, as the ttl-driven load had already renamed it. > But this situation of two concurrent loads should never occur. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 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 August 2016