According to the MarkLogic documentation here, it’s possible to create a TDE view from an Optic query. The documentation mentions that after running the op:generate-view query and inserting the resulting XML into the schema database, the view should be created.

According to the MarkLogic documentation here, it’s possible to create a TDE view from an Optic query. The documentation mentions that after running the op:generate-view query and inserting the resulting XML into the schema database, the view should be created.

According to the MarkLogic documentation here, it’s possible to create a TDE view from an Optic query. The documentation mentions that after running the op:generate-view query and inserting the resulting XML into the schema database, the view should be created.

According to the MarkLogic documentation here, it’s possible to create a TDE view from an Optic query. The documentation mentions that after running the op:generate-view query and inserting the resulting XML into the schema database, the view should be created.

In my experience with MarkLogic Unit Test I have always had my modules under src/main/ml-modules. However, I have a ml-gradle project where we do not have a modules database and instead use a path to the xqy files on our local machines. I was thinking that we would have problems trying to use MarkLogic Unit Test because of this fact. When trying to install MarkLogic Unit Test, after adding the dependency in build.gradle and trying to run gradle mlLoadModules, I get the following error:

I have three records in a collection with time information recorded like this:

I manage to create the external security Oauth2.0 with Aws Cognito.
When I go the calls to the Marklogic Application Server ( via postman) i get the user authenticated.

I have requirement to count and highlight the matched terms, the below code counts OVER & LOAD as two different terms , whereas in near query(OVER NEAR/1[ordered] LOAD) this should be OVERLOAD(only one term which matched).

I have a User Defined Function I’ve written for MarkLogic that I’d like to do work over three path range indexes. The first two indexes are on element values and the third is over a document property. The path range indexes are all defined and I can confirm that querying them separately returns data for the documents returned in the document query. However, when I pass them into my aggregate function, the tuple that gets passed to the map function is empty. Do UDFs just not work with path range indexes over properties?

I try to use search:suggest function and during experiments a few questions came up.