February 2020 - teiid-issues - Jboss List Archives

[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: --------------------------------- Story Points: 4 > 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.4.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, 1 month

1
0
0 / 0

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

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5798?focusedWorklogId=12450349&pag... ] Steven Hawkins logged work on TEIID-5798: ----------------------------------------- Author: Steven Hawkins Created on: 28/Feb/20 3:45 PM Start Date: 28/Feb/20 3:44 PM Worklog Time Spent: 2 hours, 30 minutes Work Description: for doc updates and second commit for migration Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 2 hours) Time Spent: 2 days, 2 hours, 30 minutes (was: 2 days) Worklog Id: (was: 12450349) > 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: 2 days, 2 hours, 30 minutes > Remaining Estimate: 0 minutes > > 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, 1 month

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: --------------------------------------- Added another commit that will write ddl out with policies instead of grants with conditions. It does not seem like a good idea to do this inline as we have odd side effects. This will serve as the migration mechanism. > 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: 2 days > Remaining Estimate: 2 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, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5908) Issue with "timestamp with timezone" redshift data type

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5908?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5908: ---------------------------------- Fix Version/s: 13.x > Issue with "timestamp with timezone" redshift data type > ------------------------------------------------------- > > Key: TEIID-5908 > URL: https://issues.redhat.com/browse/TEIID-5908 > Project: Teiid > Issue Type: Bug > Reporter: Chandra Akkinepalli > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.x > > > Our data source is redshift and we are using redshift translator in JDV. > The source table has a couple of fields with data type "timestamp with timezone". This is field is mapped to Teiid source model with a data type timestamp. For some reason we are receiving following error when running a query on the table with this field in VDB. > *"SQL Error [30504] [50000]: TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 SRC_RS_HYDRA: 22003 Unexpected exception while translating results: [Amazon][JDBC](10140) Error converting value to Timestamp"* > The fields which have source data type of "timestamp without timezone" mapped to teiid data type of timestamp work just fine. > Please let me know if you have any questions. > Thanks, > Chandra -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

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

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5872?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5872: ---------------------------------- Fix Version/s: 13.2 (was: 13.1) > 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: 13.2 > > > Excel translator should support reading data from Amazon S3 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5852) views are resolved twice in the metadata validator

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5852?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5852: ---------------------------------- Original Estimate: 5 hours Remaining Estimate: 5 hours Sprint: DV Sprint 60 > views are resolved twice in the metadata validator > -------------------------------------------------- > > Key: TEIID-5852 > URL: https://issues.redhat.com/browse/TEIID-5852 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.1 > > Original Estimate: 5 hours > Remaining Estimate: 5 hours > > There is an initial resolve to run the Validation visitor, then another resolve in resolveView. This should be combined as much as possible. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5852) views are resolved twice in the metadata validator

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5852?focusedWorklogId=12450347&pag... ] Steven Hawkins logged work on TEIID-5852: ----------------------------------------- Author: Steven Hawkins Created on: 28/Feb/20 1:13 PM Start Date: 28/Feb/20 1:13 PM Worklog Time Spent: 2 hours, 30 minutes Issue Time Tracking ------------------- Remaining Estimate: 2 hours, 30 minutes (was: 5 hours) Time Spent: 2 hours, 30 minutes Worklog Id: (was: 12450347) > views are resolved twice in the metadata validator > -------------------------------------------------- > > Key: TEIID-5852 > URL: https://issues.redhat.com/browse/TEIID-5852 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.1 > > Original Estimate: 5 hours > Time Spent: 2 hours, 30 minutes > Remaining Estimate: 2 hours, 30 minutes > > There is an initial resolve to run the Validation visitor, then another resolve in resolveView. This should be combined as much as possible. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5852) views are resolved twice in the metadata validator

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5852?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-5852. ----------------------------------- Resolution: Done Removed just the re-parsing of the view sql. > views are resolved twice in the metadata validator > -------------------------------------------------- > > Key: TEIID-5852 > URL: https://issues.redhat.com/browse/TEIID-5852 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.1 > > > There is an initial resolve to run the Validation visitor, then another resolve in resolveView. This should be combined as much as possible. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-173) MongoDB does not support transactions

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-173?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIIDSB-173: ---------------------------------------- It would relate to the connection pool work. On the Teiid side the connection provides a LocalTransaction to the JCA layer. > MongoDB does not support transactions > ------------------------------------- > > Key: TEIIDSB-173 > URL: https://issues.redhat.com/browse/TEIIDSB-173 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: datasource > Reporter: Steven Hawkins > Priority: Major > > In the port from Teiid to Teiid Spring Boot, mongodb no longer supports transactions. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-173) MongoDB does not support transactions

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-173?page=com.atlassian.jira.plug... ] Ramesh Reddy commented on TEIIDSB-173: -------------------------------------- What needs to be done for this? > MongoDB does not support transactions > ------------------------------------- > > Key: TEIIDSB-173 > URL: https://issues.redhat.com/browse/TEIIDSB-173 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: datasource > Reporter: Steven Hawkins > Priority: Major > > In the port from Teiid to Teiid Spring Boot, mongodb no longer supports transactions. -- 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 February 2020