January 2016 - teiid-issues - Jboss List Archives

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

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3929?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-3929: -------------------------------- Fix Version/s: 9.0 8.12.5 (was: 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: 9.0, 8.12.5 > > > 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, 2 months

1
0
0 / 0

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

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3929?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3929. --------------------------------- Resolution: Done > 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: 9.0, 8.12.5 > > > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3916) Support SAML security on OData interface using Keycloak

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3916?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3916: --------------------------------------- Can you port this doc over to the gitbook site as well? > Support SAML security on OData interface using Keycloak > ------------------------------------------------------- > > Key: TEIID-3916 > URL: https://issues.jboss.org/browse/TEIID-3916 > Project: Teiid > Issue Type: Feature Request > Components: Documentation, OData > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.13, 8.12.5 > > > Support SAML based authentication using the Keycloak. The previous approach defined was using the Picketlink in the documentation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

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

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3929?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3929: ------------------------------------- Thanks for the clarification. In that case I am seeing the right results, may be other changes affected this, can not seem find how that could be :( > 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, 3 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 commented on TEIID-3929: --------------------------------------- No he's saying that if there are any null values for ByteNum, then SELECT ByteNum FROM SMALLA won't return them. > 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, 3 months

1
0
0 / 0

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

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3929?page=com.atlassian.jira.plugin... ] Work on TEIID-3929 started by Ramesh Reddy. ------------------------------------------- > 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, 3 months

1
0
0 / 0

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

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3929?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3929: ------------------------------------- RowID is implicitly always there, may be I should re-write as {code} SELECT ByteNum FROM SmallA WHERE ByteNum IS NOT null {code} > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3894) Teiid transport ssl attributes should add some default values

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3894?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3894: --------------------------------------- It would also be good to add some validation of the parameters (such as protocol) on the transport start rather than waiting for the initial connection. > Teiid transport ssl attributes should add some default values > ------------------------------------------------------------- > > Key: TEIID-3894 > URL: https://issues.jboss.org/browse/TEIID-3894 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Kylin Soong > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5 > > > Execute the following cli > {code} > /subsystem=teiid/transport=jdbc:write-attribute(name=ssl-mode,value=enabled) > /subsystem=teiid/transport=jdbc:write-attribute(name=ssl-authentication-mode,value=1-way) > /subsystem=teiid/transport=jdbc:write-attribute(name=ssl-ssl-protocol,value=TLSv1) > /subsystem=teiid/transport=jdbc:write-attribute(name=ssl-keymanagement-algorithm,value=SunX509) > /subsystem=teiid/transport=jdbc:write-attribute(name=ssl-enabled-cipher-suites,value="SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA") > /subsystem=teiid/transport=jdbc:write-attribute(name=keystore-type,value=JKS) > {code} > no suggested value pop up, some values only allow existed value, so I think add some default value is necessary. > h3. ssl-mode allowed value > * enabled > * login > * enabled > h3. ssl-authentication-mode allowed value > * 1-way > * 2-way > * anonymous > h3. ssl-ssl-protocol default value > * TLSv1 > h3. ssl-keymanagement-algorithm default value > * SunX509 > h3. ssl-enabled-cipher-suites default value > * SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA > h3. keystore-type default value > * JKS -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

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

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3944?page=com.atlassian.jira.plugin... ] Work on TEIID-3944 started by Ramesh Reddy. ------------------------------------------- > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3941) Upgrade Accumulo libraries to 1.6.4 version

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3941?page=com.atlassian.jira.plugin... ] Work on TEIID-3941 started by Ramesh Reddy. ------------------------------------------- > Upgrade Accumulo libraries to 1.6.4 version > ------------------------------------------- > > Key: TEIID-3941 > URL: https://issues.jboss.org/browse/TEIID-3941 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.12.4 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.12.5 > > > The latest version of the Accumulo is 1.6.4 and 1.7.0, the version Teiid supports is 1.5, which was chosen from 2 years ago. We should upgrade to 1.6.4. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 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