> > | limitation |recommended value|recommended max|absolute > max| > > |-------------------------|----------------------:|--------------------:|--------------:| > | transaction duration | | > | 5 sec | > | transaction data size | | > | 10 Mb | > | key size | 32 bytes | > 1 kB | 10 kB | > | value size | | > 10 kB | 100 kB | > > I've been thinking about the transaction duration and data size limitations too.
I think the answer is assuming every document modification can upload in multiple txns. Which more or less means building a "subspace" to work on the document, then moving/renaming the space. Or similarly upload the document under some key, then linking that key into the visible document space. Otherwise the answer becomes adding "A single document can be no larger than 10MB" as a Couch limitation. (And technically it's smaller than that because that 10MB is a global limit for the whole FDB transaction.) Unless I'm missing something, a 10MB txn can't upload more than a 10MB doc in a single txn? Similar goes for attachments. Using multiple txns: 1) makes the 5 second limit simply go away by using smaller transactions 2) potentially enables the doc to upload in parallel across multiple txns simultaneously Mike
