January 2016 - teiid-issues - Jboss List Archives

[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: ------------------------------------ Just completed the changes and testing with supporting materializing to a remote cache. These changes will include the following: - added materialize configuration examples to the docs/teiid/datasources/infinispan - updated the jdg-remote-cache example. - eliminated the use of the JDG remote-query quick start, by coping that code into the teiid jdg-remote-cache quick start because there are changes to the configuration of the materialize caches that were needed. - this also includes the refactoring of the infinispan-dsl resource adapter (TEIID-3559). > 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 > > 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)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3908) Escaped quotes are not handled in odata4 parameter string literal

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3908: ------------------------------------- Summary: Escaped quotes are not handled in odata4 parameter string literal Key: TEIID-3908 URL: https://issues.jboss.org/browse/TEIID-3908 Project: Teiid Issue Type: Bug Components: OData Affects Versions: 8.12 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.12.5, 8.13 String literals use '' to escape the single quote character, but the literal parsing logic will retain the double single quotes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3869) Enable Teiid to be exposed as a GIS compliant data source

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3869?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3869: ---------------------------------- Component/s: Grammar > Enable Teiid to be exposed as a GIS compliant data source > --------------------------------------------------------- > > Key: TEIID-3869 > URL: https://issues.jboss.org/browse/TEIID-3869 > Project: Teiid > Issue Type: Feature Request > Components: Grammar, JDBC Driver, OData, ODBC > Reporter: Van Halbert > Assignee: Steven Hawkins > > See > http://www.esri.com/~/media/Files/Pdfs/library/whitepapers/pdfs/supported... > WMS - http://www.opengeospatial.org/standards/wms > WFS - http://www.opengeospatial.org/standards/wfs > Using MapViewer to show maps based on WMS services. The WMS services are provided by a GeoServer like ArcGIS or GeoServer. > OData has also some capabilities in the Geo space especially on the .Net libraries side. > See http://www.odata.org/libraries/ for Microsoft.Spatial (OData v4) and System.Spatial (OData v1-3) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3905) ODBC openquery permission issues when insert oracle date field

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3905?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3905. ----------------------------------- Resolution: Rejected Thanks for the update Steve, will mark as rejected for now. > ODBC openquery permission issues when insert oracle date field > -------------------------------------------------------------- > > Key: TEIID-3905 > URL: https://issues.jboss.org/browse/TEIID-3905 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1.6_2 > Environment: Red Hat JBoss Data Virtualization 6.2 on EAP6.4.0 patched to version 6.4.3, > JBoss Developer Studio 8.1.0GA with Teiid Designer plugin 9.0.3.Final.v20150810-1438-B1157 > 64-bit Windows 7 environment > Reporter: Steve Tran > Assignee: Steven Hawkins > Priority: Optional > > Getting an error when attempting to insert a new row into an virtualized Oracle Table in JDV. > Here's the query > INSERT INTO OPENQUERY(testb, 'SELECT * FROM TestVBL.HSI_AGGR_PROC_LK') > VALUES ('TEST 1:18am', cast (getdate() as date)) > {code} > OLE DB provider "MSDASQL" for linked server "testb" returned message "Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.". > Msg 7344, Level 16, State 1, Line 1 > The OLE DB provider "MSDASQL" for linked server "testb" could not INSERT INTO table "[MSDASQL]" because of column "LK_DT". The user did not have permission to write to the column. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3869) Enable Teiid to be exposed as a GIS compliant data source

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3869?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3869: --------------------------------------- >From here we can start a new issue to cover general opengis support, target another platform (such as qgis - http://www.qgis.org/en/site/), or add support for spatial indexes. > Enable Teiid to be exposed as a GIS compliant data source > --------------------------------------------------------- > > Key: TEIID-3869 > URL: https://issues.jboss.org/browse/TEIID-3869 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Driver, OData, ODBC > Reporter: Van Halbert > Assignee: Steven Hawkins > > See > http://www.esri.com/~/media/Files/Pdfs/library/whitepapers/pdfs/supported... > WMS - http://www.opengeospatial.org/standards/wms > WFS - http://www.opengeospatial.org/standards/wfs > Using MapViewer to show maps based on WMS services. The WMS services are provided by a GeoServer like ArcGIS or GeoServer. > OData has also some capabilities in the Geo space especially on the .Net libraries side. > See http://www.odata.org/libraries/ for Microsoft.Spatial (OData v4) and System.Spatial (OData v1-3) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3905) ODBC openquery permission issues when insert oracle date field

by Steve Tran (JIRA)

[ https://issues.jboss.org/browse/TEIID-3905?page=com.atlassian.jira.plugin... ] Steve Tran updated TEIID-3905: ------------------------------ Priority: Optional (was: Critical) > ODBC openquery permission issues when insert oracle date field > -------------------------------------------------------------- > > Key: TEIID-3905 > URL: https://issues.jboss.org/browse/TEIID-3905 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1.6_2 > Environment: Red Hat JBoss Data Virtualization 6.2 on EAP6.4.0 patched to version 6.4.3, > JBoss Developer Studio 8.1.0GA with Teiid Designer plugin 9.0.3.Final.v20150810-1438-B1157 > 64-bit Windows 7 environment > Reporter: Steve Tran > Assignee: Steven Hawkins > Priority: Optional > > Getting an error when attempting to insert a new row into an virtualized Oracle Table in JDV. > Here's the query > INSERT INTO OPENQUERY(testb, 'SELECT * FROM TestVBL.HSI_AGGR_PROC_LK') > VALUES ('TEST 1:18am', cast (getdate() as date)) > {code} > OLE DB provider "MSDASQL" for linked server "testb" returned message "Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.". > Msg 7344, Level 16, State 1, Line 1 > The OLE DB provider "MSDASQL" for linked server "testb" could not INSERT INTO table "[MSDASQL]" because of column "LK_DT". The user did not have permission to write to the column. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3905) ODBC openquery permission issues when insert oracle date field

by Steve Tran (JIRA)

[ https://issues.jboss.org/browse/TEIID-3905?page=com.atlassian.jira.plugin... ] Steve Tran commented on TEIID-3905: ----------------------------------- I think this was an ODBC and/or Linked Server configuration issue. I switched my Linked Server setup to use MSDSQL instead of MSDSQL.1 as the provider as suggested from a source I didn't bookmark. I'm able to update my date field now. Also, the SQL syntax I was using wasn't correct. It should be {code} INSERT INTO OPENQUERY(testb, 'SELECT * FROM TestVBL.HSI_AGGR_PROC_LK') VALUES ('TEST 1:18am', getdate()) {code} We can close this ticket out as a non-issue. > ODBC openquery permission issues when insert oracle date field > -------------------------------------------------------------- > > Key: TEIID-3905 > URL: https://issues.jboss.org/browse/TEIID-3905 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1.6_2 > Environment: Red Hat JBoss Data Virtualization 6.2 on EAP6.4.0 patched to version 6.4.3, > JBoss Developer Studio 8.1.0GA with Teiid Designer plugin 9.0.3.Final.v20150810-1438-B1157 > 64-bit Windows 7 environment > Reporter: Steve Tran > Assignee: Steven Hawkins > Priority: Critical > > Getting an error when attempting to insert a new row into an virtualized Oracle Table in JDV. > Here's the query > INSERT INTO OPENQUERY(testb, 'SELECT * FROM TestVBL.HSI_AGGR_PROC_LK') > VALUES ('TEST 1:18am', cast (getdate() as date)) > {code} > OLE DB provider "MSDASQL" for linked server "testb" returned message "Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.". > Msg 7344, Level 16, State 1, Line 1 > The OLE DB provider "MSDASQL" for linked server "testb" could not INSERT INTO table "[MSDASQL]" because of column "LK_DT". The user did not have permission to write to the column. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3906) OData v4 - definition of OData-Isolation header is either being ignored or is not implemented corectly

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3906?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3906: ------------------------------------- IMO, need to push check into Olingo framework, but have an option to support in the ServiceHandler interface. > OData v4 - definition of OData-Isolation header is either being ignored or is not implemented corectly > ------------------------------------------------------------------------------------------------------ > > Key: TEIID-3906 > URL: https://issues.jboss.org/browse/TEIID-3906 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.12.3 > Environment: Teiid - OData v4 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > Teiid does not process header *OData-Isolation: snapshot* defined in request correctly. > * if service (Teiid) does not support this option it must return error 412 > * if Teiid does supports this option then it is not processed correctly, because modifications made during request are visbile > See http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part1-pr... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3906) OData v4 - definition of OData-Isolation header is either being ignored or is not implemented corectly

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3906?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3906: --------------------------------------- I looked for a convenient single place to put the check, but it doesn't look like there is one (ODataServlet doesn't seem to be appropriate for the error handling). So a check may be needed in several of the methods in TeiidServiceHandler. > OData v4 - definition of OData-Isolation header is either being ignored or is not implemented corectly > ------------------------------------------------------------------------------------------------------ > > Key: TEIID-3906 > URL: https://issues.jboss.org/browse/TEIID-3906 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.12.3 > Environment: Teiid - OData v4 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > Teiid does not process header *OData-Isolation: snapshot* defined in request correctly. > * if service (Teiid) does not support this option it must return error 412 > * if Teiid does supports this option then it is not processed correctly, because modifications made during request are visbile > See http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part1-pr... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3907) Support compensating transactions for updatable non-XA sources

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3907?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-3907: -------------------------------- Description: The transaction manager will fully support xa with all xa sources and a single local transaction resource. Beyond that however there is no built-in support for compensating transactions with non-XA sources. There has been work in Narayana on compensating transactions though that could be used by custom web apps consuming Teiid. We would like to eventually offer compensating options for some of our updatable non-XA sources, but it hasn't had sufficient priority yet. (was: From: "Steven Hawkins" <shawkins(a)redhat.com> To: "Steve Tran" <stran(a)redhat.com> Cc: "Frederic Hornain" <fhornain(a)redhat.com>, "sme-dataservicesplatform" <sme-dataservicesplatform(a)redhat.com> Sent: Monday, January 18, 2016 8:30:49 AM Subject: Re: [RHB] Atomic and distributed transaction The transaction manager will fully support xa with all xa sources and a single local transaction resource. Beyond that however there is no built-in support for compensating transactions with non-XA sources. There has been work in Narayana on compensating transactions though that could be used by custom web apps consuming Teiid. We would like to eventually offer compensating options for some of our updatable non-XA sources, but it hasn't had sufficient priority yet.) > Support compensating transactions for updatable non-XA sources > -------------------------------------------------------------- > > Key: TEIID-3907 > URL: https://issues.jboss.org/browse/TEIID-3907 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Steven Hawkins > > The transaction manager will fully support xa with all xa sources and a single local transaction resource. Beyond that however there is no built-in support for compensating transactions with non-XA sources. There has been work in Narayana on compensating transactions though that could be used by custom web apps consuming Teiid. We would like to eventually offer compensating options for some of our updatable non-XA sources, but it hasn't had sufficient priority yet. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 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 January 2016