[JBoss JIRA] (TEIIDSB-150) Micrometer spike
by Ramesh Reddy (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-150?page=com.atlassian.jira.plug... ]
Ramesh Reddy moved TEIIDTOOLS-847 to TEIIDSB-150:
-------------------------------------------------
Project: Teiid Spring Boot (was: Teiid Tools)
Key: TEIIDSB-150 (was: TEIIDTOOLS-847)
Component/s: core
(was: teiid-syndesis)
> Micrometer spike
> ----------------
>
> Key: TEIIDSB-150
> URL: https://issues.redhat.com/browse/TEIIDSB-150
> Project: Teiid Spring Boot
> Issue Type: Feature Request
> Components: core
> Reporter: Steven Hawkins
> Priority: Major
>
> This work will wind up in Teiid spring boot (and even teiid), but the driver is from this project. We need to examine the level of effort of converting to micrometer rather than just jmx metrics for better spring integration.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (TEIIDSB-144) Calling setTransactionIsolation on pg driver causes the connection to be closed
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-144?page=com.atlassian.jira.plug... ]
Steven Hawkins updated TEIIDSB-144:
-----------------------------------
Fix Version/s: 1.3.1
1.3.1
(was: 1.3.0)
> Calling setTransactionIsolation on pg driver causes the connection to be closed
> -------------------------------------------------------------------------------
>
> Key: TEIIDSB-144
> URL: https://issues.redhat.com/browse/TEIIDSB-144
> Project: Teiid Spring Boot
> Issue Type: Bug
> Components: datasource
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 1.3.1
>
>
> An attempt to set the isolation level on pg 42.2.8 resulted in an exception SQLSTATE 0a000 - unsupported - which causes the connection pool to mark the connection as broken:
> {code}
> 2019-11-25 23:07:50.125 WARN 43993 --- [ProcessorQueue6] com.zaxxer.hikari.pool.ProxyConnection : HikariPool-1 - Connection org.postgresql.jdbc.PgConnection@2ffebc7e marked as broken because of SQLSTATE(0A000), ErrorCode(0)
> org.postgresql.util.PSQLException:
> at org.postgresql.jdbc.PgConnection.setTransactionIsolation(PgConnection.java:851) ~[postgresql-42.2.8.jar:42.2.8]
> at com.zaxxer.hikari.pool.ProxyConnection.setTransactionIsolation(ProxyConnection.java:407) ~[HikariCP-3.2.0.jar:na]
> at com.zaxxer.hikari.pool.HikariProxyConnection.setTransactionIsolation(HikariProxyConnection.java) ~[HikariCP-3.2.0.jar:na]
> at org.teiid.translator.jdbc.JDBCBaseExecution.<init>(JDBCBaseExecution.java:72) ~[translator-jdbc-12.3.0.jar:12.3.0]
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (TEIIDSB-27) Created targeted documentation
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-27?page=com.atlassian.jira.plugi... ]
Steven Hawkins updated TEIIDSB-27:
----------------------------------
Fix Version/s: 1.3.1
1.3.1
(was: 1.3.0)
> Created targeted documentation
> ------------------------------
>
> Key: TEIIDSB-27
> URL: https://issues.redhat.com/browse/TEIIDSB-27
> Project: Teiid Spring Boot
> Issue Type: Task
> Components: documentation
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 1.3.1
>
>
> It's expected that all developer oriented aspects will be self documented with javadoc and examples (udfs, pom options, configuration, custom extensions, etc.). However the Teiid ddl, sql - and in particular the presentation of topics that were presented separately such as data roles - need to be covered by documentation that does not reference topics such as Designer, wildfly/cli, xml vdbs, etc. We should probably also discuss if it makes any sense to still offer the local adminapi.
> We expect to receive some input from the documentation group around doc structure and strategies for generating specific documentation sets off of a master. At a high level we have:
> Administrator’s Guide - WildFly specific and should mostly be replaced by examples
> Caching Guide - References adminapi, Teiid JDBC, xml vdbs..
> Client Developer’s Guide - Teiid JDBC
> Developer’s Guide - References WildFly and several arche-types are specific to WildFly/JEE - should mostly be replaced by examples
> Embedded Guide - Should mostly be replaced by examples
> Reference Guide - References XML vdbs
> Security Guide - WildFly specific and should mostly be replaced by examples, but a lot is TDB
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (TEIIDSB-51) Define expectations for runtime metadata
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-51?page=com.atlassian.jira.plugi... ]
Steven Hawkins updated TEIIDSB-51:
----------------------------------
Fix Version/s: 1.3.1
(was: 1.3.0)
> Define expectations for runtime metadata
> ----------------------------------------
>
> Key: TEIIDSB-51
> URL: https://issues.redhat.com/browse/TEIIDSB-51
> Project: Teiid Spring Boot
> Issue Type: Feature Request
> Components: documentation
> Reporter: Steven Hawkins
> Priority: Major
> Fix For: 1.3.1
>
>
> At a high level there are potentially three modes for our ddl:
> 1. Interactive - there was some work toward this, but it needed to only be a "developer mode" as it would reload the vdb on each metadata change. There is a lot about the transactionality of DDL updates that our current simplistic metadata model does not support, which makes this hard to fully implement. We haven't talked about this much in relation to Teiid Spring Boot, but ideally there should be a way for developers to test incremental changes without full rebuilds.
> 2. Dynamic - the term is a bit dated, but this refers to any vdb that performs import from a metadata repository that has runtime dependencies. By design this allows for a simple vdb definition and options for caching or re-importing on reload. In a container environment metadata caching no longer makes sense unless we use a volume. Depending upon your viewpoint allowing for runtime import of metadata is potentially a point of mutability that is also not needed in a container environment.
> 3. Static - much like our old .index designer vdbs there are benefits to having the full metadata already available to the vdb/image. There is a lot of work that we do lazily at runtime that can be moved to an earlier phase - primarily generating the rest and odata layers, but it would also include the pg system table materializations. For Teiid Spring Boot or usage in containers in general what this would look like is a build phase for the vdb such that it could obtain appropriate metadata and initialize as much as possible statically (eventually for quarkus vm snapshotting). The only metadata that would not be fresh potentially would be the costing metadata - however that is problematic as is and will eventually need a progressive optimization strategy employing a persistent store.
> As of now we are currently focused just on #2. As we look toward operators, we should start thinking about #3.
> #1 would come into play if/when we start looking at local development options using vs code.
> We can treat this issue as an epic and a place to centralize discussion.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years