A few days ago I dropped my Nexus 4 on a parking lot. A few cracks in the screen and unfortunately I only was able to control the lower left quarter of the screen. Fortunately USB debugging was enabled (when it’s not, stop reading, this article won’t help you) and I was able to control my phone. All I needed was a factory reset so I’m able to sell my phone to someone who’s willing to pay for a screen repair.
When you’re doing continuous integration with frequent redeployments you might run into out of memory errors or some things that won’t unload properly. The Cargo daemon will solve this for you. Before reading any further you have to promise that this is no excuse to skip testing for memory leaks!
In this article I will explain how to deploy multiple applications in a Tomcat container including some jdbc-drivers. I will use the cargo-maven2-plugin since this is the easiest option when using Jenkins (or any other ci-environment).
I won’t go too deep into all the configuration options since the manual is pretty good. I just want to get you up and running a bit faster.
|1.||9-feb-14||Lokoloop (5/6)||Zeewolde||10km||39:20 [u]
- 16-mrt-14 – TVH Duathlon, Hilversum
- 29-mrt-14 – Openingswedstrijd, Papendrecht (5000m)
- 12-apr-14 – Powerman Horst (EK Sprint)
- 6-mei-14 – Zomeravondcup 2, Utrecht
- 21-mei-14 – Zomeravondcup 3, Utrecht
- 9-jun-14 – Triathlon Woerden (1/8e)
- 30-aug-14 – Run Bike Run Borne
- ? okt-14 – Cromwijckloop, Woerden
- ? nov-14 – Run Rondje Rhenoy, Beesd
- 31-dec-14 – Sylvestercross, Soest
dikgedrukt is een PR
While preparing my presentation I discovered that boosting with wildcards wasn’t working. I kind of promised to blog about it, so here it is
Last thursday I gave a talk about elasticsearch on the Dutch Java User Group conference (JFall) called “Full text search met ElasticSearch in de praktijk”. Yes it’s in Dutch but I still want to share it with you, it might contain some useful tips and tricks.
Currently I’m using a small dataset (about 3500 records) on ElasticSearch and saw some strange scoring. Hits that should have exactly the same score had _almost_ the same score. Almost the same is kind of a problem since we sort our data on score and name. After some researching it appeared sharding was the issue here. With only one shard the problem is solved. If you want to know how I found out and what alternatives you have please stay tuned.
updated @ Sep 13: Zachary Tong pointed me to an article with a much better solution (read: the right solution ). I added the second to last paragraph to explain it.
A few weeks ago I solved an issue with ElasticSearch where some search results with diacritics didn’t show up in the results. At least, I thought I did. There are quite a few places where it can go wrong. In this article I’ll explain these places and how to fix the issues.