Just another data point, I did some testing of large transactions on the
graph API a while back and also ran into memory issues, but they went away
when I reduced transaction size, and called commit periodically. Have you
tried just committing the transaction periodically to rule out the
possibilit
Note since the setting seems to be configured for the graph, it looks like
you should be able to work around it by calling graph.rollback()
immediately after getting it from the factory.
On Fri, Feb 20, 2015 at 1:57 PM, Chris Wilper wrote:
> I was curious about this as I've looked a
I was curious about this as I've looked around at that code before and saw
where it was setting these flags. Looks like a bug, I've reported it here
w/details:
https://github.com/orientechnologies/orientdb/issues/3634
- Chris
On Fri, Feb 20, 2015 at 3:32 AM, Sathwik B P wrote:
> Hi,
>
> Orient
Ok, here's a simpler example illustrating the problematic behavior when
trying to use skip/limit with the distinct function:
create database memory:test
create class People
insert into People (first, last) values ('Bob', 'Smith')
insert into People (first, last) values ('Fred', 'Smith')
insert int
r case, it's Item C, which references Bag 2.
But you should notice with your data set, that the following queries both
return Bag 2:
select distinct(bag.name) from Item limit 1 offset 1
select distinct(bag.name) from Item limit 1 offset 2
- Chris
On Fri, Oct 10, 2014 at 9:44 AM, Chris Wi
4uqfmm
>
> <http://i.imgur.com/uLrR8r5.png>
>
>
> On Thursday, October 9, 2014 9:28:27 PM UTC+7, Chris Wilper wrote:
>>
>> Hi all,
>>
>> I was doing some testing with the distinct function and paging and had a
>> surprising result. It appears that th
Hi all,
I was doing some testing with the distinct function and paging and had a
surprising result. It appears that the OFFSET is evaluated before the
distinct-limited selection, which make paging distinct results a challenge.
To be concrete, given the following:
--
create database memory:test
Whoops, I was actually trying with 1.7.7, but I just tried again and it
worked fine. I must have had a typo in my console history that I
conveniently didn't repeat when typing it for my email :) Thanks!
--
---
You received this message because you are subscribed to the Google Groups
"OrientDB"
Hello,
I'm trying to figure out the best way to limit the results of a query based
on the class of a LINKed object. For example, if I have two concrete
subclasses (Bag and Jar) of a Container abstract class, and an Item class
that has a LINK attribute pointing to the container in which it logicall
I would also like to see the Object API formally deprecated (and docs
updated to clearly state that fact) if it can't be recommended going
forward. It will save newcomers from unnecessary disappointment and allow
greater focus on the core.
Thanks,
Chris
On Fri, Jul 11, 2014 at 1:20 PM, Ivanhoe A
or.java:918)
> at java.lang.Thread.run(Thread.java:662)
> at
> com.hazelcast.util.executor.PoolExecutorThreadFactory$ManagedThread.run(PoolExecutorThreadFactory.java:59)
> [node1]<-[node2] error on reading distributed request: deploy_db
>
> Thanks.
> -galina
/issues/2558
>>
>> Best regards,
>> Artem Orobets
>>
>> * Orient Technologiesthe Company behind OrientDB*
>>
>>
>> 2014-07-09 23:22 GMT+03:00 Chris Wilper :
>>
>> I just noticed this and thought it was odd behavior.
>>>
>>>
I just noticed this and thought it was odd behavior.
This code:
OClass oClass = oSchema.createClass("Test");
System.out.println(oClass.isAbstract());
System.out.println(oClass.getDefaultClusterId());
...yields this:
false
9
...but this code:
OClass oClass = oSchema.createClass("Test");
oClass
d node1, then restarted node1 and only after that I could see my
> new CUSTOMER class on the console of node2.
> So, replication happens only if one of the nodes is going down?
>
> Is this expected behavior?
>
> -Galina
>
>
> On Thursday, July 3, 2014 2:30:51 PM UTC-7, C
Another data point:
I just tried configuring replication with two nodes on the same host with a
fresh install of 1.7.4 on Windows and OSX, and I was also not successful.
But I saw different problems than you did.
Steps I followed:
1) Unpack the official distribution in two separate directories
15 matches
Mail list logo
