rewrite intro to materialize #335
Merged
+24
−27
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
miparnisari
force-pushed
the
rewrite-intro-materialize
branch
from
df03df0 to
36ba4e3
Compare
miparnisari
force-pushed
the
rewrite-intro-materialize
branch
from
36ba4e3 to
25e1178
Compare
miparnisari
commented
Mar 19, 2025
|
|
||
| ## Current Limitations | ||
| on the path of permissions computed by Materialize, it will error out. However, your schema can still include them. |
There was a problem hiding this comment.
To be confirmed: does it error out? It is just my assumption
There was a problem hiding this comment.
correct, so long it's not in the reachability path of a watched permission, Materialize will not complain. If it does, the hydrator will fail
There was a problem hiding this comment.
can I mention "hydrator" here or is that too much information?
There was a problem hiding this comment.
Let's skip if for simplicity
miparnisari
force-pushed
the
rewrite-intro-materialize
branch
from
25e1178 to
3d21b4b
Compare
miparnisari
force-pushed
the
rewrite-intro-materialize
branch
2 times, most recently
from
ae48247 to
7417cd5
Compare
tstirrat15
reviewed
Apr 10, 2025
miparnisari
force-pushed
the
rewrite-intro-materialize
branch
from
7417cd5 to
7601e0f
Compare
miparnisari
force-pushed
the
rewrite-intro-materialize
branch
from
7601e0f to
988f0aa
Compare
igoihman
reviewed
Apr 10, 2025
igoihman
reviewed
Apr 10, 2025
| Updates occur after a relationship is written that affects a subject's membership in a permission set or a set’s permission on a specific resource. | ||
| The intent is for users to process these updates and store them to form a precomputed and denormalized view of SpiceDB permissions. | ||
| AuthZed Materialize is inspired by the Leopard index component described in the [Zanzibar paper](https://zanzibar.tech/2IoYDUFMAE:0:T). | ||
| Much like the concept of a materialized view in relational databases, AuthZed Materialize is a service that computes how permissions change after relationships |
There was a problem hiding this comment.
Suggested change
| Much like the concept of a materialized view in relational databases, AuthZed Materialize is a service that computes how permissions change after relationships | |
| Much like the concept of a materialized view in relational databases, AuthZed Materialize precomputes specified permissions defined in your SpiceDB schema. |
igoihman
reviewed
Apr 10, 2025
miparnisari
force-pushed
the
rewrite-intro-materialize
branch
from
988f0aa to
25c9f34
Compare
vroldanbet
reviewed
Apr 11, 2025
| [Dedicated]: ../guides/picking-a-product#dedicated | ||
| AuthZed Materialize is inspired by the Leopard index component described in the [Zanzibar paper](https://zanzibar.tech/2IoYDUFMAE:0:T). | ||
| Much like the concept of a materialized view in relational databases, AuthZed Materialize is a service that computes how permissions change after relationships | ||
| are written, when those relationships affect a subject's membership in a permission set or a set’s permission on a specific resource. |
There was a problem hiding this comment.
not only relationships - but also schemas
|
|
||
| ## Current Limitations | ||
| on the path of permissions computed by Materialize, it will error out. However, your schema can still include them. |
There was a problem hiding this comment.
correct, so long it's not in the reachability path of a watched permission, Materialize will not complain. If it does, the hydrator will fail
miparnisari
force-pushed
the
rewrite-intro-materialize
branch
from
25c9f34 to
9697381
Compare
|
Blocked by #340 |
miparnisari
force-pushed
the
rewrite-intro-materialize
branch
from
9697381 to
2f56d0c
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
My goal was to make the text flow better. So I structured it like so: