Solr

Solr gotchas – core swapping

Apache Solr allows to swap two cores around for non-Cloud configurations. They take each other’s name, so it is a good way to push an updated core into a production without downtime. But an interesting question is how this is achieved. Normally, core name is it’s directory name too. So, does Solr rename the directory on the filesystem too? Not really! Instead name property in the core.properties file is updated to use the name of the other core.

Comparing Solr and Elasticsearch – My presentation

I presented at the Lucene/Solr Revolution 2014 in November, comparing Solr and Elasticsearch. The target audience was a technical person who wants to understand how similar (mostly Lucene) concepts are expressed in these two products. The presentation was only 30 minutes, so I could not go into the subject as deep as I initially hoped. But the room was more than full and people came up to me afterwards saying that they really liked the comparison and found it helpful.

Javadoc custom doclets – fun, frustration and forward motion

Javadoc is default - and often only - documentation for open source Java projects. It is generated automatically and can just be dumped on any public-facing server as a bunch of static files. Or even bundled with the distribution, if size is not an issue.

However, as project grows, several issues with using Javadoc documentation become apparent. The main issue is that Javadoc (yes, even JDK 8 one) uses frames and JavaScript for navigating the packages and classes. Which breaks any sort of direct linking to the content as well as discoverability by search engine. Yes, there are NO FRAMES links, but then the navigation becomes really cumbersome. The second issue is that generated Javadoc is using rather old HTML standards and is really not designed for Search Engine Optimization. Which means that search engines usually end up discovering random entry points following somebody’s old blog post.