December 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3675) Remove JwtBearerGrant CXF classes

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3675?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-3675: -------------------------------- Fix Version/s: 8.13 (was: 9.0) > Remove JwtBearerGrant CXF classes > --------------------------------- > > Key: TEIID-3675 > URL: https://issues.jboss.org/browse/TEIID-3675 > Project: Teiid > Issue Type: Sub-task > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Minor > Fix For: 8.13 > > > When CXF version > 3.0.4 remove JwtBearerGrant related CXF classes, and use ones from CXF -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3826) Upgrade to use resteasy-jaxrs:jar:2.3.10.Final

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3826?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-3826: -------------------------------- Fix Version/s: 8.12.x > Upgrade to use resteasy-jaxrs:jar:2.3.10.Final > ---------------------------------------------- > > Key: TEIID-3826 > URL: https://issues.jboss.org/browse/TEIID-3826 > Project: Teiid > Issue Type: Enhancement > Components: OData > Affects Versions: 8.12 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 8.12.x > > > 8.12.x is currently dependent on resteasy-jaxrs:jar:2.3.7.Final > In upgrading the IP-BOM to 30, which is dependent on 2.3.10, it seems the following class has been removed from javax-rs 2.3.10: > org/jboss/resteasy/util/HttpServletRequestDelegate.java > which breaks ProxyHttpServletRequest.java -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

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

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3869?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-3869: ------------------------------- Description: 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) was: 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 RWS is 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) > 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)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3541) Remove the Teiid embedded kit

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3541?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3541. --------------------------------- Resolution: Done Labels: beta2 (was: ) Done > Remove the Teiid embedded kit > ----------------------------- > > Key: TEIID-3541 > URL: https://issues.jboss.org/browse/TEIID-3541 > Project: Teiid > Issue Type: Task > Components: Embedded > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: beta2 > Fix For: 8.13 > > > There is no reason to keep a separate embedded kit supplied by Teiid. The scripts that are building the kit needs to be removed from build. > All the required jar files for the "embedded" examples will be available from the "teiid-embedded-examples". Here we need to focus on documentation, but that is separate effort -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

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

by Van Halbert (JIRA)

Van Halbert created TEIID-3869: ---------------------------------- Summary: 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 RWS is 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)

9 years

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3869?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3869: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1291814 Bugzilla Update: Perform > 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 > RWS is 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)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3298) invokeHttp procedure should support returning HTTP Response Code

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3298?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3298: ------------------------------------- sure, do not have any immediate need but would be good to have > invokeHttp procedure should support returning HTTP Response Code > ---------------------------------------------------------------- > > Key: TEIID-3298 > URL: https://issues.jboss.org/browse/TEIID-3298 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.4 > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > > Currently WS Translator supplied "invokeHttp" procedure only returns the result and as well as the content-type. It should also return response code. > It may be useful to check if there is any other return parameters can be useful too. Like cookie etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

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 edited comment on TEIID-3725 at 12/16/15 11:58 AM: --------------------------------------------------------------- There will need to be 3 caches in order to do materialization: - the primary cache used for reading - the staging cache to load using materialization - a cache used for tracking the cache name aliasing that will be used. This will enable the underlying translator logic to swap out the cache (i.e, primary versus staging) after the cache that was used for staging is loaded and provide a persistence of the aliasing when the server is restarted. Another reason for needing the 3rd cache is that the other caches will be completely cleared before each materialization. So combining different object types into a cache wouldn't work at this time. The configuring of the caches to be used will be done on the connector, along with configuring the other JDG connection information. I contemplated using translator overrides for this additional settings, but decided on the connector because the connector settings are specific and the staging cache settings would be specifically related to that same cache. was (Author: van.halbert): There will need to be 3 caches in order to do materialization: - the primary cache used for reading - the staging cache to load using materialization - a cache used for tracking the cache name aliasing that will be used. This will enable the underlying translator logic to swap out the cache (i.e, primary versus staging) after the cache that was used for staging is loaded and provide a persistence of the aliasing when the server is restarted. The configuring of the caches to be used will be done on the connector, along with configuring the other JDG connection information. I contemplated using translator overrides for this additional settings, but decided on the connector because the connector settings are specific and the staging cache settings would be specifically related to that same cache. > 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)

9 years

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: ------------------------------------ There will need to be 3 caches in order to do materialization: - the primary cache used for reading - the staging cache to load using materialization - a cache used for tracking the cache name aliasing that will be used. This will enable the underlying translator logic to swap out the cache (i.e, primary versus staging) after the cache that was used for staging is loaded and provide a persistence of the aliasing when the server is restarted. The configuring of the caches to be used will be done on the connector, along with configuring the other JDG connection information. I contemplated using translator overrides for this additional settings, but decided on the connector because the connector settings are specific and the staging cache settings would be specifically related to that same cache. > 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)

9 years

1
0
0 / 0

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

by Pranav K (JIRA)

[ https://issues.jboss.org/browse/TEIID-3849?page=com.atlassian.jira.plugin... ] Pranav K commented on TEIID-3849: --------------------------------- Okay, Thanks! > 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: 8.13, 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)

9 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2015