MarkLogic 9 Product Documentation

Query Console User Guide — Chapter 3

Accessing Query Console

To begin using Query Console, open a browser and enter the URL:

http://your_host:8000

If the application does not appear, you may not have sufficient privileges. To use Query Console, you must be a member of the qconsole-user role. If your privileges are insufficient, contact your MarkLogic Server administrator.

Query Console does not grant extra access to databases or documents. To perform operations such as document insertion or deletion or database exploration from Query Console, you must have appropriate security privileges.

The first time you launch Query Console, you should see a page similar to the following:

You should only have one Query Console session active at a time for any given MarkLogic user. Query Console saves state to MarkLogic Server. If a user has multiple Query Console sessions active concurrently, the state can become inconsistent. For example, do not log into Query Console as the same user in multiple browsers or browser tabs.

Creating a Query

This section walks you through creating a new query.

The following example assumes an empty workspace named Workspace, populated only with the default initial XQuery query, named Query 1. This is the configuration you see the first time you launch Query Console.

To create and run a query:

1. If the current workspace is not Workspace, click on the workspace dropdown on the upper right and select the workspace named Workspace.
2. Click on the "+" at the top of the query editor to the right of the open query tabs. A new query is created and opened in the editor. The new query also appears in the workspace panel on the right.

   

3. Double-click on the query name in the tab at the top of the editor and type in a meaningful name for the query, such as hello. Notice the name changes in the tab and in the workspace panel on the right.

   

   You can also rename a query by double-clicking its name in the workspace panel.

   

4. Choose the query type by clicking on the Query Type dropdown to the right of the Server dropdown list. For this example, select XQuery.

   

The Query Type determines the evaluation context for your query when you run it. The supported query langages are:

• Server-Side JavaScript
• XQuery
• SQL
• SPARQL Query
• SPARQL Update

The following example shows a native SPARQL query with the Query Type set appropriately.

In XQuery and JavaScript, Query Console displays suggestions for matching functions, variables, and keywords as you type. For example:

If you click on a suggestion, Query Console adds the suggestion text to your query. For example, if you select documentGet in the list above, then the following text is entered into your query. You can replace the suggestion parameters with values appropriate to your task.

For a function, Query Console also display reference documentation to the right of the suggestions. For example:

Running a Query

Follow this procedure to evaluate a query and view the results. You should already have entered your query in the query editor and selected the appropriate Query Type. If not, refer to Creating a Query.

1. Click on the Database dropdown at the top of the editor to select the content database against which to run the query. For this example, you can use any database.

   

2. Click on the Server dropdown at the top of the editor to select the App Server against which to run the query. For this example, you can use any App Server.

   

3. Click the Run button to evaluate the query. In this case, the default "hello world" query. The prettyprinted results display in the output pane at the bottom of the page.

   

4. To view the query results as plain text, click the result format dropdown on the far right of the results pane and select Text. Your query results display as plain text.

   

5. To view the query results without prettyprint formatting, click the Raw button on the Result tab. Your raw query results display in the results pane at the bottom of the page. For details, see Changing the Query Output Format.

Each query has its own Results display tab, so you can switch between queries without losing the results of a run.

Each time you run a particular query, the results tab reports how long the query took and the time difference between the current and previous run. For example:

If your query returns a sequence of values, Query console reports the number of items in the sequence so you can distinguish between returning a sequence of one item versus a single item (not in a sequence).

Changing the Query Output Format

Query Console supports two modes for displaying query results, Auto and Raw. The default mode is Auto. In Auto mode, your query results are formatted for readability based on the query and the output type. For example:

• XML and JSON query results are displayed with syntax coloring and UI elements that allow you to expand and collapse the element tree. Sequences are unrolled to line items with individual formatting controls.
• Results from a SQL query (run in SQL mode) are formatted as a table.
• Results from a SPARQL query display matching IRIs.

In Auto mode, you can override the default rendering using the format dropdown at the far right of the results pane.

For example, strings are rendered as text by default, but if you know the string contains serialized JSON, you can change the rendering to JSON to get syntax highlighting and tree controls. The choices on the format dropdown depend on the type of data returned by your query.

Raw mode always displays plain text, but it is not necessarily the query results exactly as returned from MarkLogic Server. Slight formatting changes are still applied to improve readability. For example, even in Raw mode, an XQuery sequence or JavaScript Sequence displays as line items.

Using the Query Execution History

Each time you modify a query and evaluate it, Query Console saves the contents and time of execution in the Query History. Query Console maintains a separate history for each query.

