[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)
6 years, 5 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... ]
Work on TEIIDSB-127 started by Steven Hawkins.
----------------------------------------------
> "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
[JBoss JIRA] (TEIID-5829) Impala Translator - Mixed Results in Native Function Pushdown
by Scott Wallace (Jira)
[ https://issues.jboss.org/browse/TEIID-5829?page=com.atlassian.jira.plugin... ]
Scott Wallace updated TEIID-5829:
---------------------------------
Description:
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}
was:
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 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 *correct* resulting 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}
> 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)
6 years, 5 months
[JBoss JIRA] (TEIID-5829) Impala Translator - Mixed Results in Native Function Pushdown
by Scott Wallace (Jira)
[ https://issues.jboss.org/browse/TEIID-5829?page=com.atlassian.jira.plugin... ]
Scott Wallace updated TEIID-5829:
---------------------------------
Description:
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 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 *correct* resulting 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}
was:
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 Impala query for the above Teiid query is:
{{SELECT col1
FROM impala_table
WHERE regexp_replace(col1,'\\\\047','') = 'SomeString'}}
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:
{{SELECT col1
FROM TeiidView1
WHERE impala.regexp_replace(col1, '\047', '') = 'SomeString'
LIMIT 100}}
Here is the *correct* resulting Impala query for the above example Teiid query with LIMIT clause:
{{SELECT col1
FROM impala_table
WHERE regexp_replace(g_1.advertiser_name, '\\047', '') = 'SomeString'
LIMIT 100}}
> 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 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 *correct* resulting 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)
6 years, 5 months
[JBoss JIRA] (TEIID-5829) Impala Translator - Mixed Results in Native Function Pushdown
by Scott Wallace (Jira)
[ https://issues.jboss.org/browse/TEIID-5829?page=com.atlassian.jira.plugin... ]
Scott Wallace updated TEIID-5829:
---------------------------------
Description:
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 Impala query for the above Teiid query is:
{{SELECT col1
FROM impala_table
WHERE regexp_replace(col1,'\\\\047','') = 'SomeString'}}
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:
{{SELECT col1
FROM TeiidView1
WHERE impala.regexp_replace(col1, '\047', '') = 'SomeString'
LIMIT 100}}
Here is the *correct* resulting Impala query for the above example Teiid query with LIMIT clause:
{{SELECT col1
FROM impala_table
WHERE regexp_replace(g_1.advertiser_name, '\\047', '') = 'SomeString'
LIMIT 100}}
was:
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:
{{SELECT col1
FROM TeiidView1
WHERE impala.regexp_replace(col1, '\047', '') = 'SomeString'}}
Looking at the Impala generated query, it is not passing the arguments to the function correctly. The resulting Impala query for the above Teiid query is:
{{SELECT col1
FROM impala_table
WHERE regexp_replace(col1,'\\\\047','') = 'SomeString'}}
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:
{{SELECT col1
FROM TeiidView1
WHERE impala.regexp_replace(col1, '\047', '') = 'SomeString'
LIMIT 100}}
Here is the *correct* resulting Impala query for the above example Teiid query with LIMIT clause:
{{SELECT col1
FROM impala_table
WHERE regexp_replace(g_1.advertiser_name, '\\047', '') = 'SomeString'
LIMIT 100}}
> 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 Impala query for the above Teiid query is:
> {{SELECT col1
> FROM impala_table
> WHERE regexp_replace(col1,'\\\\047','') = 'SomeString'}}
> 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:
> {{SELECT col1
> FROM TeiidView1
> WHERE impala.regexp_replace(col1, '\047', '') = 'SomeString'
> LIMIT 100}}
> Here is the *correct* resulting Impala query for the above example Teiid query with LIMIT clause:
> {{SELECT col1
> FROM impala_table
> WHERE regexp_replace(g_1.advertiser_name, '\\047', '') = 'SomeString'
> LIMIT 100}}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (TEIID-5829) Impala Translator - Mixed Results in Native Function Pushdown
by Scott Wallace (Jira)
Scott Wallace created TEIID-5829:
------------------------------------
Summary: 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
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:
{{SELECT col1
FROM TeiidView1
WHERE impala.regexp_replace(col1, '\047', '') = 'SomeString'}}
Looking at the Impala generated query, it is not passing the arguments to the function correctly. The resulting Impala query for the above Teiid query is:
{{SELECT col1
FROM impala_table
WHERE regexp_replace(col1,'\\\\047','') = 'SomeString'}}
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:
{{SELECT col1
FROM TeiidView1
WHERE impala.regexp_replace(col1, '\047', '') = 'SomeString'
LIMIT 100}}
Here is the *correct* resulting Impala query for the above example Teiid query with LIMIT clause:
{{SELECT col1
FROM impala_table
WHERE regexp_replace(g_1.advertiser_name, '\\047', '') = 'SomeString'
LIMIT 100}}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (TEIID-5827) XA datasource properties are undefined
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5827?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5827.
-----------------------------------
Resolution: Done
URL has now replaced connection-url for xa as full property. Most other xa-datasource-properties will need to be set through connection-properties though.
> XA datasource properties are undefined
> --------------------------------------
>
> Key: TEIID-5827
> URL: https://issues.jboss.org/browse/TEIID-5827
> Project: Teiid
> Issue Type: Bug
> Components: AdminApi
> Reporter: Mark Tawk
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 13.0, 12.2.2, 12.3.1
>
>
> 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:
>
> {code:java}
> // 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);
> }
> {code}
> 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:
>
> {code:java}
> "xa-datasource-properties" => {
> "DatabaseName" => undefined,
> "PortNumber" => undefined,
> "ServerName" => undefined
> }
> {code}
> 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)
6 years, 5 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:
---------------------------------------
[~rareddy] It seems vastly simpler to just have the user specify the full mongo uri. Is the only concern making the credential a separate property?
> 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)
6 years, 5 months