[JBoss JIRA] (TEIIDSB-147) Caching and materialization changes for JDG / OpenShift
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-147?page=com.atlassian.jira.plug... ]
Steven Hawkins reassigned TEIIDSB-147:
--------------------------------------
Assignee: Steven Hawkins (was: Ramesh Reddy)
> Caching and materialization changes for JDG / OpenShift
> -------------------------------------------------------
>
> Key: TEIIDSB-147
> URL: https://issues.redhat.com/browse/TEIIDSB-147
> Project: Teiid Spring Boot
> Issue Type: Enhancement
> Components: core, OpenShift
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 1.3.0
>
>
> Started this as a higher level issue in Teiid Spring Boot rather than core Teiid since the work won't align well to Teiid 13.1, but some things may need addressed there as well.
> Things break down roughly into:
> * Single-pod support
> ** Define the expectations for how we'll be configured to hit a JDG instance - will it be a user exercise to create if it doesn't exist, will we need to create, will the be a crd strategy for creation, and will it be multi-tenet? There is also the issue / assumption of cache sharing based upon vdb name - is that sufficient for now?
> ** validate external materialization to JDG likely using a transactional upsert strategy to avoid issues like TEIID-5436
> * Multi-pod support
> ** everything from single-pod support
> ** Result set caching needs to directly write batches / results to JDG rather than relying upon on demand replication.
> ** requires replacing the logic that detect failed materialization loads
> ** internal materialization replacement needs to based upon something more like external materialization, but that can be seen as a next step that is turnkey internal materialization to JDG (little to no user setup required)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (TEIIDSB-147) Caching and materialization changes for JDG / OpenShift
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-147?page=com.atlassian.jira.plug... ]
Steven Hawkins commented on TEIIDSB-147:
----------------------------------------
Sure, I'll have a look.
> Caching and materialization changes for JDG / OpenShift
> -------------------------------------------------------
>
> Key: TEIIDSB-147
> URL: https://issues.redhat.com/browse/TEIIDSB-147
> Project: Teiid Spring Boot
> Issue Type: Enhancement
> Components: core, OpenShift
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Priority: Critical
> Fix For: 1.3.0
>
>
> Started this as a higher level issue in Teiid Spring Boot rather than core Teiid since the work won't align well to Teiid 13.1, but some things may need addressed there as well.
> Things break down roughly into:
> * Single-pod support
> ** Define the expectations for how we'll be configured to hit a JDG instance - will it be a user exercise to create if it doesn't exist, will we need to create, will the be a crd strategy for creation, and will it be multi-tenet? There is also the issue / assumption of cache sharing based upon vdb name - is that sufficient for now?
> ** validate external materialization to JDG likely using a transactional upsert strategy to avoid issues like TEIID-5436
> * Multi-pod support
> ** everything from single-pod support
> ** Result set caching needs to directly write batches / results to JDG rather than relying upon on demand replication.
> ** requires replacing the logic that detect failed materialization loads
> ** internal materialization replacement needs to based upon something more like external materialization, but that can be seen as a next step that is turnkey internal materialization to JDG (little to no user setup required)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (TEIIDSB-147) Caching and materialization changes for JDG / OpenShift
by Ramesh Reddy (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-147?page=com.atlassian.jira.plug... ]
Ramesh Reddy updated TEIIDSB-147:
---------------------------------
Priority: Critical (was: Major)
> Caching and materialization changes for JDG / OpenShift
> -------------------------------------------------------
>
> Key: TEIIDSB-147
> URL: https://issues.redhat.com/browse/TEIIDSB-147
> Project: Teiid Spring Boot
> Issue Type: Enhancement
> Components: core, OpenShift
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Priority: Critical
> Fix For: 1.3.0
>
>
> Started this as a higher level issue in Teiid Spring Boot rather than core Teiid since the work won't align well to Teiid 13.1, but some things may need addressed there as well.
> Things break down roughly into:
> * Single-pod support
> ** Define the expectations for how we'll be configured to hit a JDG instance - will it be a user exercise to create if it doesn't exist, will we need to create, will the be a crd strategy for creation, and will it be multi-tenet? There is also the issue / assumption of cache sharing based upon vdb name - is that sufficient for now?
> ** validate external materialization to JDG likely using a transactional upsert strategy to avoid issues like TEIID-5436
> * Multi-pod support
> ** everything from single-pod support
> ** Result set caching needs to directly write batches / results to JDG rather than relying upon on demand replication.
> ** requires replacing the logic that detect failed materialization loads
> ** internal materialization replacement needs to based upon something more like external materialization, but that can be seen as a next step that is turnkey internal materialization to JDG (little to no user setup required)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (TEIIDSB-149) Support Amazon S3 Transaltor
by Ramesh Reddy (Jira)
Ramesh Reddy created TEIIDSB-149:
------------------------------------
Summary: Support Amazon S3 Transaltor
Key: TEIIDSB-149
URL: https://issues.redhat.com/browse/TEIIDSB-149
Project: Teiid Spring Boot
Issue Type: Enhancement
Components: datasource
Reporter: Ramesh Reddy
Fix For: 1.3.0
Provide support for Amazon S3 transaltor in Teiid Spring Boot with an example.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (TEIIDSB-147) Caching and materialization changes for JDG / OpenShift
by Ramesh Reddy (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-147?page=com.atlassian.jira.plug... ]
Ramesh Reddy commented on TEIIDSB-147:
--------------------------------------
[~shawkins] I do not think I can verify this looking at issues I still need to work on, would you mind running through this and document?
> Caching and materialization changes for JDG / OpenShift
> -------------------------------------------------------
>
> Key: TEIIDSB-147
> URL: https://issues.redhat.com/browse/TEIIDSB-147
> Project: Teiid Spring Boot
> Issue Type: Enhancement
> Components: core, OpenShift
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Priority: Major
> Fix For: 1.3.0
>
>
> Started this as a higher level issue in Teiid Spring Boot rather than core Teiid since the work won't align well to Teiid 13.1, but some things may need addressed there as well.
> Things break down roughly into:
> * Single-pod support
> ** Define the expectations for how we'll be configured to hit a JDG instance - will it be a user exercise to create if it doesn't exist, will we need to create, will the be a crd strategy for creation, and will it be multi-tenet? There is also the issue / assumption of cache sharing based upon vdb name - is that sufficient for now?
> ** validate external materialization to JDG likely using a transactional upsert strategy to avoid issues like TEIID-5436
> * Multi-pod support
> ** everything from single-pod support
> ** Result set caching needs to directly write batches / results to JDG rather than relying upon on demand replication.
> ** requires replacing the logic that detect failed materialization loads
> ** internal materialization replacement needs to based upon something more like external materialization, but that can be seen as a next step that is turnkey internal materialization to JDG (little to no user setup required)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (TEIID-5865) Error with pg arrays
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5865?page=com.atlassian.jira.plugi... ]
Steven Hawkins commented on TEIID-5865:
---------------------------------------
Settled on disabling pg array_agg support and turning off the ability to select array expressions.
> Error with pg arrays
> --------------------
>
> Key: TEIID-5865
> URL: https://issues.redhat.com/browse/TEIID-5865
> Project: Teiid
> Issue Type: Bug
> Components: OData, Query Engine
> Affects Versions: 12.3
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.2.2, 12.3.1, 13.1, 13.0.1
>
> Original Estimate: 5 hours
> Time Spent: 5 hours
> Remaining Estimate: 0 minutes
>
> When I try the following query using customer-dv deployment against postgresql
> https://rdbms-springboot-dv-demo.apps.cluster-london-966d.london-966d.ope...
> I get the following error:
> {"error":{"code":"TEIID30504","message":"TEIID30504 sampledb: TEIID31176 Could not convert source column v_0.c_1 AS c_3 to the expected runtime type object[][]"}}
> This occurs with any pg array that is created with an expression:
> select (col, col2)..
> array_agg, etc.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (TEIID-5865) Error with pg arrays
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5865?page=com.atlassian.jira.plugi... ]
Steven Hawkins updated TEIID-5865:
----------------------------------
Component/s: Query Engine
Description:
When I try the following query using customer-dv deployment against postgresql
https://rdbms-springboot-dv-demo.apps.cluster-london-966d.london-966d.ope...
I get the following error:
{"error":{"code":"TEIID30504","message":"TEIID30504 sampledb: TEIID31176 Could not convert source column v_0.c_1 AS c_3 to the expected runtime type object[][]"}}
This occurs with any pg array that is created with an expression:
select (col, col2)..
array_agg, etc.
was:
When I try the following query using customer-dv deployment against postgresql
https://rdbms-springboot-dv-demo.apps.cluster-london-966d.london-966d.ope...
I get the following error:
{"error":{"code":"TEIID30504","message":"TEIID30504 sampledb: TEIID31176 Could not convert source column v_0.c_1 AS c_3 to the expected runtime type object[][]"}}
Fix Version/s: 13.0.1
12.2.2
12.3.1
Sprint: DV Sprint 56
Summary: Error with pg arrays (was: Odata $expand does not work)
> Error with pg arrays
> --------------------
>
> Key: TEIID-5865
> URL: https://issues.redhat.com/browse/TEIID-5865
> Project: Teiid
> Issue Type: Bug
> Components: OData, Query Engine
> Affects Versions: 12.3
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.2.2, 12.3.1, 13.1, 13.0.1
>
> Original Estimate: 5 hours
> Remaining Estimate: 5 hours
>
> When I try the following query using customer-dv deployment against postgresql
> https://rdbms-springboot-dv-demo.apps.cluster-london-966d.london-966d.ope...
> I get the following error:
> {"error":{"code":"TEIID30504","message":"TEIID30504 sampledb: TEIID31176 Could not convert source column v_0.c_1 AS c_3 to the expected runtime type object[][]"}}
> This occurs with any pg array that is created with an expression:
> select (col, col2)..
> array_agg, etc.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (TEIID-5865) Error with pg arrays
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5865?focusedWorklogId=12448519&pag... ]
Steven Hawkins logged work on TEIID-5865:
-----------------------------------------
Author: Steven Hawkins
Created on: 13/Dec/19 5:19 PM
Start Date: 13/Dec/19 5:19 PM
Worklog Time Spent: 5 hours
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes (was: 5 hours)
Time Spent: 5 hours
Worklog Id: (was: 12448519)
> Error with pg arrays
> --------------------
>
> Key: TEIID-5865
> URL: https://issues.redhat.com/browse/TEIID-5865
> Project: Teiid
> Issue Type: Bug
> Components: OData, Query Engine
> Affects Versions: 12.3
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.2.2, 12.3.1, 13.1, 13.0.1
>
> Original Estimate: 5 hours
> Time Spent: 5 hours
> Remaining Estimate: 0 minutes
>
> When I try the following query using customer-dv deployment against postgresql
> https://rdbms-springboot-dv-demo.apps.cluster-london-966d.london-966d.ope...
> I get the following error:
> {"error":{"code":"TEIID30504","message":"TEIID30504 sampledb: TEIID31176 Could not convert source column v_0.c_1 AS c_3 to the expected runtime type object[][]"}}
> This occurs with any pg array that is created with an expression:
> select (col, col2)..
> array_agg, etc.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years