>From console 'info class' command show me this index correctly defined:
INDEXES (1 altogether) -------------------------------+----------------+ NAME | PROPERTIES | -------------------------------+----------------+ primary_demo | primaryid | -------------------------------+----------------+ If I execute the following query: SELECT FROM cluster:demo15q4 WHERE primaryid = 117596311 I obtain correct result in 6.456 sec(s): it is too much time for a cluster with 314858 records. I'm yet using OrientDB 2.1.16, do you suggest me to migrate to 2.2.x version? Thank you. Il 19/06/2016 14:14, Luca Garulli ha scritto: > Hi Fabio, > > The ETL approach is to query the index every time. However, if you > received that message, it means the index wasn't used in the query, so > lookups will be super slow. > > Could you please execute this query from console or studio against your db? > > EXPLAIN SELECT FROM cluster:clusterName WHERE primaryid = 117538101' > > And check if there is any involvedIndexes? > > > Best Regards, > > Luca Garulli > Founder & CEO > OrientDB <http://orientdb.com/> -- Fabio Rinnone Skype: fabiorinnone Web: http://www.fabiorinnone.eu -- --- 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.
signature.asc
Description: OpenPGP digital signature
