January 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3943) Add schema name to oracle packaged objects

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3943?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3943: ---------------------------------- Issue Type: Bug (was: Task) > Add schema name to oracle packaged objects > ------------------------------------------ > > Key: TEIID-3943 > URL: https://issues.jboss.org/browse/TEIID-3943 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.13, 8.12.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > The fix for TEIID-3870 did not include the schema name - which could be need if the same package name exists in multiple schemas. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3943) Add schema name to oracle packaged objects

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3943?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3943. ----------------------------------- Resolution: Done Added the schema name if the name in source is meant to be qualified. > Add schema name to oracle packaged objects > ------------------------------------------ > > Key: TEIID-3943 > URL: https://issues.jboss.org/browse/TEIID-3943 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.13, 8.12.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > The fix for TEIID-3870 did not include the schema name - which could be need if the same package name exists in multiple schemas. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3944) Accumulo translator: rowid column is compared as string in WHERE clause

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3944?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-3944: ------------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) Assigning to Ramesh. This will be resolved by the switch to a later Accumulo and using a lexicoder that preserves the natural ordering. > Accumulo translator: rowid column is compared as string in WHERE clause > ----------------------------------------------------------------------- > > Key: TEIID-3944 > URL: https://issues.jboss.org/browse/TEIID-3944 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.3 > Reporter: Jan Stastny > Assignee: Ramesh Reddy > > When in SOURCE model user specifies the required rowid column as integer: > {code:xml} > CREATE FOREIGN TABLE "SmallA" ( > rowid integer OPTIONS (UPDATABLE FALSE, SEARCHABLE 'All_Except_Like'), > . > . > . > {code} > and performs similar query: > {code:sql} > Select rowid, StringKey From accumulo.SmallA WHERE rowid >= 15 ORDER BY rowid > {code} > following results are returned: > || rowid | StringKey || > || 2 | 2 || > || 3 | 3 || > || 4 | 4 || > || 5 | 5 || > || 6 | 6 || > || 7 | 7 || > || 8 | 8 || > || 9 | 9 || > || 15 | 15 || > || ... | ... || > and given the fact, that rowid is modelled as integer, values 2,3,4,5,6,7,8,9 shouldn't appear in the result set. Interesting to note is that the resultset is then ordered by rowid, but this time correctly as expected. > Other integer columns, mapped from accumulo's Column Family: Column Qualifier pairs works as expected and are being compared as corresponding types. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 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 Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-3816?page=com.atlassian.jira.plugin... ] Juraj Duráni commented on TEIID-3816: ------------------------------------- OK, I agree. > 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 > Fix For: 8.12.x > > > 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)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3944) Accumulo translator: rowid column is compared as string in WHERE clause

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3944?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3944: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1302977 Bugzilla Update: Perform > Accumulo translator: rowid column is compared as string in WHERE clause > ----------------------------------------------------------------------- > > Key: TEIID-3944 > URL: https://issues.jboss.org/browse/TEIID-3944 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.3 > Reporter: Jan Stastny > Assignee: Steven Hawkins > > When in SOURCE model user specifies the required rowid column as integer: > {code:xml} > CREATE FOREIGN TABLE "SmallA" ( > rowid integer OPTIONS (UPDATABLE FALSE, SEARCHABLE 'All_Except_Like'), > . > . > . > {code} > and performs similar query: > {code:sql} > Select rowid, StringKey From accumulo.SmallA WHERE rowid >= 15 ORDER BY rowid > {code} > following results are returned: > || rowid | StringKey || > || 2 | 2 || > || 3 | 3 || > || 4 | 4 || > || 5 | 5 || > || 6 | 6 || > || 7 | 7 || > || 8 | 8 || > || 9 | 9 || > || 15 | 15 || > || ... | ... || > and given the fact, that rowid is modelled as integer, values 2,3,4,5,6,7,8,9 shouldn't appear in the result set. Interesting to note is that the resultset is then ordered by rowid, but this time correctly as expected. > Other integer columns, mapped from accumulo's Column Family: Column Qualifier pairs works as expected and are being compared as corresponding types. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3944) Accumulo translator: rowid column is compared as string in WHERE clause

by Jan Stastny (JIRA)

