April 2020 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5872) Excel translator should support reading file from Amazon S3

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIID-5872?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-5872: -------------------------------- Sprint: DV Sprint 63 (was: DV Sprint 59) > Excel translator should support reading file from Amazon S3 > ----------------------------------------------------------- > > Key: TEIID-5872 > URL: https://issues.redhat.com/browse/TEIID-5872 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 14.0 > > > Excel translator should support reading data from Amazon S3 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

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

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-170?focusedWorklogId=12450895&pa... ] Ramesh Reddy logged work on TEIIDSB-170: ---------------------------------------- Author: Ramesh Reddy Created on: 26/Apr/20 3:52 PM Start Date: 26/Apr/20 3:51 PM Worklog Time Spent: 3 days Work Description: Work in the Operator and fixes in the Teiid Spring Boot Issue Time Tracking ------------------- Remaining Estimate: 5 hours (was: 3 days, 5 hours) Time Spent: 4 days, 3 hours (was: 1 day, 3 hours) Worklog Id: (was: 12450895) > 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.5.0 > > Original Estimate: 1 week > Time Spent: 4 days, 3 hours > Remaining Estimate: 5 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)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5943) Status table not found when model is not visible

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIID-5943?page=com.atlassian.jira.plugi... ] Ramesh Reddy commented on TEIID-5943: ------------------------------------- Yeah, I do not remember setting in the Teiid Spring Boot. What do I need to set, a system property? Then we can move this to TEIIDSB > Status table not found when model is not visible > ------------------------------------------------ > > Key: TEIID-5943 > URL: https://issues.redhat.com/browse/TEIID-5943 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > > When materialization schema is hidden and the Materilization Status table is part of it, then references to it from Materialization scripts is not found and load auto management fails. > A workaround is simple to make model visible -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5943) Status table not found when model is not visible

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5943?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on TEIID-5943: --------------------------------------- That's probably a side effect of the new setting for whether hidden is resolvable, which by default it is not for syndesis. I don't recall if we made that a general change for teiid spring boot as well. > Status table not found when model is not visible > ------------------------------------------------ > > Key: TEIID-5943 > URL: https://issues.redhat.com/browse/TEIID-5943 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > > When materialization schema is hidden and the Materilization Status table is part of it, then references to it from Materialization scripts is not found and load auto management fails. > A workaround is simple to make model visible -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5944) Infinispan protobuf generation fails to validate name with "-" in them

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIID-5944: ----------------------------------- Summary: 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 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)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5943) Status table not found when model is not visible

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIID-5943: ----------------------------------- Summary: Status table not found when model is not visible Key: TEIID-5943 URL: https://issues.redhat.com/browse/TEIID-5943 Project: Teiid Issue Type: Bug Components: Query Engine Reporter: Ramesh Reddy Assignee: Steven Hawkins When materialization schema is hidden and the Materilization Status table is part of it, then references to it from Materialization scripts is not found and load auto management fails. A workaround is simple to make model visible -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5872) Excel translator should support reading file from Amazon S3

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIID-5872?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-5872: -------------------------------- Sprint: (was: DV Sprint 62) > Excel translator should support reading file from Amazon S3 > ----------------------------------------------------------- > > Key: TEIID-5872 > URL: https://issues.redhat.com/browse/TEIID-5872 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 14.0 > > > Excel translator should support reading data from Amazon S3 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5872) Excel translator should support reading file from Amazon S3

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIID-5872?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-5872: -------------------------------- Sprint: DV Sprint 59 > Excel translator should support reading file from Amazon S3 > ----------------------------------------------------------- > > Key: TEIID-5872 > URL: https://issues.redhat.com/browse/TEIID-5872 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 14.0 > > > Excel translator should support reading data from Amazon S3 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

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

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-170?page=com.atlassian.jira.plug... ] Ramesh Reddy commented on TEIIDSB-170: -------------------------------------- After thinking a little more, I think the user should not create `CacheStore` in the YAML file at all, as all the materialization decoration/enhancements are occurring without user input, this should be no different. Instead the user just deploys a YAML file, however if Operator finds a secret with name "{vdb-name}-cachestore" or "teiid-cacheStore" then it can read credentials from the secret and configures the rest as defined in above comment. If not found, no changes will be made to the VDB. > 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.5.0 > > Original Estimate: 1 week > Time Spent: 1 day, 3 hours > Remaining Estimate: 3 days, 5 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)

5 years, 11 months

1
0
0 / 0

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

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-170?page=com.atlassian.jira.plug... ] Ramesh Reddy commented on TEIIDSB-170: -------------------------------------- The approach I will be taking is using a shared Infinispan cluster, where user is responsible for creating the cluster and providing the connection details in the form of a `Datasource` properties in the YAML file. The DataSource name MUST be named `CacheStore`, when Operator runs it will find this Datastore and generate and run the S2I build, in the maven build then uses `vdb-codegen-plugin` a generate a new VDB, where all the Views with `materialized = true` flag without an external materialization target set are picked and copied/cloned into a separate schema called `materialized` with their fully qualified name. The status table also gets created in the same schema. A VDB with the name `materialized.ddl` gets generated and put on the classpath. Then Operator in the next step will adjust the `application.properties` to point to the new `materialized.ddl` VDB and loads the VDB. > 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.5.0 > > Original Estimate: 1 week > Time Spent: 1 day, 3 hours > Remaining Estimate: 3 days, 5 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)

5 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2020