You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Ferenc Gerlits (Jira)" <ji...@apache.org> on 2022/01/31 09:07:00 UTC

[jira] [Updated] (MINIFICPP-1636) Use std::filesystem instead of boost and platform specific implementations

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

Ferenc Gerlits updated MINIFICPP-1636:
--------------------------------------
    Fix Version/s: 0.12.0

> Use std::filesystem instead of boost and platform specific implementations
> --------------------------------------------------------------------------
>
>                 Key: MINIFICPP-1636
>                 URL: https://issues.apache.org/jira/browse/MINIFICPP-1636
>             Project: Apache NiFi MiNiFi C++
>          Issue Type: Improvement
>            Reporter: Gábor Gyimesi
>            Assignee: Rustam Ismayilov
>            Priority: Minor
>              Labels: MiNiFi-CPP-Hygiene
>             Fix For: 0.12.0
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> C++17 support allows us to use std::filesystem instead of the currently equivalent boost library calls. We should also investigate where std::filesystem could be used instead of a platform specific implementations.
> Note: std::filesystem::last_write_time returns std::filesystem::file_time_type which uses a platform dependent clock. This makes it hard to replace the previous implementation as the time since epoch can be different in two systems, the conversion to time_t can be difficult and also out usage of time strings may be problematic. Cpp20 standardizes the std::filesystem::file_time_type with std::chrono::file_clock which solves these problems, so it may be better to implement this when we have full Cpp20 support.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)