MARKLOGIC SERVER

Recommendations

Info

NODE.JS CLIENT API Node.js is an open source runtime environment for developing middle-tier applications in JavaScript. Node.js uses an event-driven, non-blocking I/O model that makes it useful for writing scalable web applications. Like the Java client, the Node.js Client API is a wrapper around the MarkLogic REST API. It follows best practices on both the Node and MarkLogic ends—for example, enforcing entirely asynchronous I/O and providing conveniences for building complex queries that leverage MarkLogic's rich indexes. The Node.js client can be integrated into a project using npm, the standard method for importing external Node.js libraries. Below is a typical Node.js client operation, one that reads a document from the MarkLogic database and writes the content to the console: db.documents.read('/example.json').result( function(documents) { documents.forEach(function(document) { console.log( JSON.stringify(document) ); }); }, function(error) { console.log( JSON.stringify(error) ); } ); Node.js's asynchronous programming model means that, instead of a program blocking execution while it waits for a response from the database, a Node.js program defines a callback function (passed as the first argument to result() above) to be executed when the response returns. This allows program execution to continue and for many database operations to be executed efficiently in parallel. Benefits to using the Node.js Client: • It's useful to developers familiar with Node.js who want to integrate MarkLogic into multi-tier JavaScript web applications or interact with MarkLogic via the Node.js command line. • It encapsulates the complexity associated with HTTP REST calls so developers can focus on MarkLogic functionality. This includes support for digest authentication and connection pooling. • It includes built-in support for promises, object streams, and chunked streams. • It offers automatic serialization and deserialization between JSON documents and JavaScript objects. The Node.js Client API is also being developed in the open at GitHub. You can find more information in the Node.js Application Developer's Guide. 62
SEARCH AND JSEARCH APIS The Search API is a code-level XQuery library designed to make creating search applications easier. Used by the REST API, it combines searching, search parsing, an extensible/customizable search grammar, faceting, snippeting, search term completion, and other search application features into a single API. Even those who are expert in cts:query constructs can appreciate its help in transforming user-entered strings into cts:query hierarchies. For more information, see the Search API documentation. The JSearch API is a JavaScript library that makes it straightforward for JavaScript developers to execute complex searches in MarkLogic. JSearch includes many of the same features available through the Search API and cts: functions but also returns results as JavaScript objects, lets you chain your method calls, and offers convenience methods for snippet generation and faceting. For more information, see Creating JavaScript Search Applications. SPARQL FOR QUERYING TRIPLES You can access semantic data in MarkLogic with SPARQL, which is the standard language for querying for RDF triples. (For more information about semantic features, see the "Semantics" section.) SPARQL enables you to describe RDF triple patterns and then return the triples that match those patterns. Its syntax is similar to that of SQL. For example, the following SPARQL query returns a list of people born in Paris: SELECT ?s WHERE { ?s } In MarkLogic, you can query using SPARQL in various ways: • Query Console can evaluate SPARQL directly, just like it can evaluate XQuery and JavaScript. • You can use server-side XQuery and JavaScript semantic functions, which accept SPARQL queries as arguments. • You can submit SPARQL queries to semantic endpoints to access triple data via the REST API. MarkLogic also supports SPARQL Update operations. SPARQL Update is a separate standard that lets you manage collections of semantic data (semantic graphs) by inserting and deleting RDF triples. For more information about SPARQL and MarkLogic, see the Semantics Developer's Guide. 63
Page 1 and 2:
Inside MARKLOGIC SERVER Jason Hunte
Page 3 and 4:
You can find the full set of API do
Page 5 and 6:
CHAPTER 1 WHAT IS MARKLOGIC SERVER?
Page 7 and 8:
enforced, such as that no two docum
Page 9 and 10:
You can even use MarkLogic to enfor
Page 11 and 12: instance, all the way up to (in 201
Page 13 and 14: Doc1 Doc 2 Doc 3 Doc 4 a blue car t
Page 15 and 16: INDEXING LONGER PHRASES What happen
Page 17 and 18: INDEXING VALUES Now what if we want
Page 19 and 20: The indexes don't know if they're t
Page 21 and 22: for $result in cts:search( /article
Page 23 and 24: DIRECTORY INDEXES MarkLogic include
Page 25 and 26: Every fragment acts as its own self
Page 27 and 28: 4. Perform optimized order by calcu
Page 29 and 30: constraint (term lists are of no us
Page 31 and 32: Performance of range index operatio
Page 33 and 34: Fields are another way to pinpoint
Page 35 and 36: DATABASE MyDocuments FOREST MyFores
Page 37 and 38: stands. Merges tend to be CPU- and
Page 39 and 40: When doing point-in-time queries, y
Page 41 and 42: Isolating an Update When a request
Page 43 and 44: timestamp to make the fragment live
Page 45 and 46: if the global commit happened or no
Page 47 and 48: CLUSTERING AND CACHING As your data
Page 49 and 50: Expanded Tree Cache Each time a D-n
Page 51 and 52: In the regular heartbeat communicat
Page 53 and 54: QUERY QUERY LIFECYCLE 7 RESULT SET
Page 55 and 56: Figure 9: During a commit involving
Page 57 and 58: other transactions as the documents
Page 59 and 60: MODULES AND DEPLOYMENT XQuery, XSLT
Page 61: REST API FOR MULTI-TIER DEVELOPMENT
Page 65 and 66: SQL/ODBC ACCESS FOR BUSINESS INTELL
Page 67 and 68: CHAPTER 3 ADVANCED TOPICS ADVANCED
Page 69 and 70: MarkLogic provides basic language s
Page 71 and 72: as a space removed from all text, s
Page 73 and 74: If instead of matching documents th
Page 75 and 76: You can watch as the server does th
Page 77 and 78: MORE WITH FIELDS Fields also provid
Page 79 and 80: The cts:register() call returns an
Page 81 and 82: value but a latitude and longitude
Page 83 and 84: produces this XML: dog name Ch
Page 85 and 86: This XQuery code inserts the defini
Page 87 and 88: It searches across passengers, requ
Page 89 and 90: five.xml (doc ID 5): { cts:and-quer
Page 91 and 92: Valid Start: 2016-01-01 End: ∞ Sy
Page 93 and 94: BITEMPORAL QUERIES Querying on bite
Page 95 and 96: A key aspect of semantic data is no
Page 97 and 98: Triple Type Index Object values in
Page 99 and 100: estimates the efficiency of that pl
Page 101 and 102: MANAGING BACKUPS MarkLogic supports
Page 103 and 104: esult of a code bug, modifies data
Page 105 and 106: and Local-Disk Failover. Failover w
Page 107 and 108: andwidth. Local-Disk is faster when
Page 109 and 110: Contemporaneous vs. Non-Blocking Ea
Page 111 and 112: database allowed to have most of it
Page 113 and 114:
threshold needs to be reached among
Page 115 and 116:
TIERED STORAGE All storage media ar
Page 117 and 118:
storage media but still query those
Page 119 and 120:
LOW-LEVEL SYSTEM CONTROL When scali
Page 121 and 122:
OUTSIDE THE CORE That completes our
Page 123 and 124:
CONNECTOR FOR SHAREPOINT Microsoft
Page 125 and 126:
Sublime Text Plug-in An add-on to t
Page 127:
999 Skyway Road, Suite 200 San Carl
show all

MARKLOGIC SERVER

Create successful ePaper yourself

Delete template?

Save as template?