nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Very slow nxql query with some filters

Ahmad_BenMaallem

Hello,

I have a nuxeo with mongoDB which contains a lot of data.

My problem is that the following nxql query is very slow: select * from Document where ecm:isTrashed = 0

By removing the filter on ecm:isTrashed, I will have an immediate response, That's why I thought about adding an index for ecm: isTrashed in mongodb but the problem still persists.

For your information, while consulting my documents with mongoDB compass, I noticed that ecm: isTrashed does not appear in the json of my documents and it will be added only for the documents which are in the trash, maybe it is therefore, creating an index does not solve the problem.

Do you have an idea please

Find more posts tagged with

Comments

Gregory_Carlin

What about the Elasticsearch indexes and nodes?

Ahmad_BenMaallem

The Elasticsearch indexes and nodes are properly configured and initialized.

Gregory_Carlin

NXQL page provider is using the DB implementation

Ahmad_BenMaallem

Are you saying I need to add "nxql_search" to the "elasticsearch.override.pageproviders" property in nuxeo.conf ?