-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
create files in structure to serialize to disk #24
base: master
Are you sure you want to change the base?
Conversation
Looks like it only splits, so it would be a one-way split for version control after export, but no way of combining them back for import? |
Ping @maeg02 - any comment? |
Fun Fact: I'm not sure it would be so great to go back to that pattern. If you really want individual files, you can create one definition for each block. On the other hand that would break the functionality build into the Relation element, and id mapping during import does not work across multiple files. |
Still missing merge function... |
Now the first version of Merge is in there as well, could this work? Pointers to consider: I have removed Tuple in favour of "( )" return values, these can have names and that is better than Item1, Item2, Item3 etc. What do you think? |
Poking this thread, to see if we can get it moving again |
I'd love to have a look at this, but been busy for quite a while 😕 |
Last try, any feedback? |
DRAFT DRAFT DRAFT
With that said, I have created something that you can review (dismiss), and hopefully give me some pointers if this is the correct setup.
ShuffleRunner would create one of these ShufflerDataSplitter. (Or inject somehow)
This would take the data already exported, as ShuffleBlocks blocks, then recreate them as individual blocks and send them to the already existing shuffle.Serialize.
Could the be something to continue on?