September 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5813) Using the PG protocol the Virtual View schema items are not visible

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5813?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5813: ------------------------------------- [~shawkins] I was using the latest 12.3.0-SNAPSHOT when I saw this, maybe SNAPSHOT is not updated? > Using the PG protocol the Virtual View schema items are not visible > ------------------------------------------------------------------- > > Key: TEIID-5813 > URL: https://issues.jboss.org/browse/TEIID-5813 > Project: Teiid > Issue Type: Bug > Components: ODBC, Query Engine > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > > When using PSQL client against Teiid deployed VDB, the metadata does not show the tables/views that are defined under a virtual schema. The physical or foreign types are visible correctly. -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-45) Develop OpenShift Operator for deploying VDBs

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-45?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIIDSB-45: ------------------------------------ [~rareddy] When do you think the operator will be pushed to the community repo: [https://github.com/operator-framework/community-operators] > Develop OpenShift Operator for deploying VDBs > --------------------------------------------- > > Key: TEIIDSB-45 > URL: https://issues.jboss.org/browse/TEIIDSB-45 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: OpenShift > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 1.2.0 > > > Need to develop a GO lang based Operator for deploying the VDBs and its configuration. -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5813) Using the PG protocol the Virtual View schema items are not visible

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5813?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5813. ----------------------------------- Resolution: Duplicate Issue Should be a duplicate of TEIID-5805 > Using the PG protocol the Virtual View schema items are not visible > ------------------------------------------------------------------- > > Key: TEIID-5813 > URL: https://issues.jboss.org/browse/TEIID-5813 > Project: Teiid > Issue Type: Bug > Components: ODBC, Query Engine > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > > When using PSQL client against Teiid deployed VDB, the metadata does not show the tables/views that are defined under a virtual schema. The physical or foreign types are visible correctly. -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5813) Using the PG protocol the Virtual View schema items are not visible

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIID-5813: ----------------------------------- Summary: Using the PG protocol the Virtual View schema items are not visible Key: TEIID-5813 URL: https://issues.jboss.org/browse/TEIID-5813 Project: Teiid Issue Type: Bug Components: ODBC, Query Engine Reporter: Ramesh Reddy Assignee: Steven Hawkins When using PSQL client against Teiid deployed VDB, the metadata does not show the tables/views that are defined under a virtual schema. The physical or foreign types are visible correctly. -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5812) Associate Teiid validation errors with their run time objects for discoverability

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIID-5812: ----------------------------------- Summary: Associate Teiid validation errors with their run time objects for discoverability Key: TEIID-5812 URL: https://issues.jboss.org/browse/TEIID-5812 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 12.3 The validation errors that are found during the deployment of VDB are currently associated with the Model/Schema object, where they kind of lose the identity of which schema item they belong to. It would be good to associate with their respective runtime objects so that they can be easily discoverable -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5809) Please add support for deltatoken, not sure if bug or feature request

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5809?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5809: --------------------------------------- > I do not know these tools. But Debizium looks like something different. It's for change data capture. If a source does not expose delta functionality, you need something to capture when and what is changing. > Seems like their database layout generator adds two additional columns to each table, "deleted" and "last modified". They also provide a deltatoken command. Exactely like you mentioned. My hope was that there might be some support in Olingo already that I could reuse. The support in olingo is to just provide the parsed query option - they have no processing logic on their notion of Entity. The Teiid logic would have to look for the delta tokens and see if the Entities included the appropriate modification properties/procedures - which would require either a name/type based convention and/or extension metadata. Note that Salesforce exposes similar information via audit fields on each sObject and a procedure to find what has been deleted, so finding the deleted information will vary by backend. > Are you aware of a javascript based odata frontend which supports offline odata together with Teiid? Not that I'm aware of. > Please add support for deltatoken, not sure if bug or feature request > --------------------------------------------------------------------- > > Key: TEIID-5809 > URL: https://issues.jboss.org/browse/TEIID-5809 > Project: Teiid > Issue Type: Feature Request > Components: OData > Affects Versions: 13.x > Reporter: Christoph John > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.x > > > Hello Steven, > I am currently looking into the use of the deltatoken for offline synchronization. It seems like Teiid simply ignores the command. The following example results in the full collection to be > returned and not just the differences according to the deltatoken date. Is the deltatoken a feature which should currently work? > https://morpheus.fritz.box/odata4/svc/my_nutri_diary/Diary?!deltatoken=20... -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5809) Please add support for deltatoken, not sure if bug or feature request

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5809?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5809: ---------------------------------- Fix Version/s: 13.x > Please add support for deltatoken, not sure if bug or feature request > --------------------------------------------------------------------- > > Key: TEIID-5809 > URL: https://issues.jboss.org/browse/TEIID-5809 > Project: Teiid > Issue Type: Feature Request > Components: OData > Affects Versions: 13.x > Reporter: Christoph John > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.x > > > Hello Steven, > I am currently looking into the use of the deltatoken for offline synchronization. It seems like Teiid simply ignores the command. The following example results in the full collection to be > returned and not just the differences according to the deltatoken date. Is the deltatoken a feature which should currently work? > https://morpheus.fritz.box/odata4/svc/my_nutri_diary/Diary?!deltatoken=20... -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4251) Built in support for Postgres DB as materialization target

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-4251?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4251: ---------------------------------- Fix Version/s: 13.0 (was: 12.3) > Built in support for Postgres DB as materialization target > ---------------------------------------------------------- > > Key: TEIID-4251 > URL: https://issues.jboss.org/browse/TEIID-4251 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > > If Postgres database is available along with install or assumed that it is available, then some of the materialization task can be automated, like > - Creation of a common STATUS table > - Creation of the materilization targets (create views on dbms) > - On load, on undeploy and load scripts for all the materialization views > We need to device a way this to be pluggable, such that based on success of this, we can provide additional support for other sources. -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5780) Support certificate based authentication into Teiid pg

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5780?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5780: ---------------------------------- Fix Version/s: 13.0 (was: 12.3) Pulling out of 12.3. It seems like we may just want to add this as a general feature of transports, rather than honing in on the materialization case. > Support certificate based authentication into Teiid pg > ------------------------------------------------------ > > Key: TEIID-5780 > URL: https://issues.jboss.org/browse/TEIID-5780 > Project: Teiid > Issue Type: Sub-task > Components: ODBC > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > > To support the pg connection into Teiid we will do something like: > - require a pg secure port using the service signing certificate: TEIIDSB-90 TEIIDSB-92 > -- one clarification is that we must document how to make the pg cert dominant if both pg and jdbc secure are used > TODO: > - configure the pg instance to have a service signing certificate and trust the Teiid service signing certificate. If that trust seems too difficult we can just configure the connection to trust all. > - configure the pg connection to Teiid to use the pg service signing certificate as the client certificate > - trust the pg service signing certificate at the teiid service - we need hostname validation to be enabled and the Teiid server to map the service host name to an authenticated user (this could possibly be generalized via keycloak support to more users). -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5810) .vdb can't be modified connection type via change-vdb-connection-type of cli by NPE

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5810?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5810. ----------------------------------- Resolution: Out of Date The fix for this (to VDBMetadataParser) was in TEIID-4629 > .vdb can't be modified connection type via change-vdb-connection-type of cli by NPE > ----------------------------------------------------------------------------------- > > Key: TEIID-5810 > URL: https://issues.jboss.org/browse/TEIID-5810 > Project: Teiid > Issue Type: Bug > Components: VDB > Affects Versions: 8.12.18.6_4 > Environment: jdv 6.4.7 > Reporter: Hiroki Daicho > Assignee: Steven Hawkins > Priority: Major > Attachments: cli.log, proc.vdb, server.log > > > NullPointerException occurred when trying to change connection-type via cli. > It can be occurred with VDB (.vdb) has empty description for data role. > dynamic vdb would not be occur this issue. > {code} > [standalone@localhost:9999 /] /subsystem=teiid:change-vdb-connection-type(vdb-name=proc,vdb-version=1,connection-type=ANY) > { > "outcome" => "failed", > "failure-description" => "JBAS014749: Operation handler failed: java.lang.NullPointerException", > "rolled-back" => true > } > {code} > {code} > ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) JBAS014612: Operation ("change-vdb-connection-type") failed - address: ([("subsystem" => "teiid")]): java.lang.NullPointerException > at com.ctc.wstx.sw.BaseStreamWriter.writeCharacters(BaseStreamWriter.java:451) > at org.teiid.adminapi.impl.VDBMetadataParser.writeElement(VDBMetadataParser.java:654) > at org.teiid.adminapi.impl.VDBMetadataParser.writeDataPolicy(VDBMetadataParser.java:521) > at org.teiid.adminapi.impl.VDBMetadataParser.writeVDB(VDBMetadataParser.java:492) > at org.teiid.adminapi.impl.VDBMetadataParser.marshell(VDBMetadataParser.java:451) > at org.teiid.jboss.VDBService.save(VDBService.java:512) > at org.teiid.jboss.VDBService.access$300(VDBService.java:81) > at org.teiid.jboss.VDBService$2.connectionTypeChanged(VDBService.java:204) > at org.teiid.deployers.RuntimeVDB.changeConnectionType(RuntimeVDB.java:119) > at org.teiid.jboss.ChangeVDBConnectionType.executeOperation(TeiidOperationHandler.java:1261) > at org.teiid.jboss.ChangeVDBConnectionType.executeOperation(TeiidOperationHandler.java:1247) > at org.teiid.jboss.BaseOperationHandler$1.execute(BaseOperationHandler.java:79) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:710) [jboss-as-controller-7.5.18.Final-redhat-1.jar:7.5.18.Final-redhat-1] > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:545) [jboss-as-controller-7.5.18.Final-redhat-1.jar:7.5.18.Final-redhat-1] > at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:338) [jboss-as-controller-7.5.18.Final-redhat-1.jar:7.5.18.Final-redhat-1] > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:314) [jboss-as-controller-7.5.18.Final-redhat-1.jar:7.5.18.Final-redhat-1] > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1152) [jboss-as-controller-7.5.18.Final-redhat-1.jar:7.5.18.Final-redhat-1] > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:335) [jboss-as-controller-7.5.18.Final-redhat-1.jar:7.5.18.Final-redhat-1] > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:204) [jboss-as-controller-7.5.18.Final-redhat-1.jar:7.5.18.Final-redhat-1] > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:209) [jboss-as-controller-7.5.18.Final-redhat-1.jar:7.5.18.Final-redhat-1] > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:136) [jboss-as-controller-7.5.18.Final-redhat-1.jar:7.5.18.Final-redhat-1] > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:158) [jboss-as-controller-7.5.18.Final-redhat-1.jar:7.5.18.Final-redhat-1] > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:154) [jboss-as-controller-7.5.18.Final-redhat-1.jar:7.5.18.Final-redhat-1] > at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.8.0_131] > at javax.security.auth.Subject.doAs(Subject.java:422) [rt.jar:1.8.0_131] > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:94) [jboss-as-controller-7.5.18.Final-redhat-1.jar:7.5.18.Final-redhat-1] > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:154) [jboss-as-controller-7.5.18.Final-redhat-1.jar:7.5.18.Final-redhat-1] > at org.jboss.as.protocol.mgmt.AbstractMessageHandler$ManagementRequestContextImpl$1.doExecute(AbstractMessageHandler.java:364) [jboss-as-protocol-7.5.18.Final-redhat-1.jar:7.5.18.Final-redhat-1] > at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:473) [jboss-as-protocol-7.5.18.Final-redhat-1.jar:7.5.18.Final-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_131] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_131] > at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_131] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.2.Final-redhat-1.jar:2.1.2.Final-redhat-1] > {code} -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2019