October 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5832) allow connection to mongodb cluster on atlas (cloud.mongodb.com)

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5832: ------------------------------------- Summary: allow connection to mongodb cluster on atlas (cloud.mongodb.com) Key: TEIID-5832 URL: https://issues.jboss.org/browse/TEIID-5832 Project: Teiid Issue Type: Bug Components: Connector API Affects Versions: 12.2 Reporter: Marco Ardito Assignee: Steven Hawkins Fix For: 13.0, 12.3.1 The issue is that teiid mongodb connector expects connection parameters based on the " Standard Connection String Format" instead of the "DNS Seedlist Connection Format", as defined in [https://docs.mongodb.com/manual/reference/connection-string|https://docs....] _ "In addition to the standard connection format, MongoDB supports a DNS-constructed seed list. Using DNS to construct the available servers list allows more flexibility of deployment and the ability to change the servers in rotation without reconfiguring clients."_ The following is a typical connection string for a DNS seedlist connection string: mongodb+srv://server.example.com/ and: * a port number is not needed * a different prefix is used, instead of mongodb:// => mongodb+srv:// I have a "free tier" cluster instance on cloud.mongodb,com (aka Atlas), which is limited in size and resources but should be functionally identical to a full sized paid cluster on the same platform, and it does not expire. A free tier can be activated here [https://www.mongodb.com/cloud/atlas#atlas-form-container|https://www.mong...] I tried with both the mongodb command line client and with the GUI tool Compass (https://www.mongodb.com/products/compass) which has a community edition and this different syntax works perfectly, while it is not supported by the current teiid connector, it seems there is a way to use the "old" syntax, prefixed by "mongodb:// " with server and port, to those Atlas clusters, but it is cumbersome, as it needs the user to specify more parameters, as "replicaSet" and "readPreference", at least. See https://docs.mongodb.com/manual/reference/connection-string With those additional settings I was able to connect with the Compass GUI tool, but not with the latest command line client (4.2), and anyway the teiid connector seems to not support those additional parameters,, I tried to add them as DS properties but always failed -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5828) OData layer should automatically handle being proxied

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5828?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5828. ----------------------------------- Resolution: Done Added handling of forwarded headers and indicated in the docs that the proxy setting is only for when your proxy doesn't support those headers. > OData layer should automatically handle being proxied > ----------------------------------------------------- > > Key: TEIID-5828 > URL: https://issues.jboss.org/browse/TEIID-5828 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > > When behind a proxy we should be looking for https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Forwarded and related properties rather than requiring the odata servlet be configured with proxy-base-uri -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-128) OData layer should automatically handle being proxied

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-128?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIIDSB-128. ------------------------------------ Resolution: Done Added handling based upon standard headers. This required making schema references in metadata relative so that the same metadata can be used for any call. This can be backported to a product branch if needed. > OData layer should automatically handle being proxied > ----------------------------------------------------- > > Key: TEIIDSB-128 > URL: https://issues.jboss.org/browse/TEIIDSB-128 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.3.0 > > > When behind a proxy we should be looking for https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Forwarded and related properties rather than requiring the odata servlet be configured with proxy-base-uri -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-128) OData layer should automatically handle being proxied

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-128?page=com.atlassian.jira.plugi... ] Steven Hawkins moved TEIID-5831 to TEIIDSB-128: ----------------------------------------------- Project: Teiid Spring Boot (was: Teiid) Key: TEIIDSB-128 (was: TEIID-5831) Component/s: OData (was: OData) Fix Version/s: 1.3.0 (was: 13.0) > OData layer should automatically handle being proxied > ----------------------------------------------------- > > Key: TEIIDSB-128 > URL: https://issues.jboss.org/browse/TEIIDSB-128 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.3.0 > > > When behind a proxy we should be looking for https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Forwarded and related properties rather than requiring the odata servlet be configured with proxy-base-uri -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5831) OData layer should automatically handle being proxied

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5831: ------------------------------------- Summary: OData layer should automatically handle being proxied Key: TEIID-5831 URL: https://issues.jboss.org/browse/TEIID-5831 Project: Teiid Issue Type: Quality Risk Components: OData Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 13.0 When behind a proxy we should be looking for https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Forwarded and related properties rather than requiring the odata servlet be configured with proxy-base-uri -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5828) OData layer should automatically handle being proxied

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5828?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5828: --------------------------------------- Unfortunately this is not straight-forward. On the core teiid side this complicates the metadata caching logic - we need to do a search replace or individually cache each the metadata for each proxied end-point. > OData layer should automatically handle being proxied > ----------------------------------------------------- > > Key: TEIID-5828 > URL: https://issues.jboss.org/browse/TEIID-5828 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > > When behind a proxy we should be looking for https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Forwarded and related properties rather than requiring the odata servlet be configured with proxy-base-uri -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

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

by Renat Eskenin (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-127?page=com.atlassian.jira.plugi... ] Renat Eskenin edited comment on TEIIDSB-127 at 10/17/19 2:42 PM: ----------------------------------------------------------------- Or...just think...start initialization of teiid/hibernate after recieve event ContextRefreshedEvent in spring. Its need to see code of sourse. was (Author: i3draven): Or...just think...start initialization of teiid/hibernate after recieve event ContextRefreshedEvent in spring. > "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: Steven Hawkins > Priority: Major > > 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)

6 years, 5 months

1
0
0 / 0

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

by Renat Eskenin (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-127?page=com.atlassian.jira.plugi... ] Renat Eskenin commented on TEIIDSB-127: --------------------------------------- Or...just think...start initialization of teiid/hibernate after recieve event ContextRefreshedEvent in spring. > "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: Steven Hawkins > Priority: Major > > 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)

6 years, 5 months

1
0
0 / 0

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

by Renat Eskenin (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-127?page=com.atlassian.jira.plugi... ] Renat Eskenin commented on TEIIDSB-127: --------------------------------------- Ok, you can just add error message with explanation and ask user to order his datasource :) > "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: Steven Hawkins > Priority: Major > > 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)

6 years, 5 months

1
0
0 / 0

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

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-127?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on TEIIDSB-127: ---------------------------------------- [~i3draven] See my previous comment, unfortunately that is ineffective. The TeiidAutoConfiguration is already ordered to the lowest precedence, but that doesn't actually do anything. Likewise I tried that specifically for the datasource bean as well. From my reading of the docs it appears that the order is only relative to other ordered classes/instances - so all possible source classes would probably need annotated as well. > "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: Steven Hawkins > Priority: Major > > 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)

6 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2019