December 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3855) To help with debugging data source issues, return back to the calling session the data source error

by Van Halbert (JIRA)

Van Halbert created TEIID-3855: ---------------------------------- Summary: To help with debugging data source issues, return back to the calling session the data source error Key: TEIID-3855 URL: https://issues.jboss.org/browse/TEIID-3855 Project: Teiid Issue Type: Feature Request Components: Common Affects Versions: 8.12.3 Reporter: Van Halbert Assignee: Steven Hawkins When a developer is seeing query issues, would like to have a more informative message when a data source cannot be accessed. The data source error message should be returned back to the calling session, and back to the calling application to assist in debugging issues. This would improve usability with out having to go to the server log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3853) BatchedUpdateNode should not report requires transaction true

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3853?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3853. ----------------------------------- Resolution: Done Updated requires transaction to return null. > BatchedUpdateNode should not report requires transaction true > ------------------------------------------------------------- > > Key: TEIID-3853 > URL: https://issues.jboss.org/browse/TEIID-3853 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 8.1 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.13, 8.12.x > > > We expect BatchedUpdates to be executed atomicly at the source, so the node should not report a transaction as being required. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3853) BatchedUpdateNode should not report requires transaction true

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3853?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3853: ---------------------------------- Summary: BatchedUpdateNode should not report requires transaction true (was: BatchedUpdateNode should report requires transaction false) > BatchedUpdateNode should not report requires transaction true > ------------------------------------------------------------- > > Key: TEIID-3853 > URL: https://issues.jboss.org/browse/TEIID-3853 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 8.1 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.13, 8.12.x > > > We expect BatchedUpdates to be executed atomicly at the source, so the node should not report a transaction as being required. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3854) Impala translator - ORDER BY clause using incorrect columns when not in SELECT list

by Don Krapohl (JIRA)

