-
Notifications
You must be signed in to change notification settings - Fork 6
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
Configure blob and schema replication via dedicated config flags #564
Comments
What happens if I write:
..? It's a stupid example, but maybe we can not express the config as booleans but as "modes"? Something like this:
|
Oh yeh, I really like the idea of having "modes" 👍 |
Thought being able to configure "max_blob_size" would also be really good. As you would if you had a server accepting uploads. |
Yeah! That's a nice addition, don't think they contradict each other |
System schemas sometimes require more specialised configuration logic compared to application schema. Currently we include all schema we want to replicate in an
allowed_schema_ids
list which includes both application and system schema ids, which isn't always that intuitive. Using dedicated config flags for configuring replication of system schema could help bring clarity.schema definition replication
Add a flag for whether we want to replicate schema definitions.
This would result in our
TargetSet
including bothschema_definition_v1
andschema_field_definition_v1
.blob replication
Globally configure (phase 1)
Add fields for configuring behaviour around blobs globally (would apply to all schema the node allows)
The resulting
TargetSet
would containblob_v1
but notblob_piece_v1
schema ids.Fine grained control per schema (phase 2)
Configure on a per-schema basis
There would need to be multiple resulting
TargetSet
s each with a dedicated replication session. The target sets would each contain one "parent" (application) schema id and thenblob_v1
andblob_piece_v1
depending on their particular configuration.Linked to #561 the
blob_data
field could later contain the on device storage space allotted to that blob type ✊The text was updated successfully, but these errors were encountered: