December 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5867) Support capturing the IMPORT FORIGN DATA in DDLStringVisitor

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIID-5867: ----------------------------------- Summary: Support capturing the IMPORT FORIGN DATA in DDLStringVisitor Key: TEIID-5867 URL: https://issues.redhat.com/browse/TEIID-5867 Project: Teiid Issue Type: Enhancement Components: Query Engine Affects Versions: 13.0 Reporter: Ramesh Reddy Assignee: Steven Hawkins In DatabaseStore logic the IMPORT FOREIGN DATA WRAPPER is treated as runtime statements that engine is processing at runtime vs build time representation of the VDB. It is a perfectly valid scenario. However, when working with VDB building, VDB-Import scenarios we need to capture these as is. can we provide a model in DatabaseStore to capture these in certain situations? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-151) Update to Teiid 13

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-151?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIIDSB-151: ----------------------------------- Original Estimate: 1 hour Remaining Estimate: 1 hour > Update to Teiid 13 > ------------------ > > Key: TEIIDSB-151 > URL: https://issues.redhat.com/browse/TEIIDSB-151 > Project: Teiid Spring Boot > Issue Type: Task > Components: core > Reporter: Steven Hawkins > Priority: Major > Fix For: 1.3.0 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Update to Teiid 13 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-151) Update to Teiid 13

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-151?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIIDSB-151: ---------------------------------------- [~rareddy] Do you want to import the teiid pom to simplify some of the Teiid spring boot dependency management? > Update to Teiid 13 > ------------------ > > Key: TEIIDSB-151 > URL: https://issues.redhat.com/browse/TEIIDSB-151 > Project: Teiid Spring Boot > Issue Type: Task > Components: core > Reporter: Steven Hawkins > Priority: Major > Fix For: 1.3.0 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Update to Teiid 13 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-151) Update to Teiid 13

by Steven Hawkins (Jira)

Steven Hawkins created TEIIDSB-151: -------------------------------------- Summary: Update to Teiid 13 Key: TEIIDSB-151 URL: https://issues.redhat.com/browse/TEIIDSB-151 Project: Teiid Spring Boot Issue Type: Task Components: core Reporter: Steven Hawkins Fix For: 1.3.0 Update to Teiid 13 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

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

6 years

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-145) Move the Spring Boot version 2.1.6.RELEASE to match for Syndesis

by Van Halbert (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-145?page=com.atlassian.jira.plug... ] Van Halbert updated TEIIDSB-145: -------------------------------- Story Points: 3 > Move the Spring Boot version 2.1.6.RELEASE to match for Syndesis > ---------------------------------------------------------------- > > Key: TEIIDSB-145 > URL: https://issues.redhat.com/browse/TEIIDSB-145 > Project: Teiid Spring Boot > Issue Type: Task > Components: core > Reporter: Ramesh Reddy > Assignee: Van Halbert > Priority: Major > Fix For: 1.3.0 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > To match the version with Syndesis, move the Spring Boot to 2.1.6.RELEASE -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

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

6 years

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-52) Organize docs as much as possible into topics

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-52?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIIDSB-52: ---------------------------------- Fix Version/s: 1.3.1 1.3.1 (was: 1.3.0) > Organize docs as much as possible into topics > --------------------------------------------- > > Key: TEIIDSB-52 > URL: https://issues.redhat.com/browse/TEIIDSB-52 > Project: Teiid Spring Boot > Issue Type: Sub-task > Components: documentation > Reporter: Steven Hawkins > Priority: Major > Fix For: 1.3.1 > > > To align with product documentation the docs need to be as topic (a particular dev/admin action) based as possible - rather than general subject areas. We also need to update anything listing steps to use a numbered list with as granular as possible steps. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

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

6 years

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-42) Add a grafana dashboard example

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-42?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIIDSB-42: ---------------------------------- Fix Version/s: 1.3.1 1.3.1 (was: 1.3.0) > Add a grafana dashboard example > ------------------------------- > > Key: TEIIDSB-42 > URL: https://issues.redhat.com/browse/TEIIDSB-42 > Project: Teiid Spring Boot > Issue Type: Sub-task > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.3.1 > > > Building off of the prometheus metrics collection, we should provide a grafana dashboard. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2019