Have you been assigned as a MarkLogic DBA? Need to hire one? Here’s what to expect.
In my last post, I talked about using the bindings parameter of MarkLogic’s sem.sparql function to look for multiple values in a SPARQL query. It turns out that approach doesn’t work for SPARQL Update. Let’s look at how we can do it.
With MarkLogic’s SPARQL queries, we can bind values to constraint the query. Using this capability, we can gather information about something of interest. But what if I want to query against multiple values?
MarkLogic implicitly converts data types when populating type-specific indexes. Keep in mind that the Universal Index works with exactly what you give it.
When our input data has numbered fields that we want to convert to an array, how do we express that in MarkLogic’s Hub Central?
Hub Central builds a TDE template for each entity for me, so why am I getting “SQL-TABLENOTFOUND — Unknown table”?
MarkLogic’s sem.sparqlUpdate normally runs as a separate transaction, which has implications for how locks are managed.
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.
Protect yourself from the Lost Update problem in MarkLogic.
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 on dynamic attributes. Use an ExecuteScript processor instead.