Blog

I’ve seen a couple cases recently where we were making modifications to a document in MarkLogic and the process was restricted to a single thread due to concerns about overwriting data. Let’s look at an example. function makeUpdates(someArgs) { let uri = ‘/some/content.json’; let docObj = cts.doc(uri).toObject(); docObj.meta.foo = updateFoo(docObj.meta.foo, someArgs); xdmp.documentInsert( uri, docObj, { […]

We’re used to doing reviews for source code. NiFi flows look different, but when they are part of your application’s code, it’s useful to have a review prior to committing. Here’s what I look for when I’m reviewing a flow: Named processors. Wherever it would make things more clear, change the name of the processor […]

The NiFi EvaluateJsonPath processor lets you specify a JSON path, which will be applied to the content of a flow file. For most situations that works great, but what if you want to retrieve a value where the property you want to read depends on a flow file attribute? EvaluateJsonPath doesn’t support the expression language […]

If you have made or are considering an investment in MarkLogic, you’ve got an opportunity or problem you weren’t able to address with traditional databases. You’ve selected great technology and you see real value to your business. Next challenge: implementation. You’ve got a good team of developers, but MarkLogic is new to them. They are […]