October 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIIDSB-127) "No registered data sources found" if used "management.server.port=8081"

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-127?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIIDSB-127: --------------------------------- Fix Version/s: 1.3.0 > "No registered data sources found" if used "management.server.port=8081" > ------------------------------------------------------------------------ > > Key: TEIIDSB-127 > URL: https://issues.jboss.org/browse/TEIIDSB-127 > Project: Teiid Spring Boot > Issue Type: Bug > Components: datasource > Affects Versions: 1.2.0 > Environment: teiid-spring-boot > Reporter: Renat Eskenin > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.3.0 > > Attachments: TEIIDSB-127.zip > > > When we used management.server.port=8081 and server.port=8080 in spring boot properties we get exception > [2019-10-10 12:12:53,806 MSK] ERROR [test] org.teiid.PROCESSOR [restartedMain]: TEIID30019 Unexpected exception for request 8fPp+5AbzHhy.0 > java.lang.IllegalArgumentException: No registered data sources found > How can we change management port for spring actuator and do not broken Teiid? -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-127) "No registered data sources found" if used "management.server.port=8081"

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-127?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIIDSB-127: --------------------------------- Sprint: DV Sprint 54 > "No registered data sources found" if used "management.server.port=8081" > ------------------------------------------------------------------------ > > Key: TEIIDSB-127 > URL: https://issues.jboss.org/browse/TEIIDSB-127 > Project: Teiid Spring Boot > Issue Type: Bug > Components: datasource > Affects Versions: 1.2.0 > Environment: teiid-spring-boot > Reporter: Renat Eskenin > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.3.0 > > Attachments: TEIIDSB-127.zip > > > When we used management.server.port=8081 and server.port=8080 in spring boot properties we get exception > [2019-10-10 12:12:53,806 MSK] ERROR [test] org.teiid.PROCESSOR [restartedMain]: TEIID30019 Unexpected exception for request 8fPp+5AbzHhy.0 > java.lang.IllegalArgumentException: No registered data sources found > How can we change management port for spring actuator and do not broken Teiid? -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4251) Built in support for Postgres DB as materialization target

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-4251?page=com.atlassian.jira.plugin... ] Work on TEIID-4251 stopped by Steven Hawkins. --------------------------------------------- > Built in support for Postgres DB as materialization target > ---------------------------------------------------------- > > Key: TEIID-4251 > URL: https://issues.jboss.org/browse/TEIID-4251 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > > If Postgres database is available along with install or assumed that it is available, then some of the materialization task can be automated, like > - Creation of a common STATUS table > - Creation of the materilization targets (create views on dbms) > - On load, on undeploy and load scripts for all the materialization views > We need to device a way this to be pluggable, such that based on success of this, we can provide additional support for other sources. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-131) vdb-code-generator does not honor the VDB defined thorough imports

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-131?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIIDSB-131: --------------------------------- Sprint: DV Sprint 54 > vdb-code-generator does not honor the VDB defined thorough imports > ------------------------------------------------------------------ > > Key: TEIIDSB-131 > URL: https://issues.jboss.org/browse/TEIIDSB-131 > Project: Teiid Spring Boot > Issue Type: Bug > Components: core > Affects Versions: 1.2.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.3.0 > > > When using `vdb-code-generator` plugin to read a VDB file using the dependency mechanism, it always fails due to error in code. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-131) vdb-code-generator does not honor the VDB defined thorough imports

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-131?page=com.atlassian.jira.plugi... ] Ramesh Reddy resolved TEIIDSB-131. ---------------------------------- Resolution: Done The teiid-openshift-examples, with vdb-in-maven should work now with the updates made > vdb-code-generator does not honor the VDB defined thorough imports > ------------------------------------------------------------------ > > Key: TEIIDSB-131 > URL: https://issues.jboss.org/browse/TEIIDSB-131 > Project: Teiid Spring Boot > Issue Type: Bug > Components: core > Affects Versions: 1.2.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.3.0 > > > When using `vdb-code-generator` plugin to read a VDB file using the dependency mechanism, it always fails due to error in code. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5833) Update extension metadata uri's

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5833?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5833: --------------------------------------- In more detail: * * "set namespace" will throw an exception. Anyone using a custom namespace will need to choose a consistent name/prefix across all usage. The fix in most cases is just to remove the set namespace statement. * deprecate AbstractMetadataRecord.getProperty(String key, boolean checkUnqualified) * change all of our built-in lookups (mostly in translators) to just use the prefix name The only big breaking change is for custom translator development that were using uri fqn references to get properties. This will require a code change on their end. > Update extension metadata uri's > ------------------------------- > > Key: TEIID-5833 > URL: https://issues.jboss.org/browse/TEIID-5833 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > > There are a lot of long/old extension metadata uris - including the odata one which still references teiid designer. We should see about making these simpler - perhaps even dropping the notion of fqn vs prefix altogether so that we just deal with the raw prefixes. > The only issue with changes is when the extension properties are left fully qualified in the metadata. We'd need to lookup under both the old and new versions. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5833) Update extension metadata uri's

