I will try the configs at runtime to avoid cluttering folders and jvm 
settings.

Thanks for your help!!

On Tuesday, July 14, 2015 at 10:18:09 AM UTC-6, José Cornado wrote:
>
> Hello again! :-}
>
> I am embedding your jars inside the plugin's dir. Should a "config" dir 
> inside that dir suffice? Another question what memory cost does a vertex, 
> edge have? I am trying to figure out a reasonable element count for bulk 
> operations.
>
> Thanks a lot!!! 
>
> On Tuesday, July 14, 2015 at 7:17:48 AM UTC-6, Luigi Dell'Aquila wrote:
>>
>> Hi Jose,
>>
>> OrientDB uses default JDK logging functionalities, so you can just modify 
>>
>> config/orientdb-client-log.properties
>> config/orientdb-server-log.properties
>>
>> and change log levels
>>
>> Luigi
>>
>>
>>
>>
>>
>> 2015-07-14 15:00 GMT+02:00 José Cornado <[email protected]>:
>>
>>> A couple of questions:
>>>
>>> What does a transaction commit/rollback?
>>>
>>> Is there a way to mute the warning logs? redirect them to a file?
>>>
>>> I need to modify the graph structure on the fly. It  models source code. 
>>> The model changes as the user creates/modifies tests.
>>>
>>> The UI thread captures the code paths  and values, writes to disk a 
>>> vertex id and sends the rest of the work to the backgrounder that finishes 
>>> the modeling.
>>>
>>> It sounds as if no TXs are needed.
>>>
>>> On Tuesday, July 14, 2015 at 1:18:44 AM UTC-6, Luigi Dell'Aquila wrote:
>>>>
>>>> Hi Josè,
>>>>
>>>> I'm not sure where the problem exactly is, but I can give you two 
>>>> pointers:
>>>> 1) schema creation has to be managed outside of transaction, using 
>>>> OrientGraphNoTx
>>>> 2) when you try to create an edge or a vertex, the driver checks 
>>>> whether the edge/vertex class exists, and in case it tries to create it
>>>>
>>>> My general suggestion is to check/create the schema when the plugin 
>>>> starts up, using an OrientGraphNoTx
>>>>
>>>> Thanks
>>>>
>>>> Luigi
>>>>
>>>>
>>>> 2015-07-13 20:30 GMT+02:00 José Cornado <[email protected]>:
>>>>
>>>>> Forgot to mention that I am running .12 on OSX 10.9 1.7 jvm. And 
>>>>> creating the instance as follows:
>>>>>
>>>>> OrientGraph("plocal:....")
>>>>>
>>>>> On Monday, July 13, 2015 at 9:54:18 AM UTC-6, José Cornado wrote:
>>>>>>
>>>>>> First, great job! I am embedding the graph DB inside an eclipse 
>>>>>> plug-in and the startup and shutdown are really fast. It is hard to 
>>>>>> notice 
>>>>>> that in addition to the plugin a DB is being used.
>>>>>>
>>>>>> Even when I do something wrong it fails quickly and gracefully.
>>>>>>
>>>>>> I have a question: 
>>>>>>
>>>>>> As a rule of thumb I issue a begin/commit or rollback (commit if a 
>>>>>> write occurs rollback if it is only reading) every time I access the 
>>>>>> graph. 
>>>>>> Two threads access the graph: the ui thread and the backgrounder. Even 
>>>>>> though when the exception occurs the ui thread is idle.
>>>>>>
>>>>>> The message is kind of puzzling. What I am missing?
>>>>>>
>>>>>> Thanks a lot!!
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>  -- 
>>>>>
>>>>> --- 
>>>>> 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.
>>>>>
>>>>
>>>>  -- 
>>>
>>> --- 
>>> 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.
>>>
>>
>>

-- 

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