March 2020 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5917) Update the website

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5917?focusedWorklogId=12450509&pag... ] Steven Hawkins logged work on TEIID-5917: ----------------------------------------- Author: Steven Hawkins Created on: 12/Mar/20 9:51 PM Start Date: 12/Mar/20 9:51 PM Worklog Time Spent: 5 hours Issue Time Tracking ------------------- Remaining Estimate: 5 hours (was: 1 day, 2 hours) Time Spent: 5 hours Worklog Id: (was: 12450509) > Update the website > ------------------ > > Key: TEIID-5917 > URL: https://issues.redhat.com/browse/TEIID-5917 > Project: Teiid > Issue Type: Task > Components: Documentation > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 14.0 > > Original Estimate: 1 day, 2 hours > Time Spent: 5 hours > Remaining Estimate: 5 hours > > The website has not been refreshed in a while. The steps will be: > - basic copy-editing and content refresh > - make things more clearly teiid centric > - determine what to do with the blog. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5917) Update the website

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5917: ------------------------------------- Summary: Update the website Key: TEIID-5917 URL: https://issues.redhat.com/browse/TEIID-5917 Project: Teiid Issue Type: Task Components: Documentation Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 14.0 The website has not been refreshed in a while. The steps will be: - basic copy-editing and content refresh - make things more clearly teiid centric - determine what to do with the blog. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-176) Add support for soap calls

by Steven Hawkins (Jira)

Steven Hawkins created TEIIDSB-176: -------------------------------------- Summary: Add support for soap calls Key: TEIIDSB-176 URL: https://issues.redhat.com/browse/TEIIDSB-176 Project: Teiid Spring Boot Issue Type: Enhancement Components: datasource Reporter: Steven Hawkins Fix For: 1.4.0 In the porting over of the rest logic the soap support was left off. We need to also support soap as a source. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-170) Automate materialization to JDG

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-170?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIIDSB-170: ---------------------------------------- There are two approaches: 1. Handle this as part of codegen based upon ddl/cr. This minimizes changes to the core. 2. Push the handling into the core. This requires adding the concept of an implicit source, something that can be injected into the vdb like our system schema, but with a schema that is generated based upon the materialization targets. Either way we have an issue of discoverability - if/where is the infinipsan operator installed. A lot depends on the assumption of an infinispan cluster per vdb, or a shared cluster for all vdbs. If shared then we need to account for that in the cache naming strategy - in general it be vdb_table_fqn (version would need to be accounted for in core version). We would also only delete the needed caches on start-up/shut-down, rather than destroying the entire cluster. Note the need for the fqn as we can have materialized views in multiple schema in vdb in general, which would all point to the same source schema/cluster. If we do create a cluster per vdb, then the operator will likely need we need the operator to manage the creation / destruction of the cluster (using a cr like the one shown with the transactional cache example) upon the vdb being deployed / undeployed. There is also an issue of security. We can hide the materialization target schema, but we also need to consider if access is allowed at all. At least for syndesis org.teiid.hiddenMetadataResolvable is always set to false so there's not an issue there. In core/teiid spring boot we may need to drive that on a per schema basis. Also captured TEIID-5916 so that we can reach feature parity with internal materialization indexing. It appears we need to change how we are using the Indexed annotation. > 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 > Priority: Major > Fix For: 1.4.0 > > Original Estimate: 1 week > Time Spent: 1 hour > Remaining Estimate: 4 days, 7 hours > > 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)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5916) Add indexes in generated protobuf

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5916: ------------------------------------- Summary: Add indexes in generated protobuf Key: TEIID-5916 URL: https://issues.redhat.com/browse/TEIID-5916 Project: Teiid Issue Type: Enhancement Components: Infinispan Reporter: Steven Hawkins Assignee: Ramesh Reddy Fix For: 14.0 The protobuf logic will mark an entire table as indexed, but that may not line up to what we need. The usage of the Indexed annotation on the message indicates that custom IndexedField annotations will be used to selective enable indexes. This is true whether the cache is marked as indexed (which would be specified in the cache template) or not. If we auto-create an indexed cache, then all fields are automatically indexed and there's no need for the indexed annotation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-170) Automate materialization to JDG

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-170?focusedWorklogId=12450418&pa... ] Steven Hawkins logged work on TEIIDSB-170: ------------------------------------------ Author: Steven Hawkins Created on: 10/Mar/20 9:57 AM Start Date: 10/Mar/20 9:57 AM Worklog Time Spent: 1 hour Issue Time Tracking ------------------- Remaining Estimate: 4 days, 7 hours (was: 1 week) Time Spent: 1 hour Worklog Id: (was: 12450418) > 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 > Priority: Major > Fix For: 1.4.0 > > Original Estimate: 1 week > Time Spent: 1 hour > Remaining Estimate: 4 days, 7 hours > > 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)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-170) Automate materialization to JDG

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-170?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIIDSB-170: ----------------------------------- Original Estimate: 1 week Remaining Estimate: 1 week > 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 > Priority: Major > Fix For: 1.4.0 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > 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)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5859) Upgrade to wildfly 19

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5859?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5859: ---------------------------------- Fix Version/s: 14.0 (was: 13.2) Sprint: DV Sprint 60 Summary: Upgrade to wildfly 19 (was: Upgrade to wildfly 18) > Upgrade to wildfly 19 > --------------------- > > Key: TEIID-5859 > URL: https://issues.redhat.com/browse/TEIID-5859 > Project: Teiid > Issue Type: Task > Components: Build/Kits, Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 14.0 > > > We should pick up the latest wildfly 18+ -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5915) Create 12.3.2 and 13.1.0 Releases

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5915?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-5915. ----------------------------------- Resolution: Done Created the releases and updated the various bits of collateral. > Create 12.3.2 and 13.1.0 Releases > --------------------------------- > > Key: TEIID-5915 > URL: https://issues.redhat.com/browse/TEIID-5915 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > > Creating an issue to represent the release work. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5915) Create 12.3.2 and 13.1.0 Releases

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5915?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5915: ---------------------------------- Original Estimate: 4 hours Remaining Estimate: 4 hours > Create 12.3.2 and 13.1.0 Releases > --------------------------------- > > Key: TEIID-5915 > URL: https://issues.redhat.com/browse/TEIID-5915 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Creating an issue to represent the release work. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2020