Don Krapohl created TEIID-3854: ---------------------------------- Summary: Impala translator - ORDER BY clause using incorrect columns when not in SELECT list Key: TEIID-3854 URL: https://issues.jboss.org/browse/TEIID-3854 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 8.12.2, 8.12.1 Environment: Ubuntu Trusty on AWS Reporter: Don Krapohl Assignee: Steven Hawkins We have a scenario in which users want to see month and day names but the data should be sorted by month and day NUMBER. The translated query comes back sorted the wrong column. Oddly in the ORDER clause the translator uses the month name column alias when we specify the month number, day name when we specify day number. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3853) BatchedUpdateNode should report requires transaction false

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3853: ------------------------------------- Summary: BatchedUpdateNode should report requires transaction false Key: TEIID-3853 URL: https://issues.jboss.org/browse/TEIID-3853 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 8.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.13, 8.12.x We expect BatchedUpdates to be executed atomicly at the source, so the node should not report a transaction as being required. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3849) Writes using Cassandra connector are very slow

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3849?page=com.atlassian.jira.plugin... ] Work on TEIID-3849 started by Steven Hawkins. --------------------------------------------- > Writes using Cassandra connector are very slow > ---------------------------------------------- > > Key: TEIID-3849 > URL: https://issues.jboss.org/browse/TEIID-3849 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Pranav K > Assignee: Steven Hawkins > Fix For: 9.0 > > > The connector seems to execute the insert queries one by one rather than using batched approach, also the API used is the synchronous one instead of the future based async API [session.executeAsync()] > Cassandra writes are generally very fast, but it was noted in one scenario that on a single node Cassandra setup inserting a set 50k records and 3 columns took more than 25 mins. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3852) Teiid JDBC Driver SocketPing can not disable

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3852?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3852. ----------------------------------- Fix Version/s: (was: 9.x) Resolution: Rejected In initialize: PropertiesUtils.setBeanProperties(this, info, "org.teiid.sockets"); //$NON-NLS-1$ Sets properties reflectively. For a variety of reasons we split off the low level transport properties (see teiid-client-settings.orig.properties in the resources) from those that are configured via the url. > Teiid JDBC Driver SocketPing can not disable > -------------------------------------------- > > Key: TEIID-3852 > URL: https://issues.jboss.org/browse/TEIID-3852 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Driver > Affects Versions: 9.x > Reporter: Kylin Soong > Assignee: Kylin Soong > > Today I debug client code have found that JDBC Driver SocketPing can not be disabled, there are some logic hints SocketPing should be configurable, but it seems not completed, some logic snippets in _org.teiid.net.socket.SocketServerConnectionFactory_: > {code} > private boolean disablePing; > public void setDisablePing(boolean disable) { > this.disablePing = disable; > } > public void initialize(Properties info){ > ... > if (disablePing){ > return; > } > this.pingTimer = new Timer("SocketPing", true); > this.pingTimer.schedule(new TimerTask()); > } > {code} > Note that, even the setDisablePing() exist, but it never be invoked, so I think whether we can add some logic that let JDBC Driver has ability to disable SocketPing? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3852) Teiid JDBC Driver SocketPing can not disable

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-3852?page=com.atlassian.jira.plugin... ] Kylin Soong updated TEIID-3852: ------------------------------- Description: Today I debug client code have found that JDBC Driver SocketPing can not be disabled, there are some logic hints SocketPing should be configurable, but it seems not completed, some logic snippets in _org.teiid.net.socket.SocketServerConnectionFactory_: {code} private boolean disablePing; public void setDisablePing(boolean disable) { this.disablePing = disable; } public void initialize(Properties info){ ... if (disablePing){ return; } this.pingTimer = new Timer("SocketPing", true); this.pingTimer.schedule(new TimerTask()); } {code} Note that, even the setDisablePing() exist, but it never be invoked, so I think whether we can add some logic that let JDBC Driver has ability to disable SocketPing? was: Today I debug client code have found that JDBC Driver SocketPing can not be disabled, there are some logic hints SocketPing should be configurable, but it seems not completed, some logic snippets in _org.teiid.net.socket.SocketServerConnectionFactory_: {code} private boolean disablePing; public void setDisablePing(boolean disable) { this.disablePing = disable; } public void initialize(Properties info){ ... if (disablePing){ return; } this.pingTimer = new Timer("SocketPing", true); this.pingTimer.schedule(new TimerTask()); } {code} Note that, even the setDisablePing() exeist, but it never be invoked, so I think whether we can add some logic that let JDBC Driver has ability to disable SocketPing? > Teiid JDBC Driver SocketPing can not disable > -------------------------------------------- > > Key: TEIID-3852 > URL: https://issues.jboss.org/browse/TEIID-3852 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Driver > Affects Versions: 9.x > Reporter: Kylin Soong > Assignee: Kylin Soong > Fix For: 9.x > > > Today I debug client code have found that JDBC Driver SocketPing can not be disabled, there are some logic hints SocketPing should be configurable, but it seems not completed, some logic snippets in _org.teiid.net.socket.SocketServerConnectionFactory_: > {code} > private boolean disablePing; > public void setDisablePing(boolean disable) { > this.disablePing = disable; > } > public void initialize(Properties info){ > ... > if (disablePing){ > return; > } > this.pingTimer = new Timer("SocketPing", true); > this.pingTimer.schedule(new TimerTask()); > } > {code} > Note that, even the setDisablePing() exist, but it never be invoked, so I think whether we can add some logic that let JDBC Driver has ability to disable SocketPing? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3852) Teiid JDBC Driver SocketPing can not disable

by Kylin Soong (JIRA)

