PHPCR-ODM spreading table?

Question

PHP

Hello. Tell me, I have a feeling that I'm doing something wrong. There is a project where the Doctrine ODM is used and a node with its own document is created for each sneeze. As a result, one table grows to a huge size, in which a bunch of nodes are dumped with documents and mixins intertwined. There are two questions about this:
1) Due to the huge table and complexity, it becomes sometimes difficult to keep track of backward compatibility without constantly updating the documentation describing current and obsolete nodes and properties. How to deal with this and is it normal to dump everything in one heap, as in NoSQL solutions?
2) There are suspicions that if some of this is taken out into a separate ORM database with indexes and the data is selected by the second request by the UUID of the node, then everything should work much faster and more conveniently. What do you think? Will there be any pitfalls?