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 <gabr...@gmail.com <javascript:>>: > >> 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 <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 orient-database+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
