[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)
7 years, 8 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)
7 years, 8 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)
7 years, 8 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)
7 years, 8 months