roadmap: distributed file system

[jojo05]

Have you considered supporting or providing a distributed file system ?
(like Spanner or BigTable-like systems e.g. https://github.com/baidu/tera)

It would be useful also to explain this decision (pros/cons) for users of cockroach

Jira issue: CRDB-6129

[spencerkimball]

We have thought about it. It would be fairly straightforward to add this capability to CockroachDB than building it from scratch, although it's still a non-trivial amount of work. There's a really old issue discussing this: #243. Also, some preliminary work on an RFC: https://github.com/spencerkimball/cockroach/blob/2a276bf022177511dd1053304dec7a40149e1327/docs/RFCS/egg_store.md

[jianjin]

@spencerkimball , the link you posted is 404. Is it moved to another place? if so, can you update using the new link?

For "add this capability to CockraochDB", Does what you mean the filesystem is on top of CockroachDB?

[github-actions]

We have marked this issue as stale because it has been inactive for
18 months. If this issue is still relevant, removing the stale label
or adding a comment will keep it active. Otherwise, we'll close it in
10 days to keep the issue queue tidy. Thank you for your contribution
to CockroachDB!

[Bessonov]

Interesting idea.

[github-actions]

We have marked this issue as stale because it has been inactive for
18 months. If this issue is still relevant, removing the stale label
or adding a comment will keep it active. Otherwise, we'll close it in
10 days to keep the issue queue tidy. Thank you for your contribution
to CockroachDB!

[Bessonov]

a comment will keep it active

[spencerkimball]

This issue should be closed.

…

On Tue, Sep 26 2023 at 8:25 AM, Anton Bessonov ***@***.***> wrote: a comment will keep it active — Reply to this email directly, view it on GitHub <#12344 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABO4YTKU6KTNGTLKGB4K2X3X4LCU7ANCNFSM4CZUOX3Q> . You are receiving this because you were mentioned.Message ID: ***@***.***>