[JBoss JIRA] (TEIID-5906) Occasional test failure
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5906?focusedWorklogId=12450201&pag... ]
Steven Hawkins logged work on TEIID-5906:
-----------------------------------------
Author: Steven Hawkins
Created on: 17/Feb/20 7:45 AM
Start Date: 17/Feb/20 7:45 AM
Worklog Time Spent: 1 hour
Issue Time Tracking
-------------------
Remaining Estimate: 5 hours (was: 6 hours)
Time Spent: 1 hour
Worklog Id: (was: 12450201)
> Occasional test failure
> -----------------------
>
> Key: TEIID-5906
> URL: https://issues.redhat.com/browse/TEIID-5906
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 13.x
>
> Original Estimate: 6 hours
> Time Spent: 1 hour
> Remaining Estimate: 5 hours
>
> TestWithClauseProcessing.testWithImplicitIndexing fails occasionally. Locally I have reproduced this after ~700 runs of the test.
> I'm not sure at this point what is introducing the non-determinism. I'll check if we need a better bound or if there is something deeper failing.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (TEIID-5906) Occasional test failure
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5906?page=com.atlassian.jira.plugi... ]
Steven Hawkins updated TEIID-5906:
----------------------------------
Original Estimate: 6 hours
Remaining Estimate: 6 hours
> Occasional test failure
> -----------------------
>
> Key: TEIID-5906
> URL: https://issues.redhat.com/browse/TEIID-5906
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 13.x
>
> Original Estimate: 6 hours
> Remaining Estimate: 6 hours
>
> TestWithClauseProcessing.testWithImplicitIndexing fails occasionally. Locally I have reproduced this after ~700 runs of the test.
> I'm not sure at this point what is introducing the non-determinism. I'll check if we need a better bound or if there is something deeper failing.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (TEIID-5906) Occasional test failure
by Steven Hawkins (Jira)
Steven Hawkins created TEIID-5906:
-------------------------------------
Summary: Occasional test failure
Key: TEIID-5906
URL: https://issues.redhat.com/browse/TEIID-5906
Project: Teiid
Issue Type: Bug
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 13.x
TestWithClauseProcessing.testWithImplicitIndexing fails occasionally. Locally I have reproduced this after ~700 runs of the test.
I'm not sure at this point what is introducing the non-determinism. I'll check if we need a better bound or if there is something deeper failing.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (TEIIDSB-154) Create an example of materialization with JDG on openshift
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-154?focusedWorklogId=12450199&pa... ]
Steven Hawkins logged work on TEIIDSB-154:
------------------------------------------
Author: Steven Hawkins
Created on: 17/Feb/20 7:41 AM
Start Date: 17/Feb/20 7:41 AM
Worklog Time Spent: 4 hours
Issue Time Tracking
-------------------
Remaining Estimate: 2 hours (was: 6 hours)
Time Spent: 1 day, 5 hours (was: 1 day, 1 hour)
Worklog Id: (was: 12450199)
> Create an example of materialization with JDG on openshift
> ----------------------------------------------------------
>
> Key: TEIIDSB-154
> URL: https://issues.redhat.com/browse/TEIIDSB-154
> Project: Teiid Spring Boot
> Issue Type: Sub-task
> Components: documentation, examples
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 1.4.0
>
> Original Estimate: 1 day, 7 hours
> Time Spent: 1 day, 5 hours
> Remaining Estimate: 2 hours
>
> Create an example showing materialization with JDG on openshift.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[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:
----------------------------------------
Captured TEIIDSB-169 and TEIIDSB-170 as next steps.
> 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.4.0
>
> Time Spent: 2 hours
> Remaining Estimate: 0 minutes
>
> 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)
6 years, 1 month
[JBoss JIRA] (TEIIDSB-170) Automate materialization to JDG
by Steven Hawkins (Jira)
Steven Hawkins created TEIIDSB-170:
--------------------------------------
Summary: Automate materialization to JDG
Key: TEIIDSB-170
URL: https://issues.redhat.com/browse/TEIIDSB-170
Project: Teiid Spring Boot
Issue Type: Enhancement
Components: OpenShift
Reporter: Steven Hawkins
Assignee: Ramesh Reddy
Create an internal materialization replacement needs that is turnkey materialization to JDG (little to no user setup required)
- the operator may create the infinispan cluster if needed
- the status table and internal representation of the materialization target would be setup automatically
For the user this would be as simple marking a view as materialized and then it would be populated in jdg upon deployment. They would not have any concerns with cache naming, status tables, etc.
For simplicity the initial version would make a similar assumption to the current internal logic - it is for only a specific vdb. If the vdb cr is modified, then it's expected that the cache would be recreated.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (TEIIDSB-169) JDG caching for multi-pod dv
by Steven Hawkins (Jira)
Steven Hawkins created TEIIDSB-169:
--------------------------------------
Summary: JDG caching for multi-pod dv
Key: TEIIDSB-169
URL: https://issues.redhat.com/browse/TEIIDSB-169
Project: Teiid Spring Boot
Issue Type: Enhancement
Components: OpenShift
Reporter: Steven Hawkins
Assignee: Ramesh Reddy
For multi-pod support we need to:
* Result set caching needs to directly write batches / results to JDG rather than relying upon on demand replication.
* replace the logic that detect failed materialization loads
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[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:
--------------------------------------
Ok, I am fine splitting too. Then we can track that work towards the next release.
> 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.4.0
>
> Time Spent: 2 hours
> Remaining Estimate: 0 minutes
>
> 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)
6 years, 1 month