dubito, ergo cogito, ergo sum…”I doubt, therefore I think, therefore I am” -Descartes “If there’s any doubt, there is no doubt.” — “Sam” (Robert DeNiro) from “Ronin.” “Question Everything.” — Thinking People Throughtout the Ages “Imagination is more important than knowledge.” — Albert Einstein The above four quotes create something of a thinking proof, if […]
There are many ways you can make an asynchronous request in a JavaScript stage. Using the Apache HTTP Client Using the native Java URL or URI classes Using the native Java HttpConnection class Using the Jsoup built-in connect() method Examples of each 1) Apache HTTP Client function(doc) { var BufferedReader = java.io.BufferedReader; var InputStreamReader = […]
One of the most useful features of Nashorn JavaScript in Lucidworks Fusion is the ability to access Java objects within the context of your JavaScript stage. Often times, you’ll want to maintain the state of a variable; or maybe you want to only make a REST call once, and store the result. You can certainly […]
REST… easy! There are times you just need to reach outside the box and do something. Sometimes that something would be launching a process, or perhaps making an alternate query, or even calling some third party API, like ESRI. If the REST call you’re making doesn’t require authentication, you can do that with a plain, […]
I have been writing JavaScript for enterprise applications for more than 20 years. From that statement, it’s easy to discern that I’ve been a JavaScript advocate for a long, long time. JavaScript is a truly unique language, sporting qualities found in both procedural and functional languages. Despite this, there has always been one glaring missing […]
While Fusion comes with built-in Jsoup selector functionality, it is limited in its extraction capability. If you want to do something like extract attribute values — in particular attribute values with special characters or empty spaces in the values, you’ll need to do a custom JavaScript stage and implement the extraction there. To accomplish this: […]
When we last left our rogue query pipeline in Pt II, we had made our Solr query and had tucked the response into a JSON object. This call was made from our “main” function, which is incidentally the last function — an anonymous function — declared at the end of your stage. For example: function […]
In our prior discussion, I showed you how to override the query pipeline in Fusion. So what do we do now? Most often times, the reason people want to override is to manipulate the documents, or perform some sort of transformation on the result. The problem is that in a query pipeline you never actually […]
One of the most common questions I come across when discussing a query pipeline solution would have to be this: “How do I alter or transform the final result set?” The short answer, in Fusion 3, is that you’re not able to modify that in a query pipeline, but that you would need a middle […]