May 2020 - teiid-issues - Jboss List Archives

[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 reopened TEIID-5944: ----------------------------------- > 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 > > 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

1
0
0 / 0

[JBoss JIRA] (TEIID-5762) Update security configuration to elytron

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5762?page=com.atlassian.jira.plugi... ] Work on TEIID-5762 started by Steven Hawkins. --------------------------------------------- > Update security configuration to elytron > ---------------------------------------- > > Key: TEIID-5762 > URL: https://issues.redhat.com/browse/TEIID-5762 > Project: Teiid > Issue Type: Sub-task > Components: Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 14.0 > > > The Teiid configuration is based upon an out-dated version of the wildfly config. It should be brought up-to-date. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-192) Document migration for alias names

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-192?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIIDSB-192: ---------------------------------------- The datasources adoc has now been updated. > Document migration for alias names > ---------------------------------- > > Key: TEIIDSB-192 > URL: https://issues.redhat.com/browse/TEIIDSB-192 > Project: Teiid Spring Boot > Issue Type: Task > Components: documentation > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.5.0 > > Original Estimate: 4 hours > Time Spent: 4 hours > Remaining Estimate: 0 minutes > > Translators like salesforce and actian-vector has new name in the spring boot, we need to either document or switch back to original names. > Also if we are updating migration utilities we can build in smarts into it. -- 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?focusedWorklogId=12451030&pa... ] Ramesh Reddy logged work on TEIIDSB-170: ---------------------------------------- Author: Ramesh Reddy Created on: 13/May/20 4:26 PM Start Date: 13/May/20 4:25 PM Worklog Time Spent: 4 days Work Description: misc work with parser spike or reworking the regex and documentation etc. Issue Time Tracking ------------------- Time Spent: 2 weeks, 2 days, 2 hours (was: 1 week, 3 days, 2 hours) Worklog Id: (was: 12451030) > 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: 2 weeks, 2 days, 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 resolved TEIIDSB-170. ---------------------------------- Resolution: Done Initial automation of the Infinispan cluster is finished, there is further work as defined in TEIIDSB-169 The current documentation can be found at https://github.com/teiid/teiid-openshift-examples/blob/master/materializi... [~shawkins] can you review the above docs and we will change or enhance accordingly. > 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, 3 days, 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-172) Need to implement oauth2 and jwt auth in Salesforce

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-172?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIIDSB-172: --------------------------------- Fix Version/s: (was: 1.5.0) > Need to implement oauth2 and jwt auth in Salesforce > --------------------------------------------------- > > Key: TEIIDSB-172 > URL: https://issues.redhat.com/browse/TEIIDSB-172 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: datasource > Reporter: Renat Eskenin > Priority: Major > > We use oauth2 and jwt authentication for SalesForce and now in Teiid spring boot we have only user/password auth. > Please implement jwt and oauth2 authentications by spring properties. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-163) Provide pooling for BaseConnectionFactory sources

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-163?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIIDSB-163: --------------------------------- Fix Version/s: (was: 1.5.0) > Provide pooling for BaseConnectionFactory sources > ------------------------------------------------- > > Key: TEIIDSB-163 > URL: https://issues.redhat.com/browse/TEIIDSB-163 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: datasource > Reporter: Steven Hawkins > Priority: Major > > It will depend on the source and the cost of creating a connection, but in general we should provide pooling for connections rather than creating the for every operation. For example salesforce is a heavy weight connection. > The pooling will need to be tied into spring security or jca like logic to properly manage connections by identity once we re-establish that logic. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-150) Micrometer spike

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-150?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIIDSB-150: --------------------------------- Fix Version/s: (was: 1.5.0) > Micrometer spike > ---------------- > > Key: TEIIDSB-150 > URL: https://issues.redhat.com/browse/TEIIDSB-150 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: core > Reporter: Steven Hawkins > Priority: Major > > This work will wind up in Teiid spring boot (and even teiid), but the driver is from this project. We need to examine the level of effort of converting to micrometer rather than just jmx metrics for better spring integration. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-199) Teiid logging level env vars are not supported

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-199?page=com.atlassian.jira.plug... ] Ramesh Reddy resolved TEIIDSB-199. ---------------------------------- Resolution: Done Added support and documentation for this > Teiid logging level env vars are not supported > ---------------------------------------------- > > Key: TEIIDSB-199 > URL: https://issues.redhat.com/browse/TEIIDSB-199 > Project: Teiid Spring Boot > Issue Type: Bug > Components: core > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.5.0 > > > There are two undocumented env vars to enable source query logging, {{LOGGING_LEVEL_ORG_TEIID_COMMAND_LOG}} and {{LOGGING_LEVEL_ORG_TEIID_COMMAND_LOG_SOURCE}} . These should be documented to allow debugging of query-level issues. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-199) Teiid logging level env vars are not supported

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-199?focusedWorklogId=12451029&pa... ] Ramesh Reddy logged work on TEIIDSB-199: ---------------------------------------- Author: Ramesh Reddy Created on: 13/May/20 1:41 PM Start Date: 13/May/20 1:41 PM Worklog Time Spent: 3 hours Issue Time Tracking ------------------- Remaining Estimate: 0 minutes Time Spent: 3 hours Worklog Id: (was: 12451029) > Teiid logging level env vars are not supported > ---------------------------------------------- > > Key: TEIIDSB-199 > URL: https://issues.redhat.com/browse/TEIIDSB-199 > Project: Teiid Spring Boot > Issue Type: Bug > Components: core > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.5.0 > > Time Spent: 3 hours > Remaining Estimate: 0 minutes > > There are two undocumented env vars to enable source query logging, {{LOGGING_LEVEL_ORG_TEIID_COMMAND_LOG}} and {{LOGGING_LEVEL_ORG_TEIID_COMMAND_LOG_SOURCE}} . These should be documented to allow debugging of query-level issues. -- 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