February 2020 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIIDSB-152) Alter / drop will not work with vdb plugin

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-152?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIIDSB-152: --------------------------------- Fix Version/s: 1.4.0 > Alter / drop will not work with vdb plugin > ------------------------------------------ > > Key: TEIIDSB-152 > URL: https://issues.redhat.com/browse/TEIIDSB-152 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: core > Reporter: Steven Hawkins > Priority: Major > Fix For: 1.4.0 > > > If you use an alter / drop in the vdb.ddl the result will be an illegalstateexception: > {code} > Caused by: java.lang.IllegalStateException: TransformationMetadata not yet available > at org.teiid.maven.VdbMojoTest.test(VdbMojoTest.java:53) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-142) teiid-openshift-examples enhancements

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-142?page=com.atlassian.jira.plug... ] Ramesh Reddy resolved TEIIDSB-142. ---------------------------------- Resolution: Out of Date Examples changed lately, the examples sometimes show direct values for easy configuration, we can callout using of the secrets at one location as a recommended practice. > teiid-openshift-examples enhancements > ------------------------------------- > > Key: TEIIDSB-142 > URL: https://issues.redhat.com/browse/TEIIDSB-142 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: examples > Reporter: Bilgin Ibryam > Assignee: Bilgin Ibryam > Priority: Optional > > While setting up the example [scenarios|https://github.com/teiid/teiid-openshift-examples/blob/master/r...] the Secret seems unnecessary? Is it really used? > # CREATE SECRET TO CONNECT TO DATABASE (ADJUST TO YOUR VALUES) > oc create -f - <<EOF > apiVersion: v1 > kind: Secret > metadata: > name: postgresql > type: Opaque > stringData: > database-user: user > database-name: sampledb > database-password: mypassword > EOF > Also the following steps can be shortened: > oc get pods > oc rsh postgres-xxxxx > to > oc rsh $(oc get pods -o name -l app=postgresql) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-23) Document image generation options

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-23?page=com.atlassian.jira.plugi... ] Ramesh Reddy commented on TEIIDSB-23: ------------------------------------- [~shawkins] I would like to resolve this, as I can not think of any further work under this. We can open anything. Seems like this out of date to me. > Document image generation options > --------------------------------- > > Key: TEIIDSB-23 > URL: https://issues.redhat.com/browse/TEIIDSB-23 > Project: Teiid Spring Boot > Issue Type: Task > Reporter: Steven Hawkins > Priority: Major > Fix For: 1.4.0 > > > We need to document / validate all relevant image options: > - inclusion of agent bond or other mechanism for jmx exposure to prometheus. There may also be related service annotations > - annotations for 3scale for rest and openapi exposure of odata > - any common config options - disk buffer memory, max active plans / engine threads / connection pool sizes. Ideally the buffer manager heap should auto-configure and we should probably always use off-heap for the fixed memory buffer. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-23) Document image generation options

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-23?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIIDSB-23: -------------------------------- Fix Version/s: 1.4.0 > Document image generation options > --------------------------------- > > Key: TEIIDSB-23 > URL: https://issues.redhat.com/browse/TEIIDSB-23 > Project: Teiid Spring Boot > Issue Type: Task > Reporter: Steven Hawkins > Priority: Major > Fix For: 1.4.0 > > > We need to document / validate all relevant image options: > - inclusion of agent bond or other mechanism for jmx exposure to prometheus. There may also be related service annotations > - annotations for 3scale for rest and openapi exposure of odata > - any common config options - disk buffer memory, max active plans / engine threads / connection pool sizes. Ideally the buffer manager heap should auto-configure and we should probably always use off-heap for the fixed memory buffer. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 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.4.0 (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.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, 10 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: Steven Hawkins (was: 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: Steven Hawkins > Priority: Major > Fix For: 13.1 > > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > 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, 10 months

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 commented on TEIID-5908: --------------------------------------- > For some reason we are receiving following error when running a query on the table with this field in VDB. That would appear to be a driver issue. This is similar to https://issues.apache.org/jira/browse/KAFKA-5067 - which shows a very simple jdbc query that results in the same exception. The pg driver does handle the case of using getTimestamp with TIMESTAMP WITH TIMEZONE, but the redshift driver must not. You can change the source type to string to confirm that you are getting the correct values back. If so, we could pursue the fix of using getString if getTimestamp fails and attempt to parse the value ourselves. > 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 > > 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, 10 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: --------------------------------------- I see we did add a warning in the docs: http://teiid.github.io/teiid-documents/master/content/reference/ddl_deplo... To speed up this issue, I'll separate off the non-conformance issue and expand upon the warning. We can also consider having the grants/revoke only run at the end of the ddl such that they won't be affected by the drop issue. In any case here is the wip: https://github.com/teiid/teiid/compare/master...shawkins:TEIID-5798?expand=1 This is a light reorganization to better capture some of the concepts and to remove the linear scan we were doing for grants - which would get cost prohibitive for a lot of grants. The policy functionality is just beginning to be stubbed out. I will try to by-pass using the policymetadata construct and rather directly reference our regular metadata specifically for policies. I'll also need bridge the old condition login into the new. > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5910) XML value for the constraint attribute on a condition is incorrect

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5910: ------------------------------------- Summary: XML value for the constraint attribute on a condition is incorrect Key: TEIID-5910 URL: https://issues.redhat.com/browse/TEIID-5910 Project: Teiid Issue Type: Bug Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 13.1, 13.0.3 The VDBMetadataParser is writing out the value of the condition, not the constraint flag. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 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?focusedWorklogId=12450302&pag... ] Ramesh Reddy logged work on TEIID-5909: --------------------------------------- Author: Ramesh Reddy Created on: 21/Feb/20 3:58 PM Start Date: 21/Feb/20 3:58 PM Worklog Time Spent: 2 hours Issue Time Tracking ------------------- Remaining Estimate: 0 minutes Time Spent: 2 hours Worklog Id: (was: 12450302) > 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 > > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > 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, 10 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