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: --------------------------------- 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)

6 years, 1 month

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)

6 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: --------------------------------------- I've circled back to this. If I can fit this in by end of week, then it should be good for 13.1. However I'm not liking the scope of the changes. We effectively have 3 domains for the security constructs - ddl, xml, and runtime - and there's quite a bit or wiring to introduce a new construct. > 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)

6 years, 1 month

1
0
0 / 0

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

by Chandra Akkinepalli (Jira)

Chandra Akkinepalli created TEIID-5908: ------------------------------------------ Summary: 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 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)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5900) query with local and remote pushes too much to remote

by Ken Geis (Jira)

[ https://issues.redhat.com/browse/TEIID-5900?page=com.atlassian.jira.plugi... ] Ken Geis commented on TEIID-5900: --------------------------------- I am currently unable to reproduce my issue. Perhaps my DBAs changed something on the database side. > query with local and remote pushes too much to remote > ----------------------------------------------------- > > Key: TEIID-5900 > URL: https://issues.redhat.com/browse/TEIID-5900 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 12.3.1 > Reporter: Ken Geis > Assignee: Steven Hawkins > Priority: Major > > I have a table "A" in an Oracle database. I have a date dimension "B" in Teiid, which is a materialized view of a recursive query. The date dimension has all dates from 1950 to 2050, 36890 rows in total. > I run the following query: > {code:sql} > SELECT * > FROM a > JOIN b > ON a.date_column = b.date_key > {code} > Teiid sends a query to Oracle, which I will paraphrase as: > {code:sql} > SELECT <columns> > FROM a > WHERE date_column IN (to_date('1950-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS'), > <36899 other date values!>) > {code} > Oracle breaks either with the length of the query or the number of options in the IN clause. > I thought that MAKEDEP/MAKENOTDEP/MAKEIND could help, but they didn't seem to change anything. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5907) Fix PNC build issues related to building int.next

by Van Halbert (Jira)

[ https://issues.redhat.com/browse/TEIID-5907?page=com.atlassian.jira.plugi... ] Van Halbert updated TEIID-5907: ------------------------------- Git Pull Request: https://github.com/teiid/teiid/pull/1237 > Fix PNC build issues related to building int.next > ------------------------------------------------- > > Key: TEIID-5907 > URL: https://issues.redhat.com/browse/TEIID-5907 > Project: Teiid > Issue Type: Quality Risk > Components: Build/Kits > Affects Versions: 13.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5907) Fix PNC build issues related to building int.next

by Van Halbert (Jira)

[ https://issues.redhat.com/browse/TEIID-5907?page=com.atlassian.jira.plugi... ] Van Halbert commented on TEIID-5907: ------------------------------------ saxon-xom: Found duplicate and different classes in [jaxen:jaxen:1.1.6, xml-apis:xml-apis:1.4.01]: [WARNING] org.w3c.dom.UserDataHandler > Fix PNC build issues related to building int.next > ------------------------------------------------- > > Key: TEIID-5907 > URL: https://issues.redhat.com/browse/TEIID-5907 > Project: Teiid > Issue Type: Quality Risk > Components: Build/Kits > Affects Versions: 13.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5907) Fix PNC build issues related to building int.next

by Van Halbert (Jira)

Van Halbert created TEIID-5907: ---------------------------------- Summary: Fix PNC build issues related to building int.next Key: TEIID-5907 URL: https://issues.redhat.com/browse/TEIID-5907 Project: Teiid Issue Type: Quality Risk Components: Build/Kits Affects Versions: 13.x Reporter: Van Halbert Assignee: Van Halbert -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-172) Need to implement oauth2 and jwt auth in teiid spring boot

by Renat Eskenin (Jira)

Renat Eskenin created TEIIDSB-172: ------------------------------------- Summary: Need to implement oauth2 and jwt auth in teiid spring boot Key: TEIIDSB-172 URL: https://issues.redhat.com/browse/TEIIDSB-172 Project: Teiid Spring Boot Issue Type: Enhancement Components: datasource Reporter: Renat Eskenin 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)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5891) Need TeiidDialect.getNameQualifierSupport() for Hibernate 5

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5891?focusedWorklogId=12450205&pag... ] Steven Hawkins logged work on TEIID-5891: ----------------------------------------- Author: Steven Hawkins Created on: 17/Feb/20 1:09 PM Start Date: 17/Feb/20 1:09 PM Worklog Time Spent: 30 minutes Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 30 minutes) Time Spent: 30 minutes Worklog Id: (was: 12450205) > Need TeiidDialect.getNameQualifierSupport() for Hibernate 5 > ----------------------------------------------------------- > > Key: TEIID-5891 > URL: https://issues.redhat.com/browse/TEIID-5891 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Driver > Affects Versions: 8.12.18.6_4 > Reporter: Hisanobu Okuda > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.1, 12.3.2, 13.0.3 > > Attachments: reproducerapp.zip > > Original Estimate: 30 minutes > Time Spent: 30 minutes > Remaining Estimate: 0 minutes > > A newer hibernate requires TeiidDialect.getNameQualifierSupport(). -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2020