This is the first release bringing Lucene and Solr release versions in sync. There are numerous bug fixes, optimizations and new features. Download from here
I had been holding out on buying a more internet friendly phone for some time now, waiting for 3G service to start in India. After my iPad experience, it was clear to me that I couldn’t be happy with an iPhone but it was also obvious that none of the available Android phones were good enough.
Enter the new Samsung Galaxy S with Android 2.1, awesome 4” display, light weight and a good (enough) battery life. A little market research showed that Samsung’s Super AMOLED technology was best in class and a better phone, the Samsung Galaxy S2, will only be available next year. With 3G to be introduced (supposedly) around October, the stage was set. So, one fine July evening, I bought the Samsung Galaxy S.
First of all, a message to people who are surprised upon hearing the price - the Samsung Galaxy S is not a phone; it is a pocket sized computer that also happens to be a phone. And what have I been upto with this device? Here’s a list of ten things (in no particular order) that I have used it to:
- Get email alerts via K9 Mail, read blogs, check twitter, buzz and facebook feeds
- Take photographs and upload it to Facebook (darn you Airtel, I could never get MMS to work properly)
- Watch movies on my desktop monitor and phone through VLC Remote and Gmote.
- Stream music from GrooveShark - Yay! freedom from syncing my music
- Play Asphalt5 while sitting at the back of an autorickshaw - something ironic about it.
- Use AIM to answer questions from our QA team while having lunch. Note to myself, use a spoon next time if you want to use the phone.
- SMS while walking down the road without the fear of banging into an obstacle.
- Read a book on the Kindle app.
- Navigate to Kolar and back with Google Maps
- Impress people with the live wallpapers, gesture search and some not so useful tidbits such as a lie detector and a sky map.
Google integration means that all my contacts are backed up on their servers. I am still surprised that something as simple as backing up contacts has been so hard for phones till now. Another cool feature that I loved was that I could link phone numbers with Facebook contacts together. Now when a friend calls, I see his Facebook photo automatically. The device has a decent battery life; with on and off wifi use, it lasts for a little more than a day. The device has a 5 megapixel camera and can record a 720p video. And, by the way, flash sites works too.
Before I bought the phone, I wasn’t sure how easy it would be to use a touch keyboard. Well, it wasn’t too hard with the default keyboard but ever since I switched to the Swype keyboard, I’m insanely fast. I’d recommend Swype to everybody. Good thing that Samsung provides this keyboard application for free.
There are a few downsides though. The phone feels sluggish when more than a couple of applications are running. The “Advanced Task Killer” application is essential for a decent experience. There is no flash light so one must depend on external light source being available to avoid dark photos. Sometimes (and this happens rarely), after moving out of a wifi zone, it won’t automatically switch to a GPRS/EDGE connection unless I restart the phone.
All in all, I’m happy with the device and eagerly waiting for an Android 2.2 (froyo) upgrade and Airtel’s 3G service.
From the mailing list announcement:
Apache Solr 1.4.1 has been released and is now available for public
Solr 1.4.1 is a bug fix release. See the change log for more details.
Now that I have had the chance to play with the Apple iPad, I thought I’d put down some observations and opinions about the device. I know that I’m late to the party but hey, they don’t sell these devices here in India.
First of all, I love that I do not have to sit before a desk to use this. There is a real need in the world for a device like this and even though many have tried in the past, hats off to Apple for pulling this off. No company other than Apple, without its army of fan boys, would have been able to make this kind of a product successful. But now that Apple has, we can all expect that the new shiny competing devices will be able to do at least as much as what the iPad does. So, thank you Apple!
The model that I have tried is the 32GB iPad. The device is slim, the touch experience is intuitive and the display is sharp. It is great as a browsing device. I guess it would have been easier to use if it were a little more lighter - which is not too much to expect from later versions. The dimensions at 9.56 x 7.47 inches feels a little too big at times. A 7-8 inches display may be more handy.
Typing on the touch keyboard takes a little getting used to but practice makes perfect. Still, without my favorite set of browser plugins, I find it hard to share stuff on twitter/buzz. I guess the iPad is designed for people who are mostly consumers of data rather than creators. The device does not have a USB port which is a bummer. A Linux user like me cannot transfer songs or movies from my laptop to the device because one must use iTunes. I had to borrow a friend’s laptop to use Windows(!) so that I can transfer some media into the device. But to do that, you need to convert your divx media to the format iPad can play. The App Store is not open to anyone outside the US so I couldn’t use it.
As a geek, one gets bored with the device very soon. There’s just too many things that I want to do with it but am not able to because Apple won’t let me. I am looking forward to the Samsung Android based tablet which is supposed to be coming out in Q3. No one can beat Apple in the wow factor category but I am hoping that the Android devices may allow me to do much more.
[Update] - I used the excellent Handbrake application to convert between media formats and I’d highly recommend it.
[Update 2] - An interesting discussion on Google Buzz on this topic.
Apache Mahout 0.3 has been released. Apache Mahout is a project which attempts to make machine learning both scalable and accessible. It is a sub-project of the excellent Apache Lucene project which provides open source search software.
From the project website:
The Apache Lucene project is pleased to announce the release of Apache Mahout 0.3. Highlights include:
- New: math and collections modules based on the high performance Colt library
- Faster Frequent Pattern Growth(FPGrowth) using FP-bonsai pruning
- Parallel Dirichlet process clustering (model-based clustering algorithm)
- Parallel co-occurrence based recommender
- Parallel text document to vector conversion using LLR based ngram generation
- Parallel Lanczos SVD (Singular Value Decomposition) solver
- Shell scripts for easier running of algorithms, utilities and examples
.. and much much more: code cleanup, many bug fixes and performance improvements
Congratulations and thanks to all Mahout developers!
A couple of weeks back, Apache Lucene Committer and PMC member, Michael McCandless started a discussion on factoring out a shared, standalone Analysis package for Lucene, Solr and Nutch. During the discussions, Yonik Seeley, Solr Creator, proposed merging the development of Lucene and Solr. After intense discussions and multiple rounds of voting, the following changes are being put into effect:
- Merging the developer mailing lists into a single list.
- Merging the set of committers.
- When any change is committed (to a module that “belongs to” Solr or to Lucene), all tests must pass.
- Release details will be decided by dev community, but, Lucene may release without Solr.
- Modularize the sources: pull things out of Lucene’s core (break out query parser, move all core queries & analyzers under their contrib counterparts), pull things out of Solr’s core (analyzers, queries).
The following things do not change:
- Besides modularizing (above), the source code would remain factored into separate dirs/modules the way it is now.
- Issue tracking remains separate (SOLR-XXX and LUCENE-XXX issues).
- User’s lists remain separate.
- Web sites remain separate.
- Release artifacts/jars remain separate.
So what does it mean for Lucene/Solr users? Nothing much, really. Except that you should see tighter co-ordination between Lucene and Solr development. New Lucene features should reach Solr faster and releases should be more frequent. Solr features may also be made available to Lucene users who do not want to setup Solr use the RESTy APIs.
Already, Solr has been upgraded to use Lucene trunk (in branches/solr) and should soon become the new Solr trunk. There is talk of re-organizing the source structure to better fit the new model. Things are moving fast!
Personally, I feel that this merge is a good thing for both Lucene and Solr:
- Solr users get the latest Lucene improvements faster and releases get streamlined.
- Lucene users get access to Solr features such as faceting.
- The in-sync trunk allows new features to make their way into the right place (Lucene vs Solr) more easily and duplication is minimized.
- Bugs are caught earlier by the huge combined test suite.
- More number of committers means more ideas and hands available to the projects
- Other Lucene based projects can benefit too because many Solr features will be made available through Java APIs.
There are a couple of things to be worked out. For example, we need to decide where the integrated sources should live and whether or not to sync Solr’s version with Lucene’s. All this will take some time but I am confident that our combined community will manage the transition well.
Congratulations to the Apache Lucene team on releasing Lucene Java 3.0.1 and 2.9.2. Both of these are bug fix releases and are backwards compatible with Lucene Java 3.0.0 and 2.9.1 respectively.
From the official announcement:
Hello Lucene users,
On behalf of the Lucene development community I would like to announce the release of Lucene Java versions 3.0.1 and 2.9.2:
Both releases fix bugs in the previous versions:
- 2.9.2 is a bugfix release for the Lucene Java 2.x series, based on Java 1.4
- 3.0.1 has the same bug fix level but is for the Lucene Java 3.x series, based on Java 5
New users of Lucene are advised to use version 3.0.1 for new developments, because it has a clean, type-safe API.
Important improvements in these releases include:
- An increased maximum number of unique terms in each index segment.
- Fixed experimental CustomScoreQuery to respect per-segment search. This introduced an API change!
- Important fixes to IndexWriter: a commit() thread-safety issue, lost document deletes in near real-time indexing.
- Bugfixes for Contrib’s Analyzers package.
- Restoration of some public methods that were lost during deprecation removal.
- The new Attribute-based TokenStream API now works correctly with different class loaders.
Both releases are fully compatible with the corresponding previous versions. We strongly recommend upgrading to 2.9.2 if you are using 2.9.1 or 2.9.0; and to 3.0.1 if you are using 3.0.0.
See core changes at:
and contrib changes at:
Binary and source distributions are available at http://www.apache.org/dyn/closer.cgi/lucene/java/
Lucene artifacts are also available in the Maven2 repository at http://repo1.maven.org/maven2/org/apache/lucene/
According to a blog post from Microsoft Distinguished Engineer and CTO, FAST Bjørn Olstad, the 2010 products will be the last to have a search core that runs on Linux and UNIX.
Being involved in Apache Solr and the newly formed Lucene Connectors Framework (LCF) project, I’m very interested in the implications. Undoubtedly, at least some FAST customers will not be happy with this decision and will want to switch to something which can still run on Linux/UNIX.
I believe that this is a great opportunity for the Apache Solr/LCF combo. Perhaps, the newly proposed Apache Spatial Information Systems (SIS) will help as well. Of course, this is big news for Lucid Imagination, Sematext and other companies as well who offer consultancy, training and support for Lucene/Solr.
I’d like to ask people who have used FAST in the past, what would it take for Lucene/Solr/LCF to fill the gap?
Well, the cat is out of the bag. I’ve been working with Otis on Solr In Action. We’re looking for a couple of contributors to write case studies for the book describing how they have used Solr. Otis just posted this to his blog and to the Solr mailing list as well.
So, if you are are using Apache Solr in some clever, interesting or unusual way, or deal with large indexes or large number of cores or distributed search and are willing to share this information with the world, please get in touch. We are looking for between five to ten pages (soft limits) per case study.
You can contact either me or Otis by leaving a comment on this post with your contact info or contact @shalinmangar or @otisg on Twitter or email me on shalin at apache and we’ll get back to you right away.
It’d be great if you can share this message around too.