Query Console adds a history entry for each unique version of a query. If the query text is unchanged between runs or if the changes create a duplicate of an existing history entry for the query, Query Console does not create a new entry.

Query Console saves at most 50 history entries.

To use the query history:

1. Click the Query History dropdown on the upper right. The history appears, with the most recent runs at the top of the list.

   

2. To revert the query to a previous state, click on a history entry. The selected query version is restored in the editor.

   

To remove a history entry, click the delete (X) button in the upper right corner of the entry.

To close the history dropdown, click on the Query History dropdown again, or simply move the mouse outside the dropdown.

Profiling a Query

You can use Query Console to profile the performance of an XQuery or Server-Side JavaScript query. For XQuery, Query Console profiles your query as if you passed your query to prof:invoke, and then displays a performance report in the results pane.

Profiling must be enabled on an App Server before you can profile a query. It is enabled by default when you create an App Server. For details, see Enabling Profiling on an App Server in the Query Performance and Tuning Guide.

Use the following procedure to profile a query:

1. Click the Profile tab at the top of the result panel. The profile tab is brought to the front.

   

2. Click the Run button to evaluate your query. A profiling report appears. If no profiling report appears, profiling may not be enabled for your App Server.

   

   In XQuery, your Query Console query appears as the .main module in the profiling report. In JavaScript, your query appears as (program).

3. Click on a profiling report column header to sort the profiling data by a particular column. Each time you click a column, the order toggles between ascending and descending.
4. Click on the Result tab to view the output from your query.

When profiling a JavaScript query, you can click on the download icon in the upper right of the profiling report to save your profiling data in format that can be imported into the Profiles tab of the Chrome browser developer tools.

For details on profiling queries and the meaning of the profile report columns, see Profiling Requests to Evaluate Performance in Query Performance and Tuning Guide.

Exploring a Database

Use the Explorer feature to browse the contents of a database. This topic explains how to use the Explorer to explore the contents of a database. You can also use the Explorer to modify database contents; for details, see Editing Database Content.

To explore a database:

1. Select a database from the Database dropdown at the top of the current query.
2. Click Explore, to the right of the Database dropdown. Query Console displays a list of the documents in the selected database in the Explorer. For example:

   

   For each document in the database, the summary includes the document URI, the type and name of the root node, a link to the document properties, and a link to any collections to which the document belongs.

3. Optionally, enter a wildcard expression or URI in the search box to filter the list of documents by URI. For more details, see Filtering the Explorer View by URI.

   

4. Click on a document URI to explore the document contents and metadata. The content is displayed by default.

   

5. Click on one of the metadata categories above the content to explore details about that category. For example, click on Metadata to explore the document's key-value metadata:

   

6. Use the forward and back buttons in the upper left of the Explorer to navigate as you drill down into document contents and metadata. For example, to return to the database content summary after clicking on a document's URI, click the back arrow.

   

7. To explore the collections or properties of a document from the document list, click the link in the Collections or Properties column.

   

Filtering the Explorer View by URI

Use the search box of the Explorer to explore only a specific document or the documents that match a wildcard expression. The match uses the same semantics as the XQuery function cts:uri-match or the Server-Side JavaScript function cts.uriMatch.

The URI lexicon must be enabled on the database you are exploring. You will get an error if the URI lexicon is not enabled.

The following semantics apply to filtering by URI:

• Your regular expression can include the following wildcard characters. These characters can occur multiple times and in any position.
  • "*" : Matches zero or more non-space characters.
  • "?": Matches exactly one non-space character.
• If all the non-wildcard characters in your expression are lower case, then the matching is case insensitive. Otherwise, the matching is case sensitive.
• If your regular expression contains no diacritics, then the matching is diacritic insensitive. Otherwise, the matching is diacritic sensitive.
• The URI filter is combined with any collection filter. For example if you enter "*.xml" in the search box and then click on the name of a collection in the Collections column of the Explorer, you see documents in that collection that end with ".xml".

The following table contains some examples of filtering expressions:

Editing Database Content

You can use the Explorer to modify your database content without writing code. See the following topics for details:

• Inserting a New Document
• Modifying an Existing Document
• Deleting Documents

You can only insert or update content. You cannot modify metadata such as permissions and properties.

Organizing Queries with Workspaces

In Query Console, you organize your queries in workspaces. You can create multiple workspaces. However, only one workspace is active at a time. When you create a new query, Query Console automatically saves it in the active workspace.

• Workspace Overview
• Renaming a Workspace
• Copying a Workspace
• Deleting a Workspace
• Exporting a Workspace
• Importing a Workspace