Mitch Pronschinske

Mitch Pronschinske is the Senior Content Analyst aka. the CZO (Chief Zones Officer) aka. "Lord of the Zones" at DZone. That means he writes and searches for the finest developer content in the land so that you don't have to. He often eats peanut butter and bananas, likes to make his own ringtones, enjoys card and board games, and is married to an underwear model. My G+ Profile Mitch is a DZone Zone Leader and has posted 2016 posts at DZone. You can read more from them at their website. View Full User Profile

The Java 7 - Lucene Bug Controversy: The Story Behind the Story

02.03.2012

| 10527 views |

Talk 4-vimeo 843 copy copy from Lucene Revolution on Vimeo.

Learn about the controversy that emerged in the early days of the Java 7 GA release because of the effect it had on Apache Lucene - from the perspective of Uwe Schindler who blogged about the bug.

The recent release of Java 7 and its testing with Lucene exposed some significant problems with the released Java code. We'll give a brief synopsis of the technical state of play of these issues and tell you what you need to know. (A full accounting of the chronology is available at http://blog.thetaphi.de/2011/07/real-story-behind-java-7-ga-bugs.html).

Download session slides

Tags:

Comments

Tim Garrett replied on Tue, 2012/02/07 - 11:01am

I have not watched this video yet, but I have found several articles and even the headline of this one to be extremely misleading. It is not a "Java 7 Lucene" bug. It is a Java 7 bug. The VM has optimizations which can lead to lack of correctness. It is entirely irrelevant that the Lucene project is the one that suffered from the bugs. It almost seems as if Lucene was selected to be thrown under the bus for Oracle/Sun's own failings--as if enough hand-waving and calling out the Lucene guys as outliers and crazies will make everything right. Java 7 was released with flaws, correctable flaws surely, but it is not a Lucene issue! The VM was not operating to spec!