This problem is now happening to me again.

I managed to store this value in a vertex field using gremlin (by calling 
sideEffect{it,m-> it.field = m.e})

e[#36:114][#18:717-PlaysAt->#35:100]

Now I get the invalid character error and the whole class seems 
unaccessible. I can't figure out how to delete this one vertex, which is 
causing the whole class to be unaccessible. Not good for Production.


On Thursday, August 21, 2014 at 6:34:13 AM UTC+2, Lvc@ wrote:
>
> Hi Ivan,
> How did you create this?
>
> *[com.tinkerpop.blueprints.impls.orient.OrientVertex|#18:516)]*
>
> Lvc@
> ᐧ
>
>
> On 21 August 2014 05:47, Ivan Plaza <[email protected] <javascript:>> 
> wrote:
>
>>
>>  I Just updated to 1.7.8 and am unable to replicate this error, so it may 
>> be resolved in the new version.
>>
>>  Nonetheless, I would appreciate any insight into best practices for 
>> handling corrupt data, right now it seems I would have to export/import to 
>> fix any such problem...
>>
>>
>> On Wednesday, August 20, 2014 11:28:31 PM UTC, Ivan Plaza wrote:
>>>
>>> Hi,
>>>
>>> In executing some mixed SQL + Gremlin queries I set a field in a class 
>>> called Users to the following value:
>>>
>>> *[com.tinkerpop.blueprints.impls.orient.OrientVertex|#18:516)]*
>>>
>>> As a result, this record is now corrupt, and I can no longer query 
>>> anything in the Users class. I get the following error:
>>>
>>> *com.orientechnologies.orient.core.exception.OSerializationException: 
>>> Found invalid ) character at position 68 of text 
>>> userId:"53f21d555334b33c3551902d",_id:"53f3d97b8bd62325a1f83855",date:1408489851112t,active:true,test:"test",
>>>  
>>> isFriend:[com.tinkerpop.blueprints.impls.orient.OrientVertex|#18:516)]. 
>>> Ensure it is opened and closed correctly.*
>>>
>>> The value I set for the isFriend field is obviously invalid (I wanted to 
>>> set true/false instead), but I'm not concerned about that. I'm worried that 
>>> when one record is corrupt, it seems to block the entire class collection. 
>>>
>>> 1. What is the recommended way to resolve corrupt records in the 
>>> database? (given that I can't seem to query, update or delete the corrupt 
>>> record)
>>>
>>> 2. Is there a setting in OrientDB to have it ignore such errors so that 
>>> a single corrupt record does not block access to the entire class data?
>>>
>>> You can likely replicate this error by setting a field value to the 
>>> following text: "[com.tinkerpop.blueprints.
>>> impls.orient.OrientVertex|#18:516)]"
>>>
>>> I'm using 1.7
>>>
>>>
>>>  -- 
>>
>> --- 
>> 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] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 

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