Jan Stastny created TEIID-3944: ---------------------------------- Summary: Accumulo translator: rowid column is compared as string in WHERE clause Key: TEIID-3944 URL: https://issues.jboss.org/browse/TEIID-3944 Project: Teiid Issue Type: Bug Components: Misc. Connectors Affects Versions: 8.12.3 Reporter: Jan Stastny Assignee: Steven Hawkins When in SOURCE model user specifies the required rowid column as integer: {code:xml} CREATE FOREIGN TABLE "SmallA" ( rowid integer OPTIONS (UPDATABLE FALSE, SEARCHABLE 'All_Except_Like'), . . . {code} and performs similar query: {code:sql} Select rowid, StringKey From accumulo.SmallA WHERE rowid >= 15 ORDER BY rowid {code} following results are returned: || rowid | StringKey || || 2 | 2 || || 3 | 3 || || 4 | 4 || || 5 | 5 || || 6 | 6 || || 7 | 7 || || 8 | 8 || || 9 | 9 || || 15 | 15 || || ... | ... || and given the fact, that rowid is modelled as integer, values 2,3,4,5,6,7,8,9 shouldn't appear in the result set. Interesting to note is that the resultset is then ordered by rowid, but this time correctly as expected. Other integer columns, mapped from accumulo's Column Family: Column Qualifier pairs works as expected and are being compared as corresponding types. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3871) moving documentation from confluence to gitbook

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-3871?page=com.atlassian.jira.plugin... ] Kylin Soong commented on TEIID-3871: ------------------------------------ Steven, I have added, https://www.gitbook.com/book/teiid/documents/details are mapped with teiid/teiid-documents. > moving documentation from confluence to gitbook > ------------------------------------------------- > > Key: TEIID-3871 > URL: https://issues.jboss.org/browse/TEIID-3871 > Project: Teiid > Issue Type: Task > Components: Documentation > Affects Versions: 9.x > Reporter: Kylin Soong > Assignee: Kylin Soong > Fix For: 9.x > > > From Teiid DV 7 F2F Notes, > " In the Teiid 9.x timeframe we should look toward moving everything to gitbook / markdown. We should start by migrating the documentation and solicit help with the website if possible." > This issue will address this. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3943) Add schema name to oracle packaged objects

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3943: ------------------------------------- Summary: Add schema name to oracle packaged objects Key: TEIID-3943 URL: https://issues.jboss.org/browse/TEIID-3943 Project: Teiid Issue Type: Task Components: JDBC Connector Affects Versions: 8.12.4, 8.13 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.0 The fix for TEIID-3870 did not include the schema name - which could be need if the same package name exists in multiple schemas. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3929) Accumulo does not return null values

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3929?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-3929: ------------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > Accumulo does not return null values > ------------------------------------ > > Key: TEIID-3929 > URL: https://issues.jboss.org/browse/TEIID-3929 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.3 > Reporter: Jan Stastny > Assignee: Ramesh Reddy > Fix For: 8.12.x > > > Accumulo doesn't return null values when a whole 'column' is being selected. > For a command in accumulo shell like: > {code:plain} > scan -c name:BYTENUM > {code} > Accumulo returns only non-empty values, this is expected behaviour. > Equivalent query in Teiid would be: > {code:sql} > SELECT ByteNum FROM SmallA > {code} > Which returns the same results as Accumulo does. That means, no NULL values, if there are rowids without specified column families/qualifiers missing. But when a user has his schema defined in a vdb, he probably expects, that he will get as many rows as there are in the table. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3929) Accumulo does not return null values

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3929?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3929: ---------------------------------- Fix Version/s: 8.12.x > Accumulo does not return null values > ------------------------------------ > > Key: TEIID-3929 > URL: https://issues.jboss.org/browse/TEIID-3929 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.3 > Reporter: Jan Stastny > Assignee: Ramesh Reddy > Fix For: 8.12.x > > > Accumulo doesn't return null values when a whole 'column' is being selected. > For a command in accumulo shell like: > {code:plain} > scan -c name:BYTENUM > {code} > Accumulo returns only non-empty values, this is expected behaviour. > Equivalent query in Teiid would be: > {code:sql} > SELECT ByteNum FROM SmallA > {code} > Which returns the same results as Accumulo does. That means, no NULL values, if there are rowids without specified column families/qualifiers missing. But when a user has his schema defined in a vdb, he probably expects, that he will get as many rows as there are in the table. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2016