Re: [orientdb] compound index seems to be ignored
Hi, I've attached the database export, including the defined index. And here's the query: SELECT @rid FROM User WHERE state="active" AND birthdayYear <= 1994 AND birthdayYear >= 1958 AND ageMin <= 59 AND ageMax >= 59 AND height <= 176 AND height >= 161 AND heightMin <= 188 AND heightMax >= 188 AND relationship IN ["free"] AND theirRelationship IN ["free", "doesntMatter" ] AND lookingFor IN ["relationship"] AND theirLookingFor IN ["relationship", "doesntMatter" ] AND @rid NOT IN [#12:0] Thank you for conducting this test. Best regards, Mate On Friday, March 6, 2015 at 9:37:19 AM UTC+1, Luigi Dell'Aquila wrote: > > Hi, > > A small sample database and the query you execute will be enough > > Thanks > > Luigi > > > 2015-03-05 21:18 GMT+01:00 Máté Gábri >: > >> Hi Luigi, >> >> sorry I'm new to this so please forgive my noob question. What should I >> provide so that you can test it? My code (nodejs) I'm using for testing, or >> some test data with the query and index I'm using? >> >> Best regards, >> Mate >> >> On Thursday, March 5, 2015 at 10:51:26 AM UTC+1, Luigi Dell'Aquila wrote: >>> >>> Hi Mate, >>> >>> there are no limitations in the number of properties that can be >>> indexed, so there must be a bug somewhere. >>> Could you provide a test case to reproduce it? >>> >>> Thanks >>> >>> Luigi >>> >>> >>> 2015-03-04 22:25 GMT+01:00 Máté Gábri : >>> Hi, I'm trying to get familiar with OrientDB's indexing to make some performance tests. I'm running a query on a class which uses 10+ conditions in the WHERE statement with range selections, constants and IN conditions. I've created the compound index in the same order as the fields appear in the WHERE statement but it seems like the index is ignored. The EXPLAIN command shows that the index is used, but the scanned documents number is the same as the number of documents in the class. After some experimentation I came to the conclusion that with 2 conditions the index is "working", so just part of the class is scanned, but after adding the third condition the whole class is scanned. I'm just not sure wether this is normal behaviour or not. Am I missing something? Best regards, Mate -- --- 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 orient-databa...@googlegroups.com. 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 orient-databa...@googlegroups.com . >> 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 orient-database+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. test.json.gz Description: Binary data
Re: [orientdb] compound index seems to be ignored
Hi, A small sample database and the query you execute will be enough Thanks Luigi 2015-03-05 21:18 GMT+01:00 Máté Gábri : > Hi Luigi, > > sorry I'm new to this so please forgive my noob question. What should I > provide so that you can test it? My code (nodejs) I'm using for testing, or > some test data with the query and index I'm using? > > Best regards, > Mate > > On Thursday, March 5, 2015 at 10:51:26 AM UTC+1, Luigi Dell'Aquila wrote: >> >> Hi Mate, >> >> there are no limitations in the number of properties that can be indexed, >> so there must be a bug somewhere. >> Could you provide a test case to reproduce it? >> >> Thanks >> >> Luigi >> >> >> 2015-03-04 22:25 GMT+01:00 Máté Gábri : >> >>> Hi, >>> >>> I'm trying to get familiar with OrientDB's indexing to make some >>> performance tests. I'm running a query on a class which uses 10+ conditions >>> in the WHERE statement with range selections, constants and IN conditions. >>> I've created the compound index in the same order as the fields appear in >>> the WHERE statement but it seems like the index is ignored. The EXPLAIN >>> command shows that the index is used, but the scanned documents number is >>> the same as the number of documents in the class. After some >>> experimentation I came to the conclusion that with 2 conditions the index >>> is "working", so just part of the class is scanned, but after adding the >>> third condition the whole class is scanned. I'm just not sure wether this >>> is normal behaviour or not. Am I missing something? >>> >>> Best regards, >>> Mate >>> >>> -- >>> >>> --- >>> 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 orient-databa...@googlegroups.com. >>> 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 orient-database+unsubscr...@googlegroups.com. > 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 orient-database+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [orientdb] compound index seems to be ignored
Hi Luigi, sorry I'm new to this so please forgive my noob question. What should I provide so that you can test it? My code (nodejs) I'm using for testing, or some test data with the query and index I'm using? Best regards, Mate On Thursday, March 5, 2015 at 10:51:26 AM UTC+1, Luigi Dell'Aquila wrote: > > Hi Mate, > > there are no limitations in the number of properties that can be indexed, > so there must be a bug somewhere. > Could you provide a test case to reproduce it? > > Thanks > > Luigi > > > 2015-03-04 22:25 GMT+01:00 Máté Gábri >: > >> Hi, >> >> I'm trying to get familiar with OrientDB's indexing to make some >> performance tests. I'm running a query on a class which uses 10+ conditions >> in the WHERE statement with range selections, constants and IN conditions. >> I've created the compound index in the same order as the fields appear in >> the WHERE statement but it seems like the index is ignored. The EXPLAIN >> command shows that the index is used, but the scanned documents number is >> the same as the number of documents in the class. After some >> experimentation I came to the conclusion that with 2 conditions the index >> is "working", so just part of the class is scanned, but after adding the >> third condition the whole class is scanned. I'm just not sure wether this >> is normal behaviour or not. Am I missing something? >> >> Best regards, >> Mate >> >> -- >> >> --- >> 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 orient-databa...@googlegroups.com . >> 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 orient-database+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [orientdb] compound index seems to be ignored
Hi Mate, there are no limitations in the number of properties that can be indexed, so there must be a bug somewhere. Could you provide a test case to reproduce it? Thanks Luigi 2015-03-04 22:25 GMT+01:00 Máté Gábri : > Hi, > > I'm trying to get familiar with OrientDB's indexing to make some > performance tests. I'm running a query on a class which uses 10+ conditions > in the WHERE statement with range selections, constants and IN conditions. > I've created the compound index in the same order as the fields appear in > the WHERE statement but it seems like the index is ignored. The EXPLAIN > command shows that the index is used, but the scanned documents number is > the same as the number of documents in the class. After some > experimentation I came to the conclusion that with 2 conditions the index > is "working", so just part of the class is scanned, but after adding the > third condition the whole class is scanned. I'm just not sure wether this > is normal behaviour or not. Am I missing something? > > Best regards, > Mate > > -- > > --- > 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 orient-database+unsubscr...@googlegroups.com. > 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 orient-database+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[orientdb] compound index seems to be ignored
Hi, I'm trying to get familiar with OrientDB's indexing to make some performance tests. I'm running a query on a class which uses 10+ conditions in the WHERE statement with range selections, constants and IN conditions. I've created the compound index in the same order as the fields appear in the WHERE statement but it seems like the index is ignored. The EXPLAIN command shows that the index is used, but the scanned documents number is the same as the number of documents in the class. After some experimentation I came to the conclusion that with 2 conditions the index is "working", so just part of the class is scanned, but after adding the third condition the whole class is scanned. I'm just not sure wether this is normal behaviour or not. Am I missing something? Best regards, Mate -- --- 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 orient-database+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
