[JBoss JIRA] (TEIID-5827) XA datasource properties are undefined
by Mark Tawk (Jira)
Mark Tawk created TEIID-5827:
--------------------------------
Summary: XA datasource properties are undefined
Key: TEIID-5827
URL: https://issues.jboss.org/browse/TEIID-5827
Project: Teiid
Issue Type: Bug
Reporter: Mark Tawk
Assignee: Steven Hawkins
The method getTemplatePropertyDefinitions, in the class AdminFactory.java.
The datasource name should be "xa-data-source" instead of "data-source" when the datasource is XA. See the code snapshot below:
// get JDBC properties
if (isXA(templateName)) {
cliCall("read-resource-description", new String[] {"subsystem", "datasources", "data-source",
stripXA(templateName)}, null, builder);
addXAProperties(props);
} else {
cliCall("read-resource-description", new String[] {"subsystem", "datasources", "data-source",
templateName}, null, builder);
addDriverproperties(props);
}
Another issue, when reading using the method getDataSource in the class AdminFactory.java, it is not getting the properties recursively. and the connection properties are returned as undefined like below:
"xa-datasource-properties" => {
"DatabaseName" => undefined,
"PortNumber" => undefined,
"ServerName" => undefined
}
more details in the following forum discussion link: [https://developer.jboss.org/thread/280411?start=15&tstart=0]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months
[JBoss JIRA] (TEIID-5825) allow connection to mongodb cluster on atlas (cloud.mongodb.com)
by Marco Ardito (Jira)
[ https://issues.jboss.org/browse/TEIID-5825?page=com.atlassian.jira.plugin... ]
Marco Ardito updated TEIID-5825:
--------------------------------
Description:
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
was:
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, 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
> allow connection to mongodb cluster on atlas (cloud.mongodb.com)
> ----------------------------------------------------------------
>
> Key: TEIID-5825
> URL: https://issues.jboss.org/browse/TEIID-5825
> Project: Teiid
> Issue Type: Bug
> Components: Connector API
> Affects Versions: 12.2
> Reporter: Marco Ardito
> Assignee: Steven Hawkins
> Priority: Major
>
> 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)
5 years, 3 months
[JBoss JIRA] (TEIID-5825) allow connection to mongodb cluster on atlas (cloud.mongodb.com)
by Marco Ardito (Jira)
Marco Ardito created TEIID-5825:
-----------------------------------
Summary: allow connection to mongodb cluster on atlas (cloud.mongodb.com)
Key: TEIID-5825
URL: https://issues.jboss.org/browse/TEIID-5825
Project: Teiid
Issue Type: Bug
Components: Connector API
Affects Versions: 12.2
Reporter: Marco Ardito
Assignee: Steven Hawkins
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, 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)
5 years, 3 months
[JBoss JIRA] (TEIIDSB-121) cpu utilization on 100% when generate openapi doc by metadata
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIIDSB-121?page=com.atlassian.jira.plugi... ]
Steven Hawkins resolved TEIIDSB-121.
------------------------------------
Resolution: Cannot Reproduce
I'm not able to reproduce this based upon what's here. If there's a way to provide a sanitized edm file that would be best. Locally I generated a schema from 100 views defined as:
create view v0 (col1 integer primary key , col2 integer, .. col100 integer, foreign key (col1) references v1(col1), .. foreign key (col10) references v10(col1)) as SELECT 1, ...;
So that's 100 views each with 100 columns and 10 relationships and I can't get to what you are describing. From what I can see there is simple linear scaling in the generation time from there - scaling out to 200 views roughly doubles the time.
> cpu utilization on 100% when generate openapi doc by metadata
> -------------------------------------------------------------
>
> Key: TEIIDSB-121
> URL: https://issues.jboss.org/browse/TEIIDSB-121
> Project: Teiid Spring Boot
> Issue Type: Bug
> Components: datasource, OData
> Affects Versions: 1.2.0
> Reporter: Renat Eskenin
> Assignee: Steven Hawkins
> Priority: Major
>
> When i get request as
> http://localhost:8080/odata/swagger.json or http://localhost:8080/odata/datasource/Account/swagger.json or http://localhost:8080/odata/datasource/swagger.json
> cpu utilization 100% and i do not get any response.
> We have 2 bad approach:
> 1. In org.teiid.olingo.web.OpenApiHandler:151 teiid create tmp file in filesystem.
> Its bad because in Docker k8s systems applications can't create any files in FS.
> 2. In org.apache.xalan.transformer.TransformerImpl:709 we get system freeze (CPU utilization 100% infinite)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months
[JBoss JIRA] (TEIID-5824) Document socket keep-alive options
by Steven Hawkins (Jira)
Steven Hawkins created TEIID-5824:
-------------------------------------
Summary: Document socket keep-alive options
Key: TEIID-5824
URL: https://issues.jboss.org/browse/TEIID-5824
Project: Teiid
Issue Type: Quality Risk
Components: Documentation, JDBC Driver
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 13.0
With the explicit client ping removed (or disabled in older versions), there may be very little traffic on a given connection which may cause load balancers to timeout a connection in the middle of a long-running query. We should add docs to workaround this by setting the os level socket idle time: http://coryklein.com/tcp/2015/11/25/custom-configuration-of-tcp-socket-ke...
With java 11 there are also java level socket configuration for setting that on a per socket basis that we can consider exposing.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months
[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 updated TEIIDSB-127:
----------------------------------
Description:
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?
was:
When we used management.server.port=8081 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?
> "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
> 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)
5 years, 3 months
[JBoss JIRA] (TEIIDSB-127) "No registered data sources found" if used "management.server.port=8081"
by Renat Eskenin (Jira)
Renat Eskenin created TEIIDSB-127:
-------------------------------------
Summary: "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
When we used management.server.port=8081 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, 3 months
[JBoss JIRA] (TEIID-5753) Please add extension metadata support to allow for an invisibility option on single foreign tables/views for odata layer
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5753?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5753:
---------------------------------------
The most general solution is to add the visible flag to schema objects as well. However there are quite a few changes that are needed for that - teiid system metadata, odata metadata, even places in pg metadata.
Alternatively a grant based approach would be an exception to the deny all assumption - that is there is an implicit permission in odata that makes stuff visible and you have to issue an explicit deny to remove it.
The final approach is extension metadata specific to the odata interface - which is the most informal.
I'm not quite sure yet which of these makes the most sense.
> Please add extension metadata support to allow for an invisibility option on single foreign tables/views for odata layer
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIID-5753
> URL: https://issues.jboss.org/browse/TEIID-5753
> Project: Teiid
> Issue Type: Enhancement
> Components: OData
> Reporter: Christoph John
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 13.0
>
>
> The issue arose from the discussion at
> https://developer.jboss.org/message/989502#989502
> > Every tables and view I specify is becoming visible in the odata service. Of course I can use GRANT to resctrict access, however, it would be more nice to not export the tables in the odata layer in the first place. Would it be possible to add some kind of per table/view INVISIBLE OPTION for odata, or could I reach the same result in a different way and how would this look like?
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months