Luc Boudreau this week announced plans to take olap4j to version 1.0.

It is four years since I released the draft of the olap4j API. People have joked that olap4j, like google mail, has been in “perpetual beta” since then. But olap4j’s maturity belies its humble version number. It has been in use by production applications, is the foundation of several OLAP clients, and there are at least two drivers. (Mondrian’s primary interface is its olap4j driver, and the XMLA driver has variants for Mondrian, Microsoft Analysis Services and SAP BW.)

In software development (and particularly open source) culture, version 1.0 of an API is a symbolic milestone. It means that the API is stable, well tested, and will not be changed except at a major release, and then only with due consultation. So, version 1.0 of olap4j will be something to celebrate, but before then, we need to undertake a review of what is in the API.

Some parts of olap4j (such as the query model, advanced drill through, cell write back and notifications) are still under active development, and it is not in anyone’s interests to freeze these parts of the API just yet. So, sections such as these will be marked ‘experimental’, and likely to change (with consultation of the community, as usual) in future.

Whether you are an olap4j developer, part of the existing olap4j user community, or are just interested in using OLAP from within the Java without being tied to a particular vendor’s API, please get involved in the review process.