We currently have few open issues which are dependent on updating the
DocumentStore API

OAK-3878 - Avoid caching of NodeDocument while iterating in
BlobReferenceIterator
OAK-3001 - Simplify JournalGarbageCollector using a dedicated timestamp property

It would be good if we can decide what the api should be now such that
these issues can be addressed in 1.6 release.

May be we go for usecase specific api?

Chetan Mehrotra

Reply via email to