I ran in to an issue using #rstats .Rdata files being updated on a schedule. Something went wrong and the object got corrupted.
Going to build a small package that accounts for this. Distribute the files, so if a file becomes corrupted you dont lose all your data.
Doesnt seem this already exists but would be grateful if someone could share if it does.
Will also build in partitioning so if your data is large, you can load from specific parts.
A single node solution, not a replacement for cluster distributed data storeage.
kevin / kevtoshi
npub1jf…l3krn
2023-08-02 19:24:25
Author Public Key
npub1jfnq9xsqa8zva9n8ewsk9z7deljgjdqx5km89mx429j2nany76ysgl3krnPublished at
2023-08-02 19:24:25Event JSON
{
"id": "96f1f254dac103f3d325d8dcbcf3f773bca7f5ae48be2ddb6a2a422bf3f8170c",
"pubkey": "9266029a00e9c4ce9667cba1628bcdcfe4893406a5b672ecd55164a9f664f689",
"created_at": 1691004265,
"kind": 1,
"tags": [
[
"t",
"rstats"
]
],
"content": "I ran in to an issue using #rstats .Rdata files being updated on a schedule. Something went wrong and the object got corrupted. \n\nGoing to build a small package that accounts for this. Distribute the files, so if a file becomes corrupted you dont lose all your data.\n\nDoesnt seem this already exists but would be grateful if someone could share if it does. \n\nWill also build in partitioning so if your data is large, you can load from specific parts. \n\nA single node solution, not a replacement for cluster distributed data storeage.",
"sig": "7a0b181582e881a7d9bd3ac0668b4b97c0763c5ffb95b9f43065c0f101d150c117fb2e720bdb2c2522a75ed989503bd62efbef8c5720e8008258edc8715cc4cc"
}