Hi, Looking at RDBDocumentStore it appears that it is using same table schema for all collections. For e.g. columns like deletedOnce, hasBinary are only required for NodeDocument. However they are present in the tables
Any specific reason for doing this and not going for schema per collection? This is fine for small collection like settings and clusterNodes. But for bigger collection like journal the overhead of such empty columns might be large. It would be better if each Document provides a set of column names along with types to be indexed and then RDBDocumentStore create the correct schema. Chetan Mehrotra
