[JBoss JIRA] (TEIID-5825) allow connection to mongodb cluster on atlas (cloud.mongodb.com)
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5825?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5825:
---------------------------------------
> On the SpringBoot side the properties need to be somehow aligned with what is on the Syndesis.
They have a lot of limitations with their assumptions about properties as well:
https://github.com/syndesisio/syndesis/blob/9abe94a22f90d06bc53a5ea581fd8...
You can't use the seedlist option, you can't specify credentials other than username password, no additional connection properties, etc.
> It does not have to be one to one but a way to derive from Syndesis to SB based is something we would require.
Their configuration at the end of the day constructs a uri, so it would be compatible regardless.
> There was addtional property called "cluster name" that was defined on Syndesis, which I did not yet include, so need to see how that fits in too.
Do you mean their admindb property?
I'd still vote for just handling the uri - as long as we're ok with having the credential in that string.
> 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
> 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)
5 years, 3 months
[JBoss JIRA] (TEIID-5825) allow connection to mongodb cluster on atlas (cloud.mongodb.com)
by Ramesh Reddy (Jira)
[ https://issues.jboss.org/browse/TEIID-5825?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-5825:
-------------------------------------
On the SpringBoot side the properties need to be somehow aligned with what is on the Syndesis. It does not have to be one to one but a way to derive from Syndesis to SB based is something we would require. There was addtional property called "cluster name" that was defined on Syndesis, which I did not yet include, so need to see how that fits in too.
> 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
> 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)
5 years, 3 months
[JBoss JIRA] (TEIID-5830) "reload" command increases # of buffermanger instances
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5830?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5830.
-----------------------------------
Resolution: Out of Date
This was resolved by TEIID-5025 - when the buffermanager shuts down it will cancel it's timer task as well ensuring that no one holds a reference.
On 6.4 / 8.12.x it's still possible that the weak reference held by the timer task to the buffermanager isn't cleaned up until some time later - but the shutdown method will have been called which mean that the resources held by the buffermanager should already be cleared.
> "reload" command increases # of buffermanger instances
> ------------------------------------------------------
>
> Key: TEIID-5830
> URL: https://issues.jboss.org/browse/TEIID-5830
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.12.18.6_4
> Environment: - DV 6.4.0
> Reporter: Hisanobu Okuda
> Assignee: Steven Hawkins
> Priority: Major
>
> After running "reload" command in jboss-cli,
> {code}
> $ $JBOSS_HOME/bin/jboss-cli.sh -c
> [standalone@localhost:9999 /] reload
> {code}
> The numbers of BufferManagerImpl and Cleaner are increased:
> {code}
> $ jmap -histo:live 22068 | grep BufferManagerImpl
> 1493: 2 336 org.teiid.common.buffer.impl.BufferManagerImpl
> 1625: 7 280 org.teiid.common.buffer.impl.BufferManagerImpl$Cleaner
> 2296: 2 128 org.teiid.common.buffer.impl.BufferManagerImpl$1
> {code}
--
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 Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5825?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5825:
---------------------------------------
Ignoring backwards compatibility we could just do: https://github.com/shawkins/teiid/commit/3c38bbff3a9377185d0913d926f0cc48...
> 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
> 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)
5 years, 3 months
[JBoss JIRA] (TEIID-5830) "reload" command increases # of buffermanger instances
by Hisanobu Okuda (Jira)
[ https://issues.jboss.org/browse/TEIID-5830?page=com.atlassian.jira.plugin... ]
Hisanobu Okuda updated TEIID-5830:
----------------------------------
Summary: "reload" command increases # of buffermanger instances (was: "reload" command # of buffermanger instances)
> "reload" command increases # of buffermanger instances
> ------------------------------------------------------
>
> Key: TEIID-5830
> URL: https://issues.jboss.org/browse/TEIID-5830
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.12.18.6_4
> Environment: - DV 6.4.0
> Reporter: Hisanobu Okuda
> Assignee: Steven Hawkins
> Priority: Major
>
> After running "reload" command in jboss-cli,
> {code}
> $ $JBOSS_HOME/bin/jboss-cli.sh -c
> [standalone@localhost:9999 /] reload
> {code}
> The numbers of BufferManagerImpl and Cleaner are increased:
> {code}
> $ jmap -histo:live 22068 | grep BufferManagerImpl
> 1493: 2 336 org.teiid.common.buffer.impl.BufferManagerImpl
> 1625: 7 280 org.teiid.common.buffer.impl.BufferManagerImpl$Cleaner
> 2296: 2 128 org.teiid.common.buffer.impl.BufferManagerImpl$1
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months
[JBoss JIRA] (TEIID-5830) "reload" command # of buffermanger instances
by Hisanobu Okuda (Jira)
Hisanobu Okuda created TEIID-5830:
-------------------------------------
Summary: "reload" command # of buffermanger instances
Key: TEIID-5830
URL: https://issues.jboss.org/browse/TEIID-5830
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.12.18.6_4
Environment: - DV 6.4.0
Reporter: Hisanobu Okuda
Assignee: Steven Hawkins
After running "reload" command in jboss-cli,
{code}
$ $JBOSS_HOME/bin/jboss-cli.sh -c
[standalone@localhost:9999 /] reload
{code}
The numbers of BufferManagerImpl and Cleaner are increased:
{code}
$ jmap -histo:live 22068 | grep BufferManagerImpl
1493: 2 336 org.teiid.common.buffer.impl.BufferManagerImpl
1625: 7 280 org.teiid.common.buffer.impl.BufferManagerImpl$Cleaner
2296: 2 128 org.teiid.common.buffer.impl.BufferManagerImpl$1
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months
[JBoss JIRA] (TEIID-5829) Impala Translator - Mixed Results in Native Function Pushdown
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5829?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5829.
-----------------------------------
Resolution: Cannot Reproduce
I can't seem to reproduce this on master. The output of the literal is the same for me with or without a limit and includes the additional \ to escape the \. The literal handling logic though should be the same on 9.1.1 as that hasn't changed since TEIID-3692
> Impala Translator - Mixed Results in Native Function Pushdown
> -------------------------------------------------------------
>
> Key: TEIID-5829
> URL: https://issues.jboss.org/browse/TEIID-5829
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 9.1.1
> Reporter: Scott Wallace
> Assignee: Steven Hawkins
> Priority: Minor
> Labels: Impala_Translator
>
> When running a query, which is referencing an Impala native function, regexp_replace, we are seeing inconsistent results.
> The following example Teiid query returns 0 records:
> {noformat}SELECT col1
> FROM TeiidView1
> WHERE impala.regexp_replace(col1, '\047', '') = 'SomeString'{noformat}
> Looking at the Impala generated query, it is not passing the arguments to the function correctly. The resulting (incorrect and unexpected) Impala query for the above Teiid query is:
> {noformat}SELECT col1
> FROM impala_table
> WHERE regexp_replace(col1,'\\\\047','') = 'SomeString'{noformat}
> Oddly, while experimenting, if we add the LIMIT clause to the Teiid query the argument pushdown result is correct!
> The following example Teiid query returns records:
> {noformat}SELECT col1
> FROM TeiidView1
> WHERE impala.regexp_replace(col1, '\047', '') = 'SomeString'
> LIMIT 100{noformat}
> Here is the resulting (correct and expected) Impala query for the above example Teiid query with LIMIT clause:
> {noformat}SELECT col1
> FROM impala_table
> WHERE regexp_replace(g_1.advertiser_name, '\\047', '') = 'SomeString'
> LIMIT 100{noformat}
--
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 Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIIDSB-127?page=com.atlassian.jira.plugi... ]
Steven Hawkins commented on TEIIDSB-127:
----------------------------------------
The issue here is that hibernate is running before he underlying datasource is being created [~rareddy] In TeiidAutoConfiguration I don't see that the Ordered interface has any affect - the method is not called and seems more for when you have multiple beans of the same type you are trying to order. I can't seem to find another way to order things other than to add an explicit DependsOn annotation - but that has some usability issues. Do you know of another ordering mechanism?
> "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)
5 years, 3 months
[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:
----------------------------------------
Now I can reproduce what you are seeing. There's something happening that is preventing the datasource from being registered with the MultiDataSourceTransactionManagement logic. In this case the MultiDataSourceTransactionManagement is not needed as there's only a single source, but this does need addressed.
> "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)
5 years, 3 months