[JBoss JIRA] (TEIIDSB-34) Support Keycloak based OAuth authentication for OData
by Ramesh Reddy (Jira)
Ramesh Reddy created TEIIDSB-34:
-----------------------------------
Summary: Support Keycloak based OAuth authentication for OData
Key: TEIIDSB-34
URL: https://issues.jboss.org/browse/TEIIDSB-34
Project: Teiid Spring Boot
Issue Type: Feature Request
Components: OData
Reporter: Ramesh Reddy
Provide Keycloak based oAuth2 authentication on top of OData API. This needs to be an optional feature either exposed through a flag or starter project in the pom.xml file.
The scope in the OAuth needs to be used as the roles in the Teiid (this is how legacy Teiid mapped)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (TEIID-5564) Batch removed during large temp table load
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5564?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-5564:
----------------------------------
Fix Version/s: 8.12.17.6_4
> Batch removed during large temp table load
> ------------------------------------------
>
> Key: TEIID-5564
> URL: https://issues.jboss.org/browse/TEIID-5564
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 11.1.2, 12.0, 8.12.17.6_4, 11.2.2
>
>
> For a sufficiently large temp operation, such as a merge over 2.5 million rows, you can see:
> java.lang.AssertionError: Batch not found in storage 58804
> at org.teiid.common.buffer.impl.BufferManagerImpl$BatchManagerImpl.getBatch(BufferManagerImpl.java:382) [teiid-engine-8.12.16.6_4-redhat-64-2.jar:8.12.16.6_4-redhat-64-2]
> at org.teiid.common.buffer.SPage.getValues(SPage.java:240) [teiid-engine-8.12.16.6_4-redhat-64-2.jar:8.12.16.6_4-redhat-64-2]
> at org.teiid.common.buffer.SPage.search(SPage.java:139) [teiid-engine-8.12.16.6_4-redhat-64-2.jar:8.12.16.6_4-redhat-64-2]
> at org.teiid.common.buffer.STree.find(STree.java:249) [teiid-engine-8.12.16.6_4-redhat-64-2.jar:8.12.16.6_4-redhat-64-2]
> at org.teiid.common.buffer.STree.remove(STree.java:429) [teiid-engine-8.12.16.6_4-redhat-64-2.jar:8.12.16.6_4-redhat-64-2]
> at org.teiid.query.tempdata.TempTable.deleteTuple(TempTable.java:802) [teiid-engine-8.12.16.6_4-redhat-64-2.jar:8.12.16.6_4-redhat-64-2]
> at org.teiid.query.tempdata.TempTable.access$500(TempTable.java:83) [teiid-engine-8.12.16.6_4-redhat-64-2.jar:8.12.16.6_4-redhat-64-2]
> at org.teiid.query.tempdata.TempTable$InsertUpdateProcessor.undo(TempTable.java:159) [teiid-engine-8.12.16.6_4-redhat-64-2.jar:8.12.16.6_4-redhat-64-2]
> Which occurs during undo/rollback of an operation and masks the underlying exception. The actual error will typically be the same as TEIID-5439, the proactive removal of the managed batches once a space limit has been reached.
> This did not occur after the TEIID-5439 fix upstream, but it appears it could have still occurred - and did occur on 8.12.x.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (TEIIDSB-19) Create Portfolio Example
by Ramesh Reddy (Jira)
[ https://issues.jboss.org/browse/TEIIDSB-19?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIIDSB-19.
---------------------------------
Fix Version/s: 1.0.3
Resolution: Done
Documentation will be updated as we go along, but for now example is in a workable status.
> Create Portfolio Example
> ------------------------
>
> Key: TEIIDSB-19
> URL: https://issues.jboss.org/browse/TEIIDSB-19
> Project: Teiid Spring Boot
> Issue Type: Task
> Components: OpenShift
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Priority: Major
> Fix For: 1.0.3
>
>
> - Portfolio example project that includes a representative sample of all resources a user might interact with (application.properties, VDB DDL, data source definitions, beans, etc.)
> - Portfolio example project delivered via GitHub
> - README documentation instructing a user on how to build and deploy Portfolio example
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (TEIIDSB-19) Create Portfolio Example
by Ramesh Reddy (Jira)
[ https://issues.jboss.org/browse/TEIIDSB-19?page=com.atlassian.jira.plugin... ]
Ramesh Reddy updated TEIIDSB-19:
--------------------------------
Component/s: OpenShift
> Create Portfolio Example
> ------------------------
>
> Key: TEIIDSB-19
> URL: https://issues.jboss.org/browse/TEIIDSB-19
> Project: Teiid Spring Boot
> Issue Type: Task
> Components: OpenShift
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Priority: Major
>
> - Portfolio example project that includes a representative sample of all resources a user might interact with (application.properties, VDB DDL, data source definitions, beans, etc.)
> - Portfolio example project delivered via GitHub
> - README documentation instructing a user on how to build and deploy Portfolio example
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (TEIIDSB-23) Document image generation options
by Ramesh Reddy (Jira)
[ https://issues.jboss.org/browse/TEIIDSB-23?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIIDSB-23:
-------------------------------------
[~shawkins] I have added [1] the template for Prometheus, which I extracted from Syndesis as suggested above and added to new examples project at [2]. I also added how to create the instance, but beyond that, I am not sure what needs to be done. I have not modified the "relabel" section either in the template from that of Syndesis. Take look and modify and add whatever you need to complete the example with instructions, so that we can showcase this example as a demo.
[1] https://github.com/teiid/teiid-openshift-examples/pull/5
[2] https://github.com/teiid/teiid-openshift-examples/tree/master/prometheus
> Document image generation options
> ---------------------------------
>
> Key: TEIIDSB-23
> URL: https://issues.jboss.org/browse/TEIIDSB-23
> Project: Teiid Spring Boot
> Issue Type: Task
> Reporter: Steven Hawkins
> Priority: Major
> Fix For: Q119
>
>
> 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.12.1#712002)
7 years, 1 month
[JBoss JIRA] (TEIID-5658) PG transport can send multiple read messages
by Steven Hawkins (Jira)
Steven Hawkins created TEIID-5658:
-------------------------------------
Summary: PG transport can send multiple read messages
Key: TEIID-5658
URL: https://issues.jboss.org/browse/TEIID-5658
Project: Teiid
Issue Type: Bug
Components: ODBC
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 12.1, 12.0.1, 11.2.3
The code is allowing for a sequence of events such as:
2019-02-13 12:26:55.159 org.teiid.ODBC TRACE NIO1 invoking server method: execute [, 0]
2019-02-13 12:26:55.163 org.teiid.ODBC TRACE NIO1 invoking client method: sendResults [null, org.teiid.jdbc.ResultSetImpl@1a79693d, [org.teiid.odbc.PGUtil$PgColInfo@79f0f194], org.teiid.client.util.ResultsFuture@64fb47b7, FORWARD, -1, false, null]
2019-02-13 12:26:55.163 org.teiid.ODBC TRACE Worker5_QueryProcessorQueue533 invoking client method: sendCommandComplete [select oid from pg_class where relname='pg_class', [1]]
2019-02-13 12:26:55.163 org.teiid.ODBC TRACE Worker5_QueryProcessorQueue533 invoking client method: ready [false, false]
2019-02-13 12:26:55.163 org.teiid.ODBC TRACE NIO1 invoking server method: sync null
2019-02-13 12:26:55.163 org.teiid.ODBC TRACE NIO1 invoking client method: ready [false, false]
That is after execute we are immediately responding with results, command complete, and ready. Then we see a sync and respond with ready again.
The first ready is not expected - it should not be issued until after the sync.
The causes issues in the pg jdbc driver such as reporting that there is no result set. See TEIID-5425
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (TEIID-5657) VDB Migration Tool
by Van Halbert (Jira)
[ https://issues.jboss.org/browse/TEIID-5657?page=com.atlassian.jira.plugin... ]
Van Halbert updated TEIID-5657:
-------------------------------
Component/s: Documentation
Quick Starts
> VDB Migration Tool
> ------------------
>
> Key: TEIID-5657
> URL: https://issues.jboss.org/browse/TEIID-5657
> Project: Teiid
> Issue Type: Feature Request
> Components: Documentation, Quick Starts, Tooling
> Affects Versions: 12.x
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Major
>
> A migration tool will be provided to convert customer vdbs into just ddl. More than likely this will be just a single ddl file - which will probably not be acceptable to customers with large vdbs.
> We have this utility already available as just a main method in one of our jars. It is anticipated that a maven repo will be distribution mechanism and minimal documentation will be provided.
> There should be optional validation available for the vdb ddl at build time. This breaks down into 3 parts:
> 1. static syntactic validation, potentially even fully resolving if all metadata is present. This makes sure that basic typos will be caught.
> 2. providing hard errors for things that are completely removed - an error for usage of soap or function models for example.
> 3. providing errors or warning for features that are not yet available - vdb imports, sources that aren't yet supported etc.
> To avoid introducing a new plugin or plugging into fmp it's been suggested that the validation could be run via a generated unit test, which ties into another task which is booster, base project, or last resort an arche type that scaffolds the developer project.
> This could possibly be included in the quickstarts as a means to facilitate its use.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (TEIID-5657) VDB Migration Tool
by Van Halbert (Jira)
[ https://issues.jboss.org/browse/TEIID-5657?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-5657:
------------------------------------
It was discussed in todays DAS sprint meeting, that this migration tool could be an example added to the teiid-openshift-examples. That the execution using maven and passing in the VDB argument for the file to be processed.
> VDB Migration Tool
> ------------------
>
> Key: TEIID-5657
> URL: https://issues.jboss.org/browse/TEIID-5657
> Project: Teiid
> Issue Type: Feature Request
> Components: Documentation, Quick Starts, Tooling
> Affects Versions: 12.x
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Major
>
> A migration tool will be provided to convert customer vdbs into just ddl. More than likely this will be just a single ddl file - which will probably not be acceptable to customers with large vdbs.
> We have this utility already available as just a main method in one of our jars. It is anticipated that a maven repo will be distribution mechanism and minimal documentation will be provided.
> There should be optional validation available for the vdb ddl at build time. This breaks down into 3 parts:
> 1. static syntactic validation, potentially even fully resolving if all metadata is present. This makes sure that basic typos will be caught.
> 2. providing hard errors for things that are completely removed - an error for usage of soap or function models for example.
> 3. providing errors or warning for features that are not yet available - vdb imports, sources that aren't yet supported etc.
> To avoid introducing a new plugin or plugging into fmp it's been suggested that the validation could be run via a generated unit test, which ties into another task which is booster, base project, or last resort an arche type that scaffolds the developer project.
> This could possibly be included in the quickstarts as a means to facilitate its use.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (TEIIDSB-19) Create Portfolio Example
by Van Halbert (Jira)
[ https://issues.jboss.org/browse/TEIIDSB-19?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIIDSB-19:
------------------------------------
At this point, we have the example and the related sub-task completed. I would suggest this could be closed and any future changes (i.e, adding migration tool) will have a new jira created.
> Create Portfolio Example
> ------------------------
>
> Key: TEIIDSB-19
> URL: https://issues.jboss.org/browse/TEIIDSB-19
> Project: Teiid Spring Boot
> Issue Type: Task
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Priority: Major
>
> - Portfolio example project that includes a representative sample of all resources a user might interact with (application.properties, VDB DDL, data source definitions, beans, etc.)
> - Portfolio example project delivered via GitHub
> - README documentation instructing a user on how to build and deploy Portfolio example
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month