So you realize that sometimes you want your document to go to one collection or another, or perhaps even both. How would you do that? The cat is on vacation and so didn’t respond.
Let’s look at how to send a document to a different collection. Continue reading
Yes, my example is going to be trivial.
No, the cat is not happy with that.
Yes, I am doing it anyway.
With the advent of Solr 6.5 we have (drum roll, please) multi-term synonym support! Yes! Do that happy dance, but remember not to scuff up the floor too much.
Let’s run through a trivial example to show it off. Continue reading
Database lookups in the middle of ingesting content: reasonable request or abhorrent behavior? The cat tries to vote by breaking the radioactive vial, but isn’t alive long enough to vote.
In the meantime, there are 2 ways to make a database call from either the index pipeline or the query pipeline. While the process is very very (that’s 2 verys) similar I wouldn’t assume the logic works exactly the same until you can put a quantum lock on future behavior.
You would use the JDBC Lookup Index Pipeline stage or the JDBC Lookup Query Pipeline stage. The cat prefers the index pipeline. We’ll discuss that one.
Fusion 3.1, everybody! The following may or may not work on past, or future, versions of Fusion.
Don’t have it? Go get it! Don’t make the cat do all the work.
Question: How do I use the Fusion REST Query index pipeline stage to add additional metadata to an inbound document?
Answer: This assumes the existence of a Solr collection with metadata and that Fusion knows of its existence (that means either use the default Solr cluster that runs within Fusion or make sure that the external Solr cluster you are using is registered with Fusion).
The basic steps:
- create a collection to store the metadata and populate it the metadata of your choice
- create a collection which will hold new enhanced content with additional metadata from the first collection
- configure the index pipeline of the second collection to include the REST Query stage which will make a query to the first collection and add some content to the current inbound content of the second collection
The cat is hopping mad. Well, at least as hopping mad as a cat in a box can get.
Fusion has been on the streets since September of 2014 and there has been nary a post on this blog to talk about some of the rather inventive things that can be done with it. I am here to break that trend and do some super short blog posts that look at various things users might run into when using Fusion that aren’t necessarily in the documentation because, well, there are more interesting things to write about.
This post assumes you already have Fusion 2.4.1 up and running (you can download it from here) and that you understand the basics of search and Solr. There will not be a lot of background on the Why of Things. This is about the How of Things .
So let’s start by indexing something we can be upset about: Continue reading
Just a quick reminder that the Enterprise Search Summit 2014 is in town. Or will be next week.
You can download the show program from here and to see if you qualify for a free-exhibits only pass go here. Lucidworks even has a quick write up here.
I’ll be speaking on Tuesday, but the cat will not be in attendance. Stop by and say hi!
For a change of pace we are going to look at content flow from a different direction. Instead of importing content we are going to export it. Why would we do that? A few reasons:
- Having the content in Solr means that we can pre-process the fields during ingestion and export the changes for use in other venues (reports, backups, re-import in databases, etc.)
- Sometimes you just need to have more than one kind of backup
- Sometime you feel like a nut
How would you do that (no, not feel like a nut)? Continue reading