You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After investigating I found that reading fst file actually requires data.table package to be installed while DESCRIPTION defines it as Suggested depedency. Any use of data.table should be properly escaped in such case. When we try to read fst not having data.table installed we are getting following error:
fst::write.fst(iris, "iris.fst")
>ir=fst::read.fst("iris.fst")
Loadingrequirednamespace:data.tableFailedwitherror:'there is no package called 'data.table''
The text was updated successfully, but these errors were encountered:
I think at some point data.table will end up in the Imports field again, as I plan to use data.table's fast sorting capabilities to sort chunks of data that constitute one or more groups of the data-set. Together with a merge-sort algorithm (for the chunks), that would allow for out-of-memory sorting of very big tables that are stored in a fst file.
Hi @xiaodaigh, an R only version using fst as a backend for writing the chunks might be almost as fast as a C++ implementation!
Most of the computational work during a merge sort is done in serializing and de-serializing chunks and writing- and reading the data to disk I think and the actual sorting of the chunks themselves (using data.table) will probably take less time.
You'll have to coordinate your workers however, and that will be relatively slow (especially on Windows :-))
When reading fst file we are getting extra message about loading data.table package. There should be an option to suppress that message.
After investigating I found that reading
fst
file actually requiresdata.table
package to be installed while DESCRIPTION defines it as Suggested depedency. Any use ofdata.table
should be properly escaped in such case. When we try to read fst not having data.table installed we are getting following error:The text was updated successfully, but these errors were encountered: