[JBoss JIRA] (TEIID-5415) Simplify connection handling
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5415?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5415.
-----------------------------------
Fix Version/s: 11.1
(was: 11.x)
Resolution: Done
Updated the docs to remove any post connection load balancing and added references to haproxy.
> Simplify connection handling
> ----------------------------
>
> Key: TEIID-5415
> URL: https://issues.jboss.org/browse/TEIID-5415
> Project: Teiid
> Issue Type: Quality Risk
> Components: JDBC Driver
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 11.1
>
>
> With the removal of TEIID-5411 we can further simplify our notion of connection handling. The current logic maintains a set of logins for known server instances under one logical connection. When a connection is returned to an XA pool (or the client issues special sql) the logical connection will select a new instance using a cached login if possible.
> The benefits of the current approach are:
> * works just from the hosts listed in the url
> * works with XA connection pooling or connection pooling in general with additional setup to provide simple load balancing
> The drawbacks are:
> * creates a set of logins which may mostly sit idle
> * is not load balancer aware - for example when just a load balanced end point is used. And the load balancing is just random, not intelligent.
> * requires the client to keep a pool of physical connections
> A proposal would be to keep multiple url failover, but removal all of the logic related to maintaining multiple logins under a logical connection.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (TEIID-5424) timestampadd/diff with quarter should not use 91 days
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-5424:
-------------------------------------
Summary: timestampadd/diff with quarter should not use 91 days
Key: TEIID-5424
URL: https://issues.jboss.org/browse/TEIID-5424
Project: Teiid
Issue Type: Bug
Components: JDBC Connector
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 11.1, 11.0.1, 10.3.3
Teiid 8.2 and prior used interval approximations including 91 days for a quarter - which is still reflected in the jdbc translator.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (TEIID-5419) timestampadd(SQL_TSI_QUARTER, 2, date) not working after TEIID-5327
by Ivan Semenov (JIRA)
[ https://issues.jboss.org/browse/TEIID-5419?page=com.atlassian.jira.plugin... ]
Ivan Semenov edited comment on TEIID-5419 at 7/19/18 8:15 AM:
--------------------------------------------------------------
I'm not sure if this is completely resolved
{code:sql}
select hire_date, timestampadd(SQL_TSI_QUARTER, 2, hire_date) from HR.employees where employee_id = 100
{code}
hire_date here is "2003-06-*17* 00:00:00.0"
while timestampadd(SQL_TSI_QUARTER, 2, hire_date) renders "2003-12-*16* 00:00:00.0"
i.e. 1 day less than 6 months' difference
was (Author: isemenov):
I'm not sure this is completely resolved
{code:sql}
select hire_date, timestampadd(SQL_TSI_QUARTER, 2, hire_date) from HR.employees where employee_id = 100
{code}
hire_date here is "2003-06-*17* 00:00:00.0"
while timestampadd(SQL_TSI_QUARTER, 2, hire_date) renders "2003-12-*16* 00:00:00.0"
i.e. 1 day less than 6 months difference
> timestampadd(SQL_TSI_QUARTER, 2, date) not working after TEIID-5327
> --------------------------------------------------------------------
>
> Key: TEIID-5419
> URL: https://issues.jboss.org/browse/TEIID-5419
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 10.3
> Environment: WFLYSRV0049: WildFly Full 11.0.0.Final (WildFly Core 3.0.8.Final)
> Reporter: Ivan Semenov
> Assignee: Steven Hawkins
> Fix For: 11.1, 11.0.1, 10.3.3
>
>
> After adding support for timestampadd() pushdown to Oracle in TEIID-5327 - Oracle is throwing errors for some pushed queries
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (TEIID-5419) timestampadd(SQL_TSI_QUARTER, 2, date) not working after TEIID-5327
by Ivan Semenov (JIRA)
[ https://issues.jboss.org/browse/TEIID-5419?page=com.atlassian.jira.plugin... ]
Ivan Semenov reopened TEIID-5419:
---------------------------------
I'm not sure this is completely resolved
{code:sql}
select hire_date, timestampadd(SQL_TSI_QUARTER, 2, hire_date) from HR.employees where employee_id = 100
{code}
hire_date here is "2003-06-*17* 00:00:00.0"
while timestampadd(SQL_TSI_QUARTER, 2, hire_date) renders "2003-12-*16* 00:00:00.0"
i.e. 1 day less than 6 months difference
> timestampadd(SQL_TSI_QUARTER, 2, date) not working after TEIID-5327
> --------------------------------------------------------------------
>
> Key: TEIID-5419
> URL: https://issues.jboss.org/browse/TEIID-5419
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 10.3
> Environment: WFLYSRV0049: WildFly Full 11.0.0.Final (WildFly Core 3.0.8.Final)
> Reporter: Ivan Semenov
> Assignee: Steven Hawkins
> Fix For: 11.1, 11.0.1, 10.3.3
>
>
> After adding support for timestampadd() pushdown to Oracle in TEIID-5327 - Oracle is throwing errors for some pushed queries
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (TEIID-5363) SimpleDB connector not quoting table names in internal Select queries
by Pranav K (JIRA)
[ https://issues.jboss.org/browse/TEIID-5363?page=com.atlassian.jira.plugin... ]
Pranav K commented on TEIID-5363:
---------------------------------
I updated to 10.3.2 after which I could create the source model, deploy the VDB atop that. But I am getting that similar error when I try to run a 'select * from <tableNameContainingHyphen>' query on the VDB. I am using Teiid embedded here and querying using the TeiidDriver (not that that makes a difference in this case). Are you getting this too?
Stacktrace:
[CONNECTOR] Connector worker process failed for atomic-request=0KTrLms0orhj.0.1.0
org.teiid.translator.TranslatorException: The specified query expression syntax is not valid. (Service: AmazonSimpleDB; Status Code: 400; Error Code: InvalidQueryExpression; Request ID: a1cd638d-9563-746f-a51a-fbd1c6e244fd)
at org.teiid.resource.adapter.simpledb.SimpleDBConnectionImpl.performSelect(SimpleDBConnectionImpl.java:151)
at com.testapp.simpledb.SimpleDBMetadataConnection.performSelect(SimpleDBMetadataConnection.java:100)
at org.teiid.translator.simpledb.SimpleDBQueryExecution.executeDirect(SimpleDBQueryExecution.java:77)
at org.teiid.translator.simpledb.SimpleDBQueryExecution.execute(SimpleDBQueryExecution.java:69)
at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:358)
Caused by: com.amazonaws.services.simpledb.model.InvalidQueryExpressionException: The specified query expression syntax is not valid. (Service: AmazonSimpleDB; Status Code: 400; Error Code: InvalidQueryExpression; Request ID: a1cd638d-9563-746f-a51a-fbd1c6e244fd)
at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1305)
at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:852)
at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:630)
at com.amazonaws.http.AmazonHttpClient.doExecute(AmazonHttpClient.java:405)
at com.amazonaws.http.AmazonHttpClient.executeWithTimer(AmazonHttpClient.java:367)
at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:318)
at com.amazonaws.services.simpledb.AmazonSimpleDBClient.doInvoke(AmazonSimpleDBClient.java:1039)
at com.amazonaws.services.simpledb.AmazonSimpleDBClient.invoke(AmazonSimpleDBClient.java:1009)
at com.amazonaws.services.simpledb.AmazonSimpleDBClient.select(AmazonSimpleDBClient.java:958)
at org.teiid.resource.adapter.simpledb.SimpleDBConnectionImpl.performSelect(SimpleDBConnectionImpl.java:149)
> SimpleDB connector not quoting table names in internal Select queries
> ---------------------------------------------------------------------
>
> Key: TEIID-5363
> URL: https://issues.jboss.org/browse/TEIID-5363
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Reporter: Pranav K
> Assignee: Steven Hawkins
> Fix For: 11.0, 10.3.2
>
>
> Facing an issue while querying the Simple DB connector for a specific type of tables - the tables that contain a hyphen in the name.
> According to the SimpleDB documentation:
> Attribute and domain names may appear without quotes if they contain only letters, numbers, underscores (_), or dollar symbols ($) and do not start with a number. You must quote all other attribute and domain names with the backtick (`).
> (https://docs.aws.amazon.com/AmazonSimpleDB/latest/DeveloperGuide/QuotingR...)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months