May 2020 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5948) merge the mysql and mysql5 translators

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5948?focusedWorklogId=12450940&pag... ] Steven Hawkins logged work on TEIID-5948: ----------------------------------------- Author: Steven Hawkins Created on: 03/May/20 9:46 PM Start Date: 03/May/20 9:46 PM Worklog Time Spent: 2 hours, 30 minutes Issue Time Tracking ------------------- Remaining Estimate: 1 hour, 30 minutes (was: 4 hours) Time Spent: 2 hours, 30 minutes Worklog Id: (was: 12450940) > merge the mysql and mysql5 translators > -------------------------------------- > > Key: TEIID-5948 > URL: https://issues.redhat.com/browse/TEIID-5948 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 14.0, 13.1.1 > > Original Estimate: 4 hours > Time Spent: 2 hours, 30 minutes > Remaining Estimate: 1 hour, 30 minutes > > To create a single translator name, we should merge the two implementations. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5948) merge the mysql and mysql5 translators

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5948?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-5948. ----------------------------------- Fix Version/s: 13.1.1 Resolution: Done Merged the logic, but left the mysql5 for backwards compatibility. There is some logic to try and prevent the need to specify the database version even if it can't be detected - which would be similar to the old behavior. > merge the mysql and mysql5 translators > -------------------------------------- > > Key: TEIID-5948 > URL: https://issues.redhat.com/browse/TEIID-5948 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 14.0, 13.1.1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > To create a single translator name, we should merge the two implementations. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 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 edited comment on TEIIDSB-170 at 5/1/20 6:27 PM: -------------------------------------------------------------- Will be adding the following environment properties to the Pod from the Operator - TEIID_NODENAME - OpenShift Node Name where the Pod exists - TEIID_PODNAME - Pod Name - TEIID_LABELS - Labels set on the CR The Materialization tables will be added with a random name in them, so that there will be no collisions in rollup deployments of VDBs was (Author: rareddy): Will be adding the following environment properties to the Pod from the Operator - TEIID_NODENAME - OpenShift Node Name where the Pod exists - TEIID_PODIP - Pod IP - TEIID_LABELS - Labels set on the CR The Materialization tables will be added with a random name in them, so that there will be no collisions in rollup deployments of VDBs > 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 week, 1 day, 2 hours > Remaining Estimate: 0 minutes > > 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, 7 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: -------------------------------------- Will be adding the following environment properties to the Pod from the Operator - TEIID_NODENAME - OpenShift Node Name where the Pod exists - TEIID_PODIP - Pod IP - TEIID_LABELS - Labels set on the CR The Materialization tables will be added with a random name in them, so that there will be no collisions in rollup deployments of VDBs > 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 week, 1 day, 2 hours > Remaining Estimate: 0 minutes > > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5948) merge the mysql and mysql5 translators

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5948: ------------------------------------- Summary: merge the mysql and mysql5 translators Key: TEIID-5948 URL: https://issues.redhat.com/browse/TEIID-5948 Project: Teiid Issue Type: Quality Risk Components: JDBC Connector Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 14.0 To create a single translator name, we should merge the two implementations. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5946) condition support for masks needs restored

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5946?focusedWorklogId=12450931&pag... ] Steven Hawkins logged work on TEIID-5946: ----------------------------------------- Author: Steven Hawkins Created on: 01/May/20 10:40 AM Start Date: 01/May/20 10:40 AM Worklog Time Spent: 2 hours, 30 minutes Issue Time Tracking ------------------- Remaining Estimate: 1 hour, 30 minutes (was: 4 hours) Time Spent: 2 hours, 30 minutes Worklog Id: (was: 12450931) > condition support for masks needs restored > ------------------------------------------ > > Key: TEIID-5946 > URL: https://issues.redhat.com/browse/TEIID-5946 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 14.0, 13.1.1 > > Original Estimate: 4 hours > Time Spent: 2 hours, 30 minutes > Remaining Estimate: 1 hour, 30 minutes > > Cleanup in TEIID-4770 TEIID-4771 removed the ability to set a condition with a mask - more than likely to avoid specifying whether the condition was a constraint. That should be added back. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5946) condition support for masks needs restored

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5946?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5946: ---------------------------------- Original Estimate: 4 hours Remaining Estimate: 4 hours > condition support for masks needs restored > ------------------------------------------ > > Key: TEIID-5946 > URL: https://issues.redhat.com/browse/TEIID-5946 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 14.0, 13.1.1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Cleanup in TEIID-4770 TEIID-4771 removed the ability to set a condition with a mask - more than likely to avoid specifying whether the condition was a constraint. That should be added back. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5946) condition support for masks needs restored

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5946?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-5946. ----------------------------------- Resolution: Done Added back handling for mask conditions. It will accept either a string literal (for legacy consistency with the other grant statements) or an expression. > condition support for masks needs restored > ------------------------------------------ > > Key: TEIID-5946 > URL: https://issues.redhat.com/browse/TEIID-5946 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 14.0, 13.1.1 > > > Cleanup in TEIID-4770 TEIID-4771 removed the ability to set a condition with a mask - more than likely to avoid specifying whether the condition was a constraint. That should be added back. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

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

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIID-5916?page=com.atlassian.jira.plugi... ] Ramesh Reddy resolved TEIID-5916. --------------------------------- Resolution: Done Added @Feild(index=Index.YES) for Primary, Unique and Index keys on any protobuf message for any table for Infinispan access > 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 > Priority: Major > Fix For: 14.0 > > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > 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, 7 months

1
0
0 / 0

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

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIID-5916?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-5916: -------------------------------- Story Points: 0.5 (was: 1) > 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 > Priority: Major > Fix For: 14.0 > > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > 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, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2020