Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Hard limits in proto files #1468

Closed
Posya opened this issue Aug 1, 2023 · 1 comment · Fixed by authzed/api#77 or #1506
Closed

Hard limits in proto files #1468

Posya opened this issue Aug 1, 2023 · 1 comment · Fixed by authzed/api#77 or #1506
Assignees
@josephschorr
Labels
area/api v1 Affects the v1 API kind/proposal Something fundamentally needs to change priority/2 medium This needs to be done

Comments

@Posya
Copy link
Contributor

Posya commented Aug 1, 2023

I made a scheme based on the scheme from Google IAM example, but at the same time, for our use, the number of relations in the role definitions was increased to 1500.
At the same time, the scheme itself has grown in size to 900 kb.
Is it possible to change the limit in the proto file, which now does not allow schemas above 256 kb? 2...4 Mb.
Could you check in your environment if SpiceDB will work fine with such large schemas?
Are there any restrictions on the size of the schema (other than the specified limits in the proto files?)
By the way, is it possible to also increase the length of the relation? Now it can be maximum 64 bytes.
@Posya
Copy link
Contributor Author

Posya commented Aug 3, 2023

I checked for myself: increasing the limit by 10 times did not lead to any problems.

@josephschorr josephschorr added area/api v1 Affects the v1 API state/gauging interest This needs to be championed before being worked on kind/proposal Something fundamentally needs to change labels Aug 3, 2023
@josephschorr josephschorr self-assigned this Aug 3, 2023
@josephschorr josephschorr added priority/2 medium This needs to be done and removed state/gauging interest This needs to be championed before being worked on labels Aug 3, 2023
josephschorr added a commit to josephschorr/spicedb that referenced this issue Aug 3, 2023
@josephschorr
Change MySQL definition columns to LONGBLOB in prep for supporting la…
ce72a7f 
…rger definitions

Part #1 of authzed#1468
@josephschorr josephschorr mentioned this issue Aug 3, 2023
Merged
josephschorr added a commit to josephschorr/api that referenced this issue Aug 3, 2023
@josephschorr
Increase allowed schema size to 4MiB
dbf36a5 
Fixes authzed/spicedb#1468
@josephschorr josephschorr mentioned this issue Aug 3, 2023
Merged
josephschorr added a commit to josephschorr/spicedb that referenced this issue Aug 3, 2023
@josephschorr
Change MySQL definition columns to LONGBLOB in prep for supporting la…
8d66d33 
…rger definitions

Part #1 of authzed#1468
@josephschorr josephschorr reopened this Aug 24, 2023
josephschorr added a commit to josephschorr/spicedb that referenced this issue Aug 24, 2023
@josephschorr
Update authzed-go to increase allowed schema size
8780609 
Fixes authzed#1468
@josephschorr josephschorr mentioned this issue Aug 24, 2023
Merged
josephschorr added a commit to josephschorr/spicedb that referenced this issue Aug 24, 2023
@josephschorr
Update authzed-go to increase allowed schema size
4fb259f 
Fixes authzed#1468
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@josephschorr josephschorr

Labels
area/api v1 Affects the v1 API kind/proposal Something fundamentally needs to change priority/2 medium This needs to be done
Projects
None yet
Milestone
No milestone
2 participants
@Posya @josephschorr