by Barry LaFond (Jira)

[ https://issues.jboss.org/browse/TEIID-5833?page=com.atlassian.jira.plugin... ] Barry LaFond commented on TEIID-5833: ------------------------------------- +1 too and I agree with Ramesh. Work would be in the conversion utilities. > Update extension metadata uri's > ------------------------------- > > Key: TEIID-5833 > URL: https://issues.jboss.org/browse/TEIID-5833 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > > There are a lot of long/old extension metadata uris - including the odata one which still references teiid designer. We should see about making these simpler - perhaps even dropping the notion of fqn vs prefix altogether so that we just deal with the raw prefixes. > The only issue with changes is when the extension properties are left fully qualified in the metadata. We'd need to lookup under both the old and new versions. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5833) Update extension metadata uri's

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5833?page=com.atlassian.jira.plugin... ] Work on TEIID-5833 started by Steven Hawkins. --------------------------------------------- > Update extension metadata uri's > ------------------------------- > > Key: TEIID-5833 > URL: https://issues.jboss.org/browse/TEIID-5833 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > > There are a lot of long/old extension metadata uris - including the odata one which still references teiid designer. We should see about making these simpler - perhaps even dropping the notion of fqn vs prefix altogether so that we just deal with the raw prefixes. > The only issue with changes is when the extension properties are left fully qualified in the metadata. We'd need to lookup under both the old and new versions. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5826) Odata based translators ignore column metadata from source during metadata import

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5826?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-5826: -------------------------------- Git Pull Request: https://github.com/teiid/teiid/pull/1182 > Odata based translators ignore column metadata from source during metadata import > --------------------------------------------------------------------------------- > > Key: TEIID-5826 > URL: https://issues.jboss.org/browse/TEIID-5826 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors, OData > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 13.0 > > > The OData V2 and SAP and OData V4 translators do not set column metadata such as precision and scale and length the is supplied to it through $metadata call on to the schema it builds on Teiid. Then Teiid assumes some of the defaults. > This can be fixed by setting the values to what has been delivered as part of metadata. Example here https://github.com/rareddy/sap-demo/blob/master/src/main/java/org/teiid/t... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5826) Odata based translators ignore column metadata from source during metadata import

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5826?page=com.atlassian.jira.plugin... ] Work on TEIID-5826 started by Ramesh Reddy. ------------------------------------------- > Odata based translators ignore column metadata from source during metadata import > --------------------------------------------------------------------------------- > > Key: TEIID-5826 > URL: https://issues.jboss.org/browse/TEIID-5826 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors, OData > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 13.0 > > > The OData V2 and SAP and OData V4 translators do not set column metadata such as precision and scale and length the is supplied to it through $metadata call on to the schema it builds on Teiid. Then Teiid assumes some of the defaults. > This can be fixed by setting the values to what has been delivered as part of metadata. Example here https://github.com/rareddy/sap-demo/blob/master/src/main/java/org/teiid/t... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2019