June 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5762) Modernize the teiid configuration

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5762?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5762: --------------------------------------- At first glance there were only superficial changes here to the config versions (checked in under the parent issue). Will take a look at if there are any changes to be made for Elytron. > Modernize the teiid configuration > --------------------------------- > > Key: TEIID-5762 > URL: https://issues.jboss.org/browse/TEIID-5762 > Project: Teiid > Issue Type: Sub-task > Components: Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.3 > > > The Teiid configuration is based upon an out-dated version of the wildfly config. It should be brought up-to-date. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-102) Update legacy terminology

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-102?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIIDSB-102. ------------------------------------ Resolution: Done Updated teiid, the docs, examples, and teiid-spring-boot to no longer use the jaas nor jndi terms. > Update legacy terminology > ------------------------- > > Key: TEIIDSB-102 > URL: https://issues.jboss.org/browse/TEIIDSB-102 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.2.0 > > > There are several places where we are using old terminology: > * updating model count - should not use the term model, and would be better phrased in terms of the transactional requirement. > * jndi-name - could be bean-name to be more spring specific. Could be source-name, but that's an overloaded term. connection-source? > * jaas role > Others should be captured here as well. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-103) Support vdb and/or classpath resources

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-103?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on TEIIDSB-103: ---------------------------------------- > do you mean looking for "teiid.vdb" file also by default? You mean rather than having the explicit property? Yes I'm good with that. > Support vdb and/or classpath resources > -------------------------------------- > > Key: TEIIDSB-103 > URL: https://issues.jboss.org/browse/TEIIDSB-103 > Project: Teiid Spring Boot > Issue Type: Feature Request > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.2.0 > > > The loading logic for a .vdb artifact does not create the associated vdb resources, so things like the ddl-file metadata repo cannot be used. We should probably support that, and in general may consider supporting a classpath based resource mechanism now that we have unified classloader. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-103) Support vdb and/or classpath resources

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-103?page=com.atlassian.jira.plugi... ] Ramesh Reddy commented on TEIIDSB-103: -------------------------------------- The DDL version either you can define or looks for "teiid-vdb.ddl" by default, do you mean looking for "teiid.vdb" file also by default? > Support vdb and/or classpath resources > -------------------------------------- > > Key: TEIIDSB-103 > URL: https://issues.jboss.org/browse/TEIIDSB-103 > Project: Teiid Spring Boot > Issue Type: Feature Request > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.2.0 > > > The loading logic for a .vdb artifact does not create the associated vdb resources, so things like the ddl-file metadata repo cannot be used. We should probably support that, and in general may consider supporting a classpath based resource mechanism now that we have unified classloader. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-103) Support vdb and/or classpath resources

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-103?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on TEIIDSB-103: ---------------------------------------- [~rareddy] do you want a classloader based vdb resource option as well? > Support vdb and/or classpath resources > -------------------------------------- > > Key: TEIIDSB-103 > URL: https://issues.jboss.org/browse/TEIIDSB-103 > Project: Teiid Spring Boot > Issue Type: Feature Request > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.2.0 > > > The loading logic for a .vdb artifact does not create the associated vdb resources, so things like the ddl-file metadata repo cannot be used. We should probably support that, and in general may consider supporting a classpath based resource mechanism now that we have unified classloader. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-103) Support vdb and/or classpath resources

by Steven Hawkins (Jira)

Steven Hawkins created TEIIDSB-103: -------------------------------------- Summary: Support vdb and/or classpath resources Key: TEIIDSB-103 URL: https://issues.jboss.org/browse/TEIIDSB-103 Project: Teiid Spring Boot Issue Type: Feature Request Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 1.2.0 The loading logic for a .vdb artifact does not create the associated vdb resources, so things like the ddl-file metadata repo cannot be used. We should probably support that, and in general may consider supporting a classpath based resource mechanism now that we have unified classloader. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5745) Reduce memory overhead of ddl vdbs

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5745?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5745: ---------------------------------- Priority: Minor (was: Major) Lowering the priority as this also could be eventually addressed on the teiid spring boot / operator side by making the initial ddl processing a build time activity and create an image that is more efficient. > Reduce memory overhead of ddl vdbs > ---------------------------------- > > Key: TEIID-5745 > URL: https://issues.jboss.org/browse/TEIID-5745 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 12.3 > > > Due to mapping to the existing vdb metadata structure we are holding a memory reference to the full ddl. At a minimum that could be replaced with a file reference. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5762) Modernize the teiid configuration

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5762: ------------------------------------- Summary: Modernize the teiid configuration Key: TEIID-5762 URL: https://issues.jboss.org/browse/TEIID-5762 Project: Teiid Issue Type: Sub-task Components: Server Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 12.3 The Teiid configuration is based upon an out-dated version of the wildfly config. It should be brought up-to-date. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5481) Evaluate JSONPATH as expression language for Json payload to table

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5481?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5481. ----------------------------------- Resolution: Done Marking as initially resolved. > Evaluate JSONPATH as expression language for Json payload to table > ------------------------------------------------------------------ > > Key: TEIID-5481 > URL: https://issues.jboss.org/browse/TEIID-5481 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.3 > > > Currently in Teiid in order to turn a JSON document to a relational structure, JSONTOXML function is used then XPATH used on it to retrieve data using XMLTABLE. > Investigate the feasibility of using JSONPATH [1] directly on JSON document to build a JSONTABLE construct. > [1] https://code.google.com/archive/p/json-path/ -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-101) OData issues with multiple visible schema

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-101?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on TEIIDSB-101: ---------------------------------------- Added a constructor arg for OlingoBridge (to force the fix upon upgrade) that should be set to "odata" for Teiid Spring Boot. Also updated security config paths. > OData issues with multiple visible schema > ----------------------------------------- > > Key: TEIIDSB-101 > URL: https://issues.jboss.org/browse/TEIIDSB-101 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.2.0 > > > The odata logic accommodates a subcontext specifying the schema to access. Other logic however doesn't allow for this: > * if multiple visible schema are exposed and have a cross reference, then the metadata links will be invalid as they are created based upon the Teiid Wildfly conventions. > * The keycloak logic exposes /$metadata as unsecured, but any of the schema/$metadata links would require authentication. > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2019