Database in MarkLogic and Forest?

 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 one database at a time. 
  • You cannot load data into a forest that is not attached to a database.

Stands: Stands are small data sets of compressed document data. Stands are physically stored inside the Forest directory. Each stand contains actual compressed data of documents and indexes also.

Below is the screenshot of the stands.

Comments

Post a Comment

Popular posts from this blog

What is universal index and range index?

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

How to measure query Xquery performance in Marklogic?

Image
  First, we can analyze our query by profiling the meter that is given on the Console page. It completely shows line-by-line execution time.  Here you can able to see line-by-line execution time. Based on this execution time you can re-design or tune your query.  Read the complete article here , to know a better understanding of the displayed button on the Profile button on the QConsole page.   Second, we use the  xdmp:query-meters  and  xdmp:query-trace  functions to understand and tune the performance of queries. 
Read more

The security model in Marklogic

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