April 2020 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5926) Issues with policy/grant docs

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5926?focusedWorklogId=12450725&pag... ] Steven Hawkins logged work on TEIID-5926: ----------------------------------------- Author: Steven Hawkins Created on: 03/Apr/20 6:49 PM Start Date: 03/Apr/20 6:49 PM Worklog Time Spent: 1 hour, 30 minutes Issue Time Tracking ------------------- Remaining Estimate: 30 minutes (was: 2 hours) Time Spent: 1 hour, 30 minutes Worklog Id: (was: 12450725) > Issues with policy/grant docs > ----------------------------- > > Key: TEIID-5926 > URL: https://issues.redhat.com/browse/TEIID-5926 > Project: Teiid > Issue Type: Bug > Components: Documentation > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 14.0, 13.1.1 > > Original Estimate: 2 hours > Time Spent: 1 hour, 30 minutes > Remaining Estimate: 30 minutes > > One of the create policy examples is incorrect and some of our existing docs indicated you could use READ as a permission in GRANT, which should actually be SELECT. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5926) Issues with policy/grant docs

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5926: ------------------------------------- Summary: Issues with policy/grant docs Key: TEIID-5926 URL: https://issues.redhat.com/browse/TEIID-5926 Project: Teiid Issue Type: Bug Components: Documentation Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 14.0, 13.1.1 One of the create policy examples is incorrect and some of our existing docs indicated you could use READ as a permission in GRANT, which should actually be SELECT. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-184) Create a common base for salesforce connections

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-184?page=com.atlassian.jira.plug... ] Work on TEIIDSB-184 started by Steven Hawkins. ---------------------------------------------- > Create a common base for salesforce connections > ----------------------------------------------- > > Key: TEIIDSB-184 > URL: https://issues.redhat.com/browse/TEIIDSB-184 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: datasource > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.5.0 > > > The salesforce connection logic was forked for teiid spring boot, we should go back and create a common base. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-184) Create a common base for salesforce connections

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-184?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIIDSB-184: ----------------------------------- Original Estimate: 6 hours Remaining Estimate: 6 hours > Create a common base for salesforce connections > ----------------------------------------------- > > Key: TEIIDSB-184 > URL: https://issues.redhat.com/browse/TEIIDSB-184 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: datasource > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.5.0 > > Original Estimate: 6 hours > Remaining Estimate: 6 hours > > The salesforce connection logic was forked for teiid spring boot, we should go back and create a common base. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5925) Support a materialization on failure action of no cache

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5925?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on TEIID-5925: --------------------------------------- Admittedly there's not a lot of detail in the stackoverflow post, but as described there the pg source is acting as a materialization of the excel data. Only if pg is not available, then consult the excel source. So cache first and if not available then source - which looks like a different on error action. > The way I understood that is, the user always wants to go source without intermediate cache in Teiid, if source not available then failover to the next source that is configured. Will this method avoids that scenario? That's a more general failover scenario. It's made more complicated if you are dealing with heterogeneous sources (pg/excel) as the source metadata won't necessarily line-up across failover targets (multi-source has the same issue) . Ideally we lean on source support where possible to handle failover. There were even a few JDBC projects over the years to provide generic clustering/failover at the driver level. I'd go so far as to say in most homogeneous scenarios involving sql/nosql sources there would be source support of some kind. I see the appeal of fleshing out a general failover feature as that leads to other source query modes, such as parallel execution to obtain the first/fastest result, etc. However if it's primarily for what looks to be a materialization scenario, I'd start there. > Support a materialization on failure action of no cache > ------------------------------------------------------- > > Key: TEIID-5925 > URL: https://issues.redhat.com/browse/TEIID-5925 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.x > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > The stackoverflow user is asking about a failover scenario, which would actually be implemented with materialization - but we lack an on failure option to describe "just use the original view definition". -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5925) Support a materialization on failure action of no cache

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIID-5925?page=com.atlassian.jira.plugi... ] Ramesh Reddy commented on TEIID-5925: ------------------------------------- Yes, I see. The way I understood that is, the user always wants to go source without intermediate cache in Teiid, if source not available then failover to the next source that is configured. Will this method avoids that scenario? Maybe if I understand what you say is, tell the engine that "main source" is where the materialization target is, then failover to the "second source" which is the configured as primary for caching. Am I close? > Support a materialization on failure action of no cache > ------------------------------------------------------- > > Key: TEIID-5925 > URL: https://issues.redhat.com/browse/TEIID-5925 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.x > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > The stackoverflow user is asking about a failover scenario, which would actually be implemented with materialization - but we lack an on failure option to describe "just use the original view definition". -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5925) Support a materialization on failure action of no cache

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5925: ------------------------------------- Summary: Support a materialization on failure action of no cache Key: TEIID-5925 URL: https://issues.redhat.com/browse/TEIID-5925 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 13.x The stackoverflow user is asking about a failover scenario, which would actually be implemented with materialization - but we lack an on failure option to describe "just use the original view definition". -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2020