Solr 3.5 er sluppet

I dag ble en ny versjon av Apache Solr sluppet, nemlig versjon 3.5.0. Her er kunngjøringen fra Lucene PMC: The Lucene PMC is pleased to announce the release of Apache Solr 3.5.0! See the CHANGES.txt file included with the release for a full list of details. Solr 3.5.0 Release Highlights: Bug fixes and improvements from Apache

Solr 3.5 released

Today a new version of Apache Solr was released, version 3.5.0. Here’s the release statement from the Lucene PMC: The Lucene PMC is pleased to announce the release of Apache Solr 3.5.0! See the CHANGES.txt file included with the release for a full list of details. Solr 3.5.0 Release Highlights: Bug fixes and improvements from Apache

Discover CommitWithin in Solr

You may have been using Apache Solr for some time, and you all know that you have to do a <commit/> in order for the <add>ed content to become indexed. But what commit strategy should you choose? Many rely on the explicit commit from the client, or perhaps AutoCommit in solrconfig.xml. Explicit commits leaves all the responsibility to the client and you soon end up with too frequent/unnecessary commits (causing resource waste) or too few commits.

Sure, we have AutoCommit, where clients don’t need to think about committing, but then it gets less flexible; What if you sometimes want to index in larger batches, while other times you need low latency?

Discover CommitWithin! CommitWithin is a commit strategy introduced in Solr 1.4, which lets the client ask Solr to make sure this <add> request gets committed within a certain time. This leaves the control of when to do the commit to Solr itself, optimizing number of commits to a minimum while still fulfilling the update latency requirements. If I send an <add commitWithin=10000> (in an XML update), that tells Solr to make sure the document gets committed within 10000ms, i.e. 10s. You can then continue to add other documents, and Solr will automatically do a <commit> when the oldest <add> is due.

MacOS X Lion har fortsatt noen barnesykdommer

Etter å ha oppgradert til Lion denne uka fikk jeg flere problemer, selv om jeg kjører 10.7.1. Tenkte jeg ville dele de – og løsningene med dere.

Badeball på login-skjermen

Jeg kjøpte en ny SSD disk og kjørte en helt ren installering av Lion. Men selv før jeg lastet inn filer fra backupdisken, fikk jeg trøbbel med badeball (snurrende farget musepeker) på innloggings-skjermen. Noen ganger gikk den rett til “blåskjerm” med behov for hard reset.

Løsningen fant jeg bl.a. her, kort fortalt må du kjappe deg med å logge inn før maskina henger (eller logge inn i Sikker Modus ved å holde SKIFT ved oppstart), åpne Energisparings-valgpanelet, og skru av automatisk veksling mellom grafikk-kort. Dette løste mitt problem.