Kylin Soong created TEIID-3852: ---------------------------------- Summary: Teiid JDBC Driver SocketPing can not disable Key: TEIID-3852 URL: https://issues.jboss.org/browse/TEIID-3852 Project: Teiid Issue Type: Quality Risk Components: JDBC Driver Affects Versions: 9.x Reporter: Kylin Soong Assignee: Kylin Soong Fix For: 9.x Today I debug client code have found that JDBC Driver SocketPing can not be disabled, there are some logic hints SocketPing should be configurable, but it seems not completed, some logic snippets in _org.teiid.net.socket.SocketServerConnectionFactory_: {code} private boolean disablePing; public void setDisablePing(boolean disable) { this.disablePing = disable; } public void initialize(Properties info){ ... if (disablePing){ return; } this.pingTimer = new Timer("SocketPing", true); this.pingTimer.schedule(new TimerTask()); } {code} Note that, even the setDisablePing() exeist, but it never be invoked, so I think whether we can add some logic that let JDBC Driver has ability to disable SocketPing? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3818) Issues with ODBC metadata foreign key queries

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3818?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3818: --------------------------------- Fix Version/s: 8.7.2.6_2 8.7.6 > Issues with ODBC metadata foreign key queries > --------------------------------------------- > > Key: TEIID-3818 > URL: https://issues.jboss.org/browse/TEIID-3818 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 8.4 > Environment: Most likely not OS / hardware dependent. > Reporter: Dave Nicodemus > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.7.2.6_2, 8.12.2, 8.13, 8.7.6 > > > The current foreign key handling should return imported key, but instead returns exported keys. > When exported keys are asked for an exception is thrown: > While attempting to use Client Microsoft's Power BI desktop using ODBC connecting to Teiid Embedded server using VDB with metadata tags. > Received the following errors : > {code} > [36.864]ERROR from backend during send_query: 'SERROR' > [36.865]ERROR from backend during send_query: 'C50000' > [36.869]ERROR from backend during send_query: 'MTEIID31100 Parsing error: Encountered "('ScottTestMart' AS [*]name[*]) as" at line 1, column 33. > Was expecting: "string" | "varbinary" | "varchar" | "boolean" | "byte" | "tinyint" | "short" | "smallint" | "char" | "integer" ...' > [36.875]ERROR from backend during send_query: 'Dorg.teiid.jdbc.TeiidSQLException: TEIID31100 Parsing error: Encountered "('ScottTestMart' AS [*]name[*]) as" at line 1, column 33. > Was expecting: "string" | "varbinary" | "varchar" | "boolean" | "byte" | "tinyint" | "short" | "smallint" | "char" | "integer" ...' > [37.397]STATEMENT ERROR: func=PGAPI_ForeignKeys, desc='', errnum=1, errmsg='PGAPI_ForeignKeys query error' > {code} > Due to this query being generated by the BI tool : > {code} > 'select 'ScottTestMart'::name as PKTABLE_CAT, > n2.nspname as PKTABLE_SCHEM, > c2.relname as PKTABLE_NAME, > a2.attname as PKCOLUMN_NAME, > 'ScottTestMart'::name as FKTABLE_CAT, > n1.nspname as FKTABLE_SCHEM, > c1.relname as FKTABLE_NAME, > a1.attname as FKCOLUMN_NAME, > i::int2 as KEY_SEQ, > case ref.confupdtype > when 'c' then 0::int2 > when 'n' then 2::int2 > when 'd' then 4::int2 > when 'r' then 1::int2 > else 3::int2 > end as UPDATE_RULE, > case ref.confdeltype > when 'c' then 0::int2 > when 'n' then 2::int2 > when 'd' then 4::int2 > when 'r' then 1::int2 > else 3::int2 > end as DELETE_RULE, > ref.conname as FK_NAME, > cn.conname as PK_NAME, > case > when ref.condeferrable then > case > when ref.condeferred then 5::int2 > else 6::int2 > end > else 7::int2 > end as DEFERRABLITY > from > ((((((( (select cn.oid, conrelid, conkey, confrelid, confkey, > generate_series(array_lower(conkey, 1), array_upper(conkey, 1)) as i, > confupdtype, confdeltype, conname, > condeferrable, condeferred > from pg_catalog.pg_constraint cn, > pg_catalog.pg_class c, > pg_catalog.pg_namespace n > where contype = 'f' > and confrelid = c.oid > and relname = 'Categories' > and n.oid = c.relnamespace > and n.nspname = 'ScottTestMart' > ) ref > inner join pg_catalog.pg_class c1 > on c1.oid = ref.conrelid) > inner join pg_catalog.pg_namespace n1 > on n1.oid = c1.relnamespace) > inner join pg_catalog.pg_attribute a1 > on a1.attrelid = c1.oid > and a1.attnum = conkey[i]) > inner join pg_catalog.pg_class c2 > on c2.oid = ref.confrelid) > inner join pg_catalog.pg_namespace n2 > on n2.oid = c2.relnamespace) > inner join pg_catalog.pg_attribute a2 > on a2.attrelid = c2.oid > and a2.attnum = confkey[i]) > left outer join pg_catalog.pg_constraint cn > on cn.conrelid = ref.confrelid > and cn.contype = 'p') > order by ref.oid, ref.i' > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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 December 2015