Hey George, I'm having same issue.  any luck resolving this?

On Thursday, January 29, 2015 at 1:22:04 PM UTC-7, George Jugurt wrote:
>
> I am trying to delete some of the vertices/edges from my graph db. But it 
> looks like it somehow got corrupted and it won't let me clean it up. Is 
> there a way to force deletion of a vertex or edge of certain class, other 
> than dropping and recreating the database from scratch? 
>
> orientdb {db=df}> delete edge SampleEdge
> Error: 
> com.orientechnologies.orient.core.exception.OCommandExecutionException: 
> Error on execution of command: sql.select from SampleEdge
> Error: java.lang.NullPointerException
>
> orientdb {db=df}> delete vertex SampleVertex
> Error: com.orientechnologies.orient.core.exception.ODatabaseException: 
> Error on retrieving record #-1:-90 (cluster: null)
> Error: java.lang.IllegalArgumentException: Cannot read record #-1:-90 
> since the position is invalid in database 'df'
>
> orientdb {db=df}> delete vertex #22:39
> Error: com.orientechnologies.orient.core.exception.ODatabaseException: 
> Error on retrieving record #-1:-90 (cluster: null)
> Error: java.lang.IllegalArgumentException: Cannot read record #-1:-90 
> since the position is invalid in database 'df'
>
> orientdb {db=df}> select in_SampleEdge from #22:39
> ----+------+------------------
> #   |@CLASS|in_SampleEdge
> ----+------+------------------
> 0   |null  |[size=1905]
> ----+------+------------------
>
> orientdb {db=df}> select in() from #22:39
> Error: 
> com.orientechnologies.orient.core.exception.OCommandExecutionException: 
> Error on execution of command: sql.select in() from #22:39
> Error: java.lang.NullPointerException
>
> If I run this from studio:
> select from #22:39
> the IN shows following, I guess the nulls in the beginning are the root 
> cause:
>
> [null,null,null,null,null,null,null,null,null,null,null,"#16:14780","#16:14781","#16:14782","#16:14783","#16:14784","#16:14785","#16:14786","#16:14787","#16:14788","#16:14789","#16:14790","#16:14791",....]
>
> Version 2.0, just updated to 2.0.1 and copied over the database, but the 
> issue persists. It may be related to multi-threading, I was pumping data 
> with multiple threads using transactions with commits and rollbacks if that 
> helps.
>
> Thanks,
> George
>

-- 

--- 
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.

Reply via email to