QRun-IO/qbit-collaboration
3
0 Fork 0
Code Issues 3 Pull Requests 10 Actions Packages Projects Releases 6 Wiki Activity

feat(attachments): bucket upload cap via object storage api (RC.4) #17

Merged
KofTwentyTwo merged 1 commits from feature/object-storage-rc4 into develop 2026-10-14 14:58:46 +00:00
Conversation 0 Commits 1 Files Changed 2
+5 -6
2 changed files with 5 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

pom.xml
+1 -1
View File
@@ -80,7 +80,7 @@
<dependency>
<groupId>com.kingsrook.qbits</groupId>
<artifactId>qbit-object-storage</artifactId>
<version>0.1.0-RC.2</version>
<version>0.1.0-RC.4</version>
</dependency>
<dependency>
<groupId>com.kingsrook.qqq</groupId>
src/main/java/com/kingsrook/qbits/collaboration/attachments/AttachmentStorage.java
+4 -5
View File
@@ -45,14 +45,13 @@ public class AttachmentStorage
}
/*******************************************************************************
** The bucket's own upload cap, when object storage exposes it through its api
** package. It does not yet (requested from qbit-object-storage), so this
** returns Long.MAX_VALUE: collaboration enforces its configured per-table cap,
** and object storage still enforces the bucket's cap when the object is put.
** The bucket's own upload cap, from object storage's api package; Long.MAX_VALUE
** when the bucket has no limit. Collaboration also enforces its per-table cap.
*******************************************************************************/
public long maxBytes(String name)
{
return (Long.MAX_VALUE);
Long max = bucket(name).maxUploadBytes();
return (max == null ? Long.MAX_VALUE : max);
}
/*******************************************************************************