Github user bzz commented on the issue: https://github.com/apache/zeppelin/pull/1231 Thank you for your explanation, what's your progress on refactoring current impelemtation? Let me try to re-visit points 1-5. Also, let's make sure that behavior of BittorentRepo is consistent with other implementations, like i.e S3, so it could be a drop-in replacement for the same use-cases where S3NotebookRerpo is used by a single line of configuration change. 1. listing existing notes that shared through Bittorrent Could we use Mutable item to save a list of hashes of all notebooks, stored by this user\publicKey ? 2. checkpointing AKA creating revisions Can we store Note as Immutable item, so each "revision" of the Note will look like a separate Note with it's own Hash ? 3. listing revisions for each note Can each Note have a publicKey, so we could store a list of all revisions for each note as a Mutable item? 4. importing new note by hashcode (should work similar to current "import by URL") Hashcode should be good indeed, but this might still require changes that are discussed in #989 Let me know what you think!
--- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---