DataSets.jl
DataSets.jl copied to clipboard
JuliaComputing
This is a joint DataSets and Parquet issue — at the root of issue #59 is really that Parquet.jl is currently entirely file-based (cf https://github.com/JuliaIO/Parquet.jl/issues/145). I would love it to...
All the ways to work with a Blob (er, I suppose after 0.2.7 it's just File) are IO-based. But it's backed by a file that's cached in `tmp`. Not all...
One issue that is see with implementing create/update/delete operations (#31, #38) here in DataSets is that different data repositories may have a very different ideas of how to execute them,...
We want to be able to declare some amount of data processing on the level of DataSets. This is very much related to the users being able to declare layers...
Right now, a dataset has two unique identifiers (unique within a data repository anyhow): `name :: String` and `uuid :: UUID`. The UUID is mandatory, but not really used as...
As a user, I have a package registered on JuliaHub, and I want to upload a dataset to JuliaHub which a test script (e.g., `test/runtests.jl`) from my registered package can...
I love everything about this package and how it treats data. But it is really hard to incorporate for non-local data. Is there a sanctioned way to deal with data...
Here's a rough list of items I'm considering on the path to a DataSets-1.0 release. Several of these can and should be done prior to version 1.0 in case the...
This is a big batch of changes, implementing * A big rewrite of the `BlobTree` API to make it more coherent and simpler * Allow a dataset to be opened...
`BlobTree` currently iterates values for much the same reasoning that Dictionaries.jl does (broadcast support, etc). For cases where the name is important this might seem inconvenient. But individual `Blob` or...