February 2020 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5909) Pg compatibility issues to support Graphback API

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIID-5909?page=com.atlassian.jira.plugi... ] Work on TEIID-5909 started by Ramesh Reddy. ------------------------------------------- > Pg compatibility issues to support Graphback API > ------------------------------------------------ > > Key: TEIID-5909 > URL: https://issues.redhat.com/browse/TEIID-5909 > Project: Teiid > Issue Type: Enhancement > Components: ODBC > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 13.1 > > > 1) Graphback expects "select version()" call to return the result set with alias "version" as column name > 2) The client supplies the "utf-8" as the charset, which needs to be treated as UTF-8 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5909) Pg compatibility issues to support Graphback API

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIID-5909: ----------------------------------- Summary: Pg compatibility issues to support Graphback API Key: TEIID-5909 URL: https://issues.redhat.com/browse/TEIID-5909 Project: Teiid Issue Type: Enhancement Components: ODBC Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 13.1 1) Graphback expects "select version()" call to return the result set with alias "version" as column name 2) The client supplies the "utf-8" as the charset, which needs to be treated as UTF-8 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5909) Pg compatibility issues to support Graphback API

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIID-5909?page=com.atlassian.jira.plugi... ] Ramesh Reddy reassigned TEIID-5909: ----------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > Pg compatibility issues to support Graphback API > ------------------------------------------------ > > Key: TEIID-5909 > URL: https://issues.redhat.com/browse/TEIID-5909 > Project: Teiid > Issue Type: Enhancement > Components: ODBC > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 13.1 > > > 1) Graphback expects "select version()" call to return the result set with alias "version" as column name > 2) The client supplies the "utf-8" as the charset, which needs to be treated as UTF-8 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-171) Add an opentracing example

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-171?focusedWorklogId=12450299&pa... ] Ramesh Reddy logged work on TEIIDSB-171: ---------------------------------------- Author: Ramesh Reddy Created on: 21/Feb/20 2:14 PM Start Date: 21/Feb/20 2:13 PM Worklog Time Spent: 2 hours Issue Time Tracking ------------------- Remaining Estimate: 0 minutes Time Spent: 2 hours Worklog Id: (was: 12450299) > Add an opentracing example > -------------------------- > > Key: TEIIDSB-171 > URL: https://issues.redhat.com/browse/TEIIDSB-171 > Project: Teiid Spring Boot > Issue Type: Task > Components: OpenShift > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.4.0 > > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > Provide an example demonstrating end-to-end opentracing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-171) Add an opentracing example

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-171?page=com.atlassian.jira.plug... ] Ramesh Reddy resolved TEIIDSB-171. ---------------------------------- Resolution: Done https://github.com/teiid/teiid-openshift-examples/commit/d73ff355703fc0f3... > Add an opentracing example > -------------------------- > > Key: TEIIDSB-171 > URL: https://issues.redhat.com/browse/TEIIDSB-171 > Project: Teiid Spring Boot > Issue Type: Task > Components: OpenShift > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.4.0 > > > Provide an example demonstrating end-to-end opentracing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-171) Add an opentracing example

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-171?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIIDSB-171: --------------------------------- Story Points: 0.5 Sprint: DV Sprint 59 > Add an opentracing example > -------------------------- > > Key: TEIIDSB-171 > URL: https://issues.redhat.com/browse/TEIIDSB-171 > Project: Teiid Spring Boot > Issue Type: Task > Components: OpenShift > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.4.0 > > > Provide an example demonstrating end-to-end opentracing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5798) Mixed PERMISSION GRANTS

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5798?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on TEIID-5798: --------------------------------------- It seems that there are several issues with our interpretation of ddl imperative grant/revoke vs. the old declarative xml model. First it is not aware of drops: create foreign table t ... revoke insert on t to ... drop table t; create foreign table t ... -- the new t still has insert revoked Next, it is not hierarchical: if you grant / revoke at the database/table/schema level that needs to cascade through the tree of children. grant ... revoke ... -- etc. grant all on database to superuser; -- should remove all revokes > Mixed PERMISSION GRANTS > ----------------------- > > Key: TEIID-5798 > URL: https://issues.redhat.com/browse/TEIID-5798 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Christoph John > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.1 > > Original Estimate: 6 hours > Time Spent: 4 hours > Remaining Estimate: 1 day, 6 hours > > Hello, > I am currently trying to set a set of permissions on a table/view. Hence a condition on INSERT,UPDATE,DELETE and an unconditioned SELECT. > However, it seems that conditioned and unconditioned GRANT statements do not work together. > {code} > GRANT INSERT,UPDATE,DELETE ON TABLE "my_nutri_diary.UserDefinedProducts_SRC" CONDITION 'UserDefinedProducts_SRC.fkProfile in (SELECT Account.idProfile FROM Account WHERE Account.uuidUser = LEFT(user(), 36) )' TO odata; > GRANT SELECT ON TABLE "my_nutri_diary.UserDefinedProducts_SRC" TO odata; > REVOKE ALTER,EXECUTE ON TABLE "my_nutri_diary.UserDefinedProducts_SRC" FROM odata; > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-39) Create launcher for delivery on https://launch.openshift.io/launch/

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-39?page=com.atlassian.jira.plugi... ] Ramesh Reddy resolved TEIIDSB-39. --------------------------------- Resolution: Out of Date > Create launcher for delivery on https://launch.openshift.io/launch/ > ------------------------------------------------------------------- > > Key: TEIIDSB-39 > URL: https://issues.redhat.com/browse/TEIIDSB-39 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: OpenShift > Reporter: Van Halbert > Priority: Major > > Create a launcher that will enable it to be used here https://launch.openshift.io/launch/ -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 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 updated TEIIDSB-170: --------------------------------- Fix Version/s: 1.5.0 > 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 > > > 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, 3 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 updated TEIIDSB-170: --------------------------------- Fix Version/s: (was: 1.5.0) > 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 > > > 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, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2020