We're always keen to get more people involved in the Lucene search community - there's always lots to do, from deep hacking of the core code, to testing with different frameworks and clients, to creating documentation and examples. It's also just over fifteen years since Tom Mortimer and I founded Flax and we thought we should mark this birthday with some kind of event! So I'm thus very happy to announce we'll be involved in three Lucene hackday events over the next two months: Firstly, Continue reading
Boosts Considered Harmful – adventures with badly configured search
During a recent client visit we encountered a common problem in search - over-application of 'boosts', which can be used to weight the influence of matches in one particular field. For example, you might sensibly use this to make results that match a query on their title field come higher in search results. However in this case we saw huge boost values used (numbers in the hundreds) which were probably swamping everything else - and it wasn't at all clear where the values had come from, be it ex...Continue reading
Setting up your first Quepid test case
Quepid is an innovative tool from our partners Open Source Connections, which allows you to bridge the gap between content owners (who really know what's in your search index and how people might search for it) and search developers (who can tweak the search engine to improve relevance, given some examples of 'good' and 'bad' results for a query). We're increasingly using it in...Continue reading
Simple Solr connector for React.js
We've just published a simple (60 lines of code) React.js component to npm which makes it easy to perform searches on a Solr 6 instance and get the data into the app to display. Unlike Twigkit or Searchkit this is not a UI library - it is just a connector. If you use it you will have to implement all the UI components yourself. ...Continue reading
Can we fix your Solr or Elasticsearch system in a single day?
Here at Flax, we're often called in to take a look at existing Apache Solr or Elasticsearch search applications, to suggest improvements, tune-ups or enhancements. It's impossible for us to know ahead of time what we might find - out-of-date versions of the software, slow performance on either (or both) the indexing or search side of the application ...Continue reading
London Lucene Solr Meetup – Enterprising attitudes to open source search & query completion strategies
Last night the London Lucene Solr Meetup was hosted by Elsevier in their Finsbury Square offices. Our first speaker was Martin White, expert consultant, author of many books about enterprise search and intranets and visiting professor at the University of Sheffield (oh, and Fl...Continue reading
Out with the old – and in with the new Lucene query parser?
Over the years we've dealt with quite a few migration projects where the query syntax of the client's existing search engine must be preserved. This might be because other systems (or users) depend on it, or a large number of stored expressions exist and it is difficult or uneconomic to translate them all by hand. Our usual approach is to write a query parser, which understands the current syntax but creates a Continue reading
Can you make a contribution to Apache Solr core development?
As any regular reader of this blog will be aware, we use almost exclusively open source software on customer projects. To meet their requirements, we often have to extend the functionality of the software (e.g. XJOIN in Solr). As far as possible, with the agreement of the customer, we like to then contribute these changes b...Continue reading
Running out of disk space with Elasticsearch and Solr: a solution
We recently did a proof-of-concept project for a customer which ingested log events from various sources into a Kafka - Logstash - Elasticsearch - Kibana stack. This was configured with Ansible and hosted on about a dozen VMs inside the customer's main...Continue reading
Measuring search relevance scores
A series of blogs by Karen Renshaw on improving site search: