This is Issue 958 moved from a Google Code project.
Added by 2012-07-19T08:47:13.000Z by DenisMik...@gmail.com.
Please review that bug for more context and additional comments, but update this bug.
Original labels: Type-Enhancement, Priority-Low, v1.3.0
This is follow-up request based on the discussion from https://groups.google.com/d/topic/orient-database/Pm9CKzdaT6k/discussion
The problem under discussion was that even if one creates custom classes bound to custom physical clusters bound to custom data segments, some data (in particular, indexes) are still stored in the default data segment which might negate the benefits of having split data segments (for example, concurrent performance).
Because the default data segment is shared, read/write access would require read/write locks which would block on concurrent access. On the other hand, if indexes were in separate segments, a write on one data segment (think - one data set) would not block reads (or writes) on another data segment (another data set).
Lvc's response to that was:
I agree that partitioning indexes in different data segments makes sense. MVRBTree API already supports this kind of partitioning allowing the selection of custom clusters. What is missed are:
* specify custom data-segments
* update the SQL create index to support this
So this issue is raised as a placeholder for potential improvement in this area.