Hi there, I have a use case best described by the following UT (and is reproducing the problem consistently):
https://gist.github.com/cstamas/03f9d3ca4621cf743e87 In short: - OrientDB 1.7.4, Java 7 - am using document DB (as in UT) - using a document schema and index (similar to one in UT) - adding clusters in "caterpillar" mode - the code consistently explodes on line 100 - if line 100 _removed_, it explodes on line 104, the first SELECT In both cases error refers to dropped cluster "cluster1". This UT produces following output With line 100 executed https://gist.github.com/cstamas/86822aa87f025a0d57cb With line 100 commented out (first SELECT) https://gist.github.com/cstamas/7fe60655582c9adebff8 Question: do I remove the cluster in wrong way? I expect to simply "drop" all the records that were in cluster1, and that is what actually happens, so far so good. But the problem later are indexes.... If not rebuilt, they refer to dropped cluster, but cannot rebuild them either, due to same problem.... So, how could this be done in proper way, with indexes being properly maintained? What do i miss? Thanks, ~t~ -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
