November 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5285) Add high-level feature for redirection of updates

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5285?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-5285. --------------------------------- Resolution: Done Initial redirection feature is available now with the spring-boot library, anything additional we will work as a separate issue. > Add high-level feature for redirection of updates > ------------------------------------------------- > > Key: TEIID-5285 > URL: https://issues.jboss.org/browse/TEIID-5285 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Teiid Spring Boot > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 12.x > > Attachments: redirection-vdb.xml > > > In microservices testing it is desirable to test against production/live data but not commit any updates. We should offer a simple solution that can defined by extension metadata and enabled/disabled by a feature flag. We may need to make simplifying assumptions about the scope (per session, per application, etc.) and durability of the updates. > Under the covers this will be achieved by using views, update triggers, and a store for the updates and when not enabled the expectation is that all operations should pass through. However the application will be limited to using Teiid SQL and will be required to use the Teiid or pg driver, or Teiid spring boot. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2869) Support consuming REST based service that is secured by SAML

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-2869?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2869. --------------------------------- Resolution: Out of Date > Support consuming REST based service that is secured by SAML > ------------------------------------------------------------ > > Key: TEIID-2869 > URL: https://issues.jboss.org/browse/TEIID-2869 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 12.x > > > Add SSO based support for consuming the REST based web-services. Currently only HTTP-Basic is supported. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5521) Add build plugins used by basepom to help with dependency handling

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5521?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5521: --------------------------------------- Is the proposal here to change from jboss-parent to basebom? > Add build plugins used by basepom to help with dependency handling > ------------------------------------------------------------------ > > Key: TEIID-5521 > URL: https://issues.jboss.org/browse/TEIID-5521 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Affects Versions: 12.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > Fix For: 12.0 > > > Utilize plugins that basebom uses, which will help reduce half the headaches you go though during the productization with versions. > plugins: > * duplicate-finder-maven-plugin > * maven-dependency-plugin > * maven-dependency-versions-check-plugin -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5526) Missing data source thorntail

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5526?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5526: --------------------------------------- > If you define a vdb and there is a source for which a jndi name is not matched with a data source from the configuration, the vdb will still be deployed, but won't be active To clarify, this is only for the case where the source metadata is not provided and cannot be obtained without a connection. If the jndi name does not match and we have metadata the vdb will deploy and be active. > and there is no indication in the default console log as to the progress or lack thereof with the metadata load. There is always the log about metadata load starting. And testing this some more I do see appropriate failure logs. > Given the presumed static nature of thorntail deployments, this scenario should result in a failed deployment like embedded. It seems like this would either need to be a build time validation or something that can be detected via running/health check. Our initial versions of those would only detect this when the metadata is not available. Given that I'm seeing appropriate error messages, I'll not worry about this yet. > Missing data source thorntail > ----------------------------- > > Key: TEIID-5526 > URL: https://issues.jboss.org/browse/TEIID-5526 > Project: Teiid > Issue Type: Quality Risk > Components: thorntail > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.x > > > If you define a vdb and there is a source for which a jndi name is not matched with a data source from the configuration, the vdb will still be deployed, but won't be active - and there is no indication in the default console log as to the progress or lack thereof with the metadata load. > Given the presumed static nature of thorntail deployments, this scenario should result in a failed deployment like embedded. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5526) Missing data source thorntail

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5526?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5526: ---------------------------------- Fix Version/s: 12.x (was: 11.2.1) > Missing data source thorntail > ----------------------------- > > Key: TEIID-5526 > URL: https://issues.jboss.org/browse/TEIID-5526 > Project: Teiid > Issue Type: Quality Risk > Components: thorntail > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.x > > > If you define a vdb and there is a source for which a jndi name is not matched with a data source from the configuration, the vdb will still be deployed, but won't be active - and there is no indication in the default console log as to the progress or lack thereof with the metadata load. > Given the presumed static nature of thorntail deployments, this scenario should result in a failed deployment like embedded. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5526) Missing data source thorntail

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5526?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5526: ---------------------------------- Priority: Minor (was: Major) > Missing data source thorntail > ----------------------------- > > Key: TEIID-5526 > URL: https://issues.jboss.org/browse/TEIID-5526 > Project: Teiid > Issue Type: Quality Risk > Components: thorntail > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 12.x > > > If you define a vdb and there is a source for which a jndi name is not matched with a data source from the configuration, the vdb will still be deployed, but won't be active - and there is no indication in the default console log as to the progress or lack thereof with the metadata load. > Given the presumed static nature of thorntail deployments, this scenario should result in a failed deployment like embedded. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5526) Missing data source thorntail

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5526?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-5526: ------------------------------------- Assignee: (was: Steven Hawkins) > Missing data source thorntail > ----------------------------- > > Key: TEIID-5526 > URL: https://issues.jboss.org/browse/TEIID-5526 > Project: Teiid > Issue Type: Quality Risk > Components: thorntail > Reporter: Steven Hawkins > Priority: Minor > Fix For: 12.x > > > If you define a vdb and there is a source for which a jndi name is not matched with a data source from the configuration, the vdb will still be deployed, but won't be active - and there is no indication in the default console log as to the progress or lack thereof with the metadata load. > Given the presumed static nature of thorntail deployments, this scenario should result in a failed deployment like embedded. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5554) Inappropriate sizing of the fixed memory buffer when only the max reserve is set

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5554?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5554. ----------------------------------- Fix Version/s: 11.2.1 Resolution: Done Updated the logic to consider using 1/4 of the remaining max memory when the max reserve is set. > Inappropriate sizing of the fixed memory buffer when only the max reserve is set > -------------------------------------------------------------------------------- > > Key: TEIID-5554 > URL: https://issues.jboss.org/browse/TEIID-5554 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.0, 11.2.1 > > > If the max reserve kb is set to a large value, the default for the fixed memory buffer will be 40% of that - which in total may be too large for the vm. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5410) Incorrect result from timestampadd with 1 billion or more fractional seconds

by Johnathon Lee (Jira)

[ https://issues.jboss.org/browse/TEIID-5410?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-5410: --------------------------------- Fix Version/s: 8.12.17.6_4 > Incorrect result from timestampadd with 1 billion or more fractional seconds > ---------------------------------------------------------------------------- > > Key: TEIID-5410 > URL: https://issues.jboss.org/browse/TEIID-5410 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 11.1, 11.0.1, 10.3.3, 8.12.17.6_4 > > > A query such as: > Select TimestampAdd(SQL_TSI_FRAC_SECOND, 999999999 + 1, Cast(CurDate() as timestamp)); > Returns a result with the incorrect amount of factional seconds. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5554) Inappropriate sizing of the fixed memory buffer when only the max reserve is set

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5554: ------------------------------------- Summary: Inappropriate sizing of the fixed memory buffer when only the max reserve is set Key: TEIID-5554 URL: https://issues.jboss.org/browse/TEIID-5554 Project: Teiid Issue Type: Bug Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 12.0 If the max reserve kb is set to a large value, the default for the fixed memory buffer will be 40% of that - which in total may be too large for the vm. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2018