You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2015/04/26 01:57:38 UTC

[jira] [Resolved] (CALCITE-699) In Avatica, synchronize access to Calendar

     [ https://issues.apache.org/jira/browse/CALCITE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Hyde resolved CALCITE-699.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.3.0-incubating

Fixed in http://git-wip-us.apache.org/repos/asf/incubator-calcite/commit/a357e910.

> In Avatica, synchronize access to Calendar
> ------------------------------------------
>
>                 Key: CALCITE-699
>                 URL: https://issues.apache.org/jira/browse/CALCITE-699
>             Project: Calcite
>          Issue Type: Bug
>            Reporter: Julian Hyde
>            Assignee: Julian Hyde
>             Fix For: 1.3.0-incubating
>
>
> The Calendar class is not thread-safe. Some JDBC methods accept Calendar objects from the client. We must  synchronize on this Calendar in case the client is using the Calendar elsewhere.
> Avatica also creates Calendar objects internally. Access to those calendars does not need to be synchronized, but they are often passed into methods that accept client Calendars, and will get synchronized anyway.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)