-
Notifications
You must be signed in to change notification settings - Fork 62
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
Make content repository/store root configurable on a per content repository basis. #5
Comments
With the new Placement Service/Strategy feature this may now be achievable. Based on This would achieve this by
We may have to implement a precedence/sorting algorithm to ensure that your developer provided placement strategies are tried before SC-provided ones but this is on the backlog anyways. What do you think? Does this satisfy the requirement. If not, why? etc...love to hear your thoughts. |
Hey @bilak, Just pinging you to see if this is still relevant. Let me know. If I don't hear anything within 48hrs or so I will close. |
Hi @paulcwarren. I'm currently busy. If you think it's ok, then close the ticket. |
Closing. If it turns out that this doesn't satisfy the requirement then feel free to re-open. |
From @bilak >>>>
From current implementation it looks like when I want new FS content store (CS) then I need to create new entity/spring repository/content repository for it. There could be an option where all contents will be stored in one entity/content store and somehow partitioned. Let's create annotation
@FileSystemPartition
(or maybe some name which fits better) for entity field which will split contents in partitions on FS (e.g. /filesystemroot/partition1 /filesystemroot/partition2). For this there also need to be some@ContentId
generator which will guarantee the correct "sequence" id generation.Maybe
parameter andreturn type should be of Long type.The text was updated successfully, but these errors were encountered: