You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Tim Armstrong (JIRA)" <ji...@apache.org> on 2017/11/23 00:23:00 UTC

[jira] [Resolved] (IMPALA-663) Setting BOOST_DATE_TIME_POSIX_TIME_STD_CONFIG doesn't work.

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

Tim Armstrong resolved IMPALA-663.
----------------------------------
    Resolution: Fixed

We appear to be compiling with the flag, so I guess this works.

> Setting BOOST_DATE_TIME_POSIX_TIME_STD_CONFIG doesn't work.
> -----------------------------------------------------------
>
>                 Key: IMPALA-663
>                 URL: https://issues.apache.org/jira/browse/IMPALA-663
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>    Affects Versions: Impala 1.0
>            Reporter: Nong Li
>            Priority: Minor
>
> That flag is a compile time #define for boost to enable nanosecond precision. We need this to be compatible with the hive timestamp type.
> Unfortunately, setting this has serious problems with other boost libraries, in particular, the threading libraries. The threading libraries are, by default, compiled without this set. The threading library and Impala therefore have differently sized time structs and cannot work together.
> e.g.
> posix_time duration(xxx); // object created in impala, with the #define
> boost::time_wait(duration); // we pass this object to a library compiled without the #define and the duration object is not usable.
> This explains why we've had some issues with some of the boost sync primitives just not working.
> http://stackoverflow.com/questions/6636731/sleeping-a-boost-thread-for-some-nanoseconds



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)