I know Lucene / Solr 4.6.1 just came out, but 4.7 is right around the corner. We already have loads of goodies stacked up. A brief tour of some of my favorites...
Development support for the netbeans IDE
A Kurdish analyzer.
A very sweet, very straightforward new simple queryparser: https://issues.apache.org/jira/browse/LUCENE-5336
Proper support for NearRealTime with alternate file systems like NFS and HDFS.
Plus a ton of other features, optimizations, and bug fixes.
All the goodness of Lucene 4.7.
A variety of great feature additions and improvements like support for Lucene's FreeTextSuggester (http://blog.mikemccandless.com/2014/01/finding-long-tail-suggestions-using.html) , multi-level compositeId routing (http://searchhub.org/2014/01/06/10590/), and a new migrate command for splitting collections (https://issues.apache.org/jira/browse/SOLR-5308).
A new contrib module for building indexes with Hadoop's mapreduce. https://plus.google.com/+MarkMillerMan/posts/64y2ZkF42wp
A new cursor api for efficient 'deep paging'. http://searchhub.org/2013/12/12/coming-soon-to-solr-efficient-cursor-based-iteration-of-large-result-sets/
Support for SolrCloud over SSL.
A sweet new Suggest API that is a much nicer more capable replacement for what we had. https://issues.apache.org/jira/browse/SOLR-5378
Plus many other features and a ton of bug fixes and optimizations.
Hot on the heels of 4.6.1, 4.7 is going to be a pretty nice release.
+1 to everything Mark has said.
Hardening SolrCloud is the hardest thing I have ever faced, and honestly, I have spent just crazy amounts of time on it. My work on Lucene, Solr, and SolrCloud is really the largest thing of consequence I have dropped into the world and I would be crushed if each did not see some level of success in the coming years. This is where I am putting my 10,000 hours of engaged work.
There is a light at the end of the tunnel though. As Solr users have started migrating to SolrCloud in mass, feedback and bug reports have surged. Teams are banging on the system and reporting back detailed reports around where things went wrong. This is the life blood of a hardened system. Lots of users, lots of environments, lots of testing, lots of feedback.
SolrCloud had a large early advantage in user base because the Solr community was so strong and so large - but in the early days, of course, it mainly was used by early adopters and there are never as many of those as you would like. That was a critical phase, and many of those early adopters were invaluable. Recently, we have moved beyond that though. People picking up Solr are now starting with SolrCloud. Many older Solr users are migrating when they update to recent versions. Use is jumping drastically, and the results of this use on the code are helping me to smile again.
It's hard to be happy in the early days of a distributed system. All you see are the known flaws, the things you meant to get to, the tests you know should have been written but have not been yet. Building a distributed system is just a lot of grunt work - a marathon of pushing boulders up a hill. You spend more time bug fixing and debugging than you do coding. Now that SolrCloud is starting to transition beyond that phase, it's easier to start feeling less critical. No doubt there is a lot to do, but the underpinnings are starting to really firm up. And there is no better feeling.
If you tried SolrCloud in the early days and ran into issues, I really encourage you to take another look at 4.6.1 when it comes out in a few days. Sure, there is a lot we still have planned, some rough edges in different spots, plenty of improvements and additions coming - but what is there is starting to look and behave pretty nicely. In my opinion, the future for Solr and SolrCloud is looking bright.
- JSS Academy of Technical Education, NoidaInformation Technology, 2003 - 2007
- St. Joseph's College, AllahabadHigh School, 1988 - 2002
- LucidWorksEngineer, 2012 - present
- AOLPrincipal Software Engineer, 2007 - 2012
- Onyomo.comIntern, 2006 - 2006
The Netflix Tech Blog: The Netflix Dynamic Scripting Platform
At the core of the redesign is a Dynamic Scripting Platform which provides us the ability to inject code into a running Java application at
Gold Fix Study Shows Signs of Decade of Bank Manipulation
The London gold fix, the benchmark used by miners, jewelers and central banks to value the metal, may have been manipulated for a decade by
Ken Shirriff's blog: Bitcoin mining the hard way: the algorithms, protoc...
This article explains Bitcoin mining in details, right down to the hex data and network traffic. If you've ever wondered what really happens
Which Algorithms Really Matter? – Guidelines for How to Choose the Right...
Ted Dunning, MapR's Chief Applications Architect, recently presented an invited talk titled "Which Algorithms Really Matter?" at the CIKM co
Jailed whistle-blowers to Edward Snowden: Don't come home | Al Jazeera...
What happens to whistle-blowers after the whistle is blown
How a Radical New Teaching Method Could Unleash a Generation of Geniuses...
Students in Matamoros, Mexico weren't getting much out of school -- until a radical new teaching method unlocked their potential.
What Did the Continents Look Like Millions of Years Ago?
An artist-geologist renders the history of the Earth with maps.
Aadhaar and the myth of lack of identity - Moneylife
What is needed today to solve the problems of the poor is not so much esoteric technology but first and foremost clear logic as to where the
They’re Taking Over! by Tim Flannery | The New York Review of Books
It's become fashionable to keep jellyfish in aquariums. Behind glass they can be hypnotically beautiful and immensely relaxing to watch. Unl
What DNA Testing Reveals About India’s Caste System | TIME.com
Kumarasamy Thangaraj traveled 840 miles (1,350 km) off of the eastern coast of India by plane, then ship, then six hours by car, then ship a