[
https://issues.apache.org/jira/browse/CALCITE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14511688#comment-14511688
]
Vladimir Sitnikov commented on CALCITE-699:
-------------------------------------------
Why do you think it is a good idea to synchronize on the Calendar?
There is no point in synchronizing over the Calendar if the client does not do
the same thing.
I suppose it makes sense just state that we discourage using calendar
concurrently with Calcite.
> 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
>
> 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)
