[JBoss JIRA] (TEIIDSB-201) Add cassandra support to code-gen / operator
by Steven Hawkins (Jira)
Steven Hawkins created TEIIDSB-201:
--------------------------------------
Summary: Add cassandra support to code-gen / operator
Key: TEIIDSB-201
URL: https://issues.redhat.com/browse/TEIIDSB-201
Project: Teiid Spring Boot
Issue Type: Enhancement
Components: datasource, OpenShift
Reporter: Steven Hawkins
Assignee: Ramesh Reddy
Fix For: 1.6.0
Now that cassandra support has been added it should be available for use in a crd.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (TEIIDSB-169) JDG caching for multi-pod dv
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-169?page=com.atlassian.jira.plug... ]
Steven Hawkins commented on TEIIDSB-169:
----------------------------------------
Which is fine. That replaces only the key replication piece. The rest will require Teiid changes.
> 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
> Priority: Major
> Fix For: 1.5.0
>
>
> 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)
4 years, 7 months
[JBoss JIRA] (TEIIDSB-169) JDG caching for multi-pod dv
by Ramesh Reddy (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-169?page=com.atlassian.jira.plug... ]
Ramesh Reddy commented on TEIIDSB-169:
--------------------------------------
[~shawkins] As the first part of the result cache, I am going to replace the caffeine cache with the Infinispan cache based on the data source already created for the materialization. Since this data source gets created if Infinispan is available there is no separate configuration needed.
> 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
> Priority: Major
> Fix For: 1.5.0
>
>
> 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)
4 years, 7 months
[JBoss JIRA] (TEIID-5928) Allow External and Internal materialization of multi-source to fail/update individually
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5928?page=com.atlassian.jira.plugi... ]
Steven Hawkins updated TEIID-5928:
----------------------------------
Fix Version/s: 14.1
Original Estimate: 0 minutes
Story Points: 1 (was: 0.1)
Sprint: (was: DV Sprint 63)
> Allow External and Internal materialization of multi-source to fail/update individually
> ---------------------------------------------------------------------------------------
>
> Key: TEIID-5928
> URL: https://issues.redhat.com/browse/TEIID-5928
> Project: Teiid
> Issue Type: Enhancement
> Components: Common
> Affects Versions: 12.2.2
> Reporter: Rafael Sampaio
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 14.1
>
> Original Estimate: 0 minutes
> Time Spent: 30 minutes
> Remaining Estimate: 0 minutes
>
> Hi, all.
> First of all thanks in advance for your attention, and efforts on such a great product.
> Since I haven't found any docs or examples regarding my current usage (please if this already exists or there's a better way of doing this, disregard this request and advice) here goes my suggestion:
> It would be nice to have a way to gracefully update/fail per source, if a view that has Materialization enabled and target a multi-source source model, because things can get, messy if I have to create a view per source and Materialize each one and only then create a unified (UNION) view.
> Using this approach also obligates me to implement custom insert/update/delete/based on the discriminator column.
> Thanks again.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (TEIID-5944) Infinispan protobuf generation fails to validate name with "-" in them
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5944?page=com.atlassian.jira.plugi... ]
Steven Hawkins resolved TEIID-5944.
-----------------------------------
Fix Version/s: 14.0
Resolution: Done
Added validation and made the usage of name in source more consistent - one issue with that from a protobuf generation is that the nis is supposed to be qualified, so we assume there can be a single qualification in the schema to protobuf logic. Opted against an auto-correction scheme as that involves setting the name in source property (which may already be set), ensuring uniqueness, and aligning with any of the other existing properties.
> Infinispan protobuf generation fails to validate name with "-" in them
> ----------------------------------------------------------------------
>
> Key: TEIID-5944
> URL: https://issues.redhat.com/browse/TEIID-5944
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 14.0
>
>
> When the name of the view contains like "mat-example_vix" the protobuf generation seems to succeed however the validation of it by the Infinispan seems to fail.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (TEIID-5944) Infinispan protobuf generation fails to validate name with "-" in them
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5944?focusedWorklogId=12451034&pag... ]
Steven Hawkins logged work on TEIID-5944:
-----------------------------------------
Author: Steven Hawkins
Created on: 14/May/20 8:45 AM
Start Date: 14/May/20 8:45 AM
Worklog Time Spent: 2 hours
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes (was: 2 hours)
Time Spent: 2 hours
Worklog Id: (was: 12451034)
> Infinispan protobuf generation fails to validate name with "-" in them
> ----------------------------------------------------------------------
>
> Key: TEIID-5944
> URL: https://issues.redhat.com/browse/TEIID-5944
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 14.0
>
> Original Estimate: 2 hours
> Time Spent: 2 hours
> Remaining Estimate: 0 minutes
>
> When the name of the view contains like "mat-example_vix" the protobuf generation seems to succeed however the validation of it by the Infinispan seems to fail.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months