Query Mind

When we want to automate some tasks when some CRUD operation performs on the Document. We use the trigger in Marklogic. There are two types of triggers in Marklogic. 1. Pre-commit Trigger 2. Post-commit Trigger 1. Pre-commit trigger:  Trigger fire before the transaction commits, if any error is found during transaction commit, the trigger is rolled back. 2. Post-commit trigger:  Trigger fire after the transaction commits, if any error is found during transaction commit, the trigger is not rolled back.

  Ans :   A database as a layer of abstraction between forests and HTTP, WebDAV, or XDBC servers. A database is made up of data forests that are configured on hosts within the same cluster but not necessarily in the same group. Multiple HTTP, XDBC, and WebDAV servers can be connected to the same database. Modules Database : The modules database is an auxiliary database that is used to store executable XQuery, JavaScript, and REST code.  During installation, a database named Modules is created, but any database can be used as a modules database, as long as the HTTP or XDBC server is configured to use it as a modules database.  Also, it is possible to use the same database to store executable modules, to store queryable documents, and/or store triggers. Forest : A forest is a collection of XML, JSON, text, or binary documents. Forest are physically stored inside the data folder of installed MarkLogic directory: Below is the screenshot: A forest can only be attached to ...

  Marklogic is an enterprise NoSQL multi-model database management system. Enterprise:  Marklogic provides ACID transactions and government-grade security.   Atomicity:   Either all the data modifications in a transaction are performed or none are performed. Consistency:     When completed, a transaction leaves all data in a consistent state.  Isolation:     Transactions run in isolation from one another.  Durability:   A fter a transaction is completed, its effects remain even in cases of unexpected interruptions.  No SQL:              Flexibility and scalability Multi-Model:   We believe it stores all type of data in any format or shape. Management System :

  Universal index : The universal index is the indexing process of MarkLogic that Marklogic performs automatically when data is loaded into MarkLogic. By default MarkLogic indexing below universal index: Word Indexing Phrase Indexing Relationship Indexing Value Indexing Word and Phrase Indexing Inverted index: An inverted index inverts the document-word relationship into a word-documents relationship.  Each entry in the inverted index is called a  term list .  Range Index:  Ranges index is also an indexing process in Marklogic but this index is created by the developer based on project requirements. When we need a fast result in the project, we create ranges indexes.   Path range index Element range index Element attribute range index etc...

  Ans: Three main principles used in MarkLogic Server security: Authentication and Access Control Authorization Administration Authentication and Access Control: Authentication is the process of verifying user credentials for a named user. Authorization: Authorization provides the mechanism to control document access, XQuery and JavaScript code execution, and document creation.  Administration: The administration is the process of defining, configuring, and managing the security objects, such as users, roles, privileges, and permissions that implement your security policies.  Role-Based Security Model (Authorization) Roles are the central point of authorization in the MarkLogic Server security model. Privileges, users, other roles, and document permissions all relate directly to roles. 

  The Search API (e.g. search:search()) is an XQuery library that provides a high-level interface for some of the core capabilities of MarkLogic, such as search, facets, and aggregates. It uses the lower-level cts:* (and other) libraries under the covers but will save most developers a bunch of typing and debugging.