Null Query and Count Query take too long to execute

[Hung Tran]

Hi,

These queries are executed on OrientDB v1.7.8. And the Contact table only contains 110962 rows.

1/ A query with null in where take too long to complete. It usually takes 3-6 seconds.

    select from Contact where Account is null

    select from Contact where OwnedBy is null

2/ "Select count(1) from Contact" takes 3.149 second

Any suggestion will be appreciated!

[alessand...@gmail.com]

Hi,

did you insert an index on the field account ?

Kind regards,

Alessandro

[Hung Tran]

Hi Alessandro,

No, I don't create any index on a Link property but have indices on others

Here is Contact structure

My Best,

Hung Tran

[alessand...@gmail.com]

Hi, 

indexes do not support null values as you can see at http://orientdb.com/docs/2.1/Indexes.html#indexes-and-null-values

Try with CREATE INDEX Contact.account ON Contact (account) NOTUNIQUE_HASH_INDEX METADATA {ignoreNullValues: false}

Alessandro

[Luca Garulli]

If you want also to index NULL values, you should enable it:

http://orientdb.com/docs/2.1/Indexes.html#indexes-and-null-values

Best Regards,

Luca Garulli

Founder & CEO

OrientDB

On 24 December 2015 at 21:32, <alessand...@gmail.com> wrote:

Hi, 

indexes do not support null values,

Alessandro

--

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

[Hung Tran]

Hi,

Thank Alessandro, it's working perfectly with NULL query, but COUNT query seems to be not working

Any help will be very appreciated!

My Best,

Hung Tran

[Hung Tran]

Hi,

Thank Luca, it's working perfectly with NULL query, but COUNT query seems to be not working (it took 8.85 seconds, see my photo above)

My Best,

Hung Tran