I think I encountered a similar situation in 1.6.1 where a deleted vertex was 
still pointed to by others - I solved it in about the same way, explicitly 
nulling the connections before deleting. 

I had not reported it since we will be attempting to move to 1.7 and was 
concerned this might be a dead issue. 

- Dexter

Dexter Pratt
Director, NDEx project
Ideker Lab UCSD / Cytoscape Consortium
[email protected]  -  [email protected]
www.ndexbio.org




On Thursday, February 6, 2014 at 8:48 AM, Jonathan Rosen wrote:

> version is 1.6.3
> 
> This problem occurred against a specific vertex. I have a vertex called store 
> that connects to products via edges. I deleted the connected products to that 
> vertex by using delete vertex where @class="products" and in.out.storename = 
> "x" 
> 
> This seemed to put that store vertex into an inconsistent state. It's edge 
> count for in_myedge was a big number, where it should have been 0.
> 
> Note that I am not using lightweight edges. I am using edges with unique 
> indexes to prevent duplication of edges between the same vertices. 
> 
> I fixed the problem by issuing update storerid set in_myedge = []
> 
> In the past, this type of problem would take down the entire database, so it 
> is good to see that the problem is now compartmentalized. However, there 
> needs to be more information about how to get Orientdb out of these types of 
> inconsistent states when they occur, and perhaps some scripts to run that 
> attempt to identify and fix these problems. Generally, when I have asked 
> about these types of problems in the past, the answer has been "you're kind 
> of screwed" or "attach a debugger to the database". This is really an 
> unacceptable answer...there needs to be a better way to fix these types of 
> inconsistent state problems. 
> 
> 
> 
> 
> 
> 
> 
> On Thu, Feb 6, 2014 at 3:34 AM, Luca Garulli <[email protected] 
> (mailto:[email protected])> wrote:
> > What version are you using?
> > Sent from Mobile device 
> > Il 05/feb/2014 22:42 "Jonathan Rosen" <[email protected] 
> > (mailto:[email protected])> ha scritto:
> > > Here is the error message:
> > > Error: 
> > > com.orientechnologies.orient.enterprise.channel.binary.OResponseProcessingException:
> > >  Exception during response processing.
> > > Error: 
> > > com.orientechnologies.orient.core.exception.OCommandExecutionException: 
> > > Error on execution of command: sql.select out_carries_product.in.name 
> > > (http://out_carries_product.in.name) from #13:4
> > > Error: java.lang.NullPointerException
> > > 
> > > 
> > > What is the best way to debug this and fix the database? 
> > > 
> > > -- 
> > >  
> > > --- 
> > > 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] 
> > > (mailto:orient-database%[email protected]).
> > > 
> > > For more options, visit https://groups.google.com/groups/opt_out.
> > -- 
> >  
> > --- 
> > You received this message because you are subscribed to a topic in the 
> > Google Groups "OrientDB" group.
> > To unsubscribe from this topic, visit 
> > https://groups.google.com/d/topic/orient-database/pJxT5aWqDds/unsubscribe.
> > To unsubscribe from this group and all its topics, send an email to 
> > [email protected] 
> > (mailto:orient-database%[email protected]).
> > For more options, visit https://groups.google.com/groups/opt_out.
> 
> -- 
>  
> --- 
> 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] 
> (mailto:[email protected]).
> For more options, visit https://groups.google.com/groups/opt_out.

-- 

--- 
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/groups/opt_out.

Reply via email to