June 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4106) Rename and align infinispan translators/resource-adapters for their purpose

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4106?page=com.atlassian.jira.plugin... ] Van Halbert resolved TEIID-4106. -------------------------------- Release Notes Text: Resolving the alignment, for any additional issues a new jira can be logged. Resolution: Done > Rename and align infinispan translators/resource-adapters for their purpose > ---------------------------------------------------------------------------- > > Key: TEIID-4106 > URL: https://issues.jboss.org/browse/TEIID-4106 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 9.0 > > > The infinispan-cache and infinispan-cache-dsl translators/resource-adapters need to be renamed and aligned for what their purpose is. Because using "dsl" as part of the name is confusing, because both translators now support querying using JDG DSL language. > infinispan-cache: > - rename to infinispan-cache-library-mode (or leave as infinispan-cache and it be assume library mode) > - deprecate the access to remote-cache because the other infinispan-cache-dsl translator provides this feature. > - this will enable the cleaning of the documentation to be specific to library mode > infinispan-cache-dsl: > - rename to infinispan-cache-hot-rod (or something other than "dsl") because this all about remote cache access using hot rod client -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3801) Upgrade Infinispan translator to support 6.4.x version (JDG 6.6)

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3801?page=com.atlassian.jira.plugin... ] Van Halbert resolved TEIID-3801. -------------------------------- Resolution: Done > Upgrade Infinispan translator to support 6.4.x version (JDG 6.6) > ---------------------------------------------------------------- > > Key: TEIID-3801 > URL: https://issues.jboss.org/browse/TEIID-3801 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.12.x, 9.x > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.12.x, 9.1 > > > Upgrade Infinispan translator to support version 6.4 (JDG 6.6). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3801) Upgrade Infinispan translator to support 6.4.x version (JDG 6.6)

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3801?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3801: ------------------------------------ This has been completed > Upgrade Infinispan translator to support 6.4.x version (JDG 6.6) > ---------------------------------------------------------------- > > Key: TEIID-3801 > URL: https://issues.jboss.org/browse/TEIID-3801 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.12.x, 9.x > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.12.x, 9.1 > > > Upgrade Infinispan translator to support version 6.4 (JDG 6.6). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3801) Upgrade Infinispan translator to support 6.4.x version (JDG 6.6)

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3801?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-3801: ------------------------------- Fix Version/s: 9.1 > Upgrade Infinispan translator to support 6.4.x version (JDG 6.6) > ---------------------------------------------------------------- > > Key: TEIID-3801 > URL: https://issues.jboss.org/browse/TEIID-3801 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.12.x, 9.x > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.12.x, 9.1 > > > Upgrade Infinispan translator to support version 6.4 (JDG 6.6). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3725) In the JDG translators, enable named cache swapping so that materialization can be supported

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3725?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3725: ------------------------------------ added PR: https://github.com/teiid/teiid-documents/pull/52 for document update. > In the JDG translators, enable named cache swapping so that materialization can be supported > -------------------------------------------------------------------------------------------- > > Key: TEIID-3725 > URL: https://issues.jboss.org/browse/TEIID-3725 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.12 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 9.0, 8.12.5 > > > The JDG translators, that in order to support materialization, will need to enable the named cache that's referenced by the connection, to be swapped. This is due to JDG doesn't currently support renaming a cache (i.e., like table rename in JDBC). And because of that, it limits how the cache can be refreshed (don't want to clear it before re-loading). > Ideas are: > 1. configure translator with the 2 cache names to use (a) initial cache to read from and (b) the staging cache to use > perform materialize load > call SYSADMIN.setProperty to trigger the swapping of the cache names > 2 ??? > Note: because there's no persistence in Teiid so that any cache name changes will outlive a server restart, when a restart occurs, the translator will read from the cache identified as the initial cache to read from. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

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

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4090?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4090: --------------------------------------- If it's not needed, yes it should be removed. However unlikely it is possible for static/keycloak to conflict with entity set names correct? > 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 > 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, 10 months

1
0
0 / 0

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

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4090?page=com.atlassian.jira.plugin... ] Ramesh Reddy reopened TEIID-4090: --------------------------------- > 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 > 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, 10 months

1
0
0 / 0

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

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4090?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4090: ------------------------------------- [~shawkins] Basically you are advocating to remove that check in the ODataFilter, I will remove it and see if need to re-wire the web.xml any differently > 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 > 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, 10 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: ------------------------------------- [~jstastny] I updated the code, can you locally build the translator and replace in your server and accumulo instance and give a quick try again? For some reason I can not seem to make my local Accumulo instance start at all > 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)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4260) Accumulo: Resource adapter fails to load

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4260?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-4260: -------------------------------- Fix Version/s: 8.13.6 > Accumulo: Resource adapter fails to load > ---------------------------------------- > > Key: TEIID-4260 > URL: https://issues.jboss.org/browse/TEIID-4260 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 9.0, 8.13.x > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 9.0, 8.13.6 > > > "org/apache/commons/configuration" module seemed to be removed, this needs to be corrected. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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