Bug 182296 Crosstab - non-numeric measures
Feature request. Looking at the 2.2.M6 release, it seems that measures (the fields that can be in the matrix part of the output) need to be numeric. I looked at the spec documents and it seems there is no requirement for non-numeric measures
data/org.eclipse.birt.data/src/org/eclipse/birt/data/engine/olap/data/impl/dimension/Hierarchy.java
import org.eclipse.birt.data.engine.core.DataException;
import org.eclipse.birt.data.engine.i18n.ResourceConstants;
import org.eclipse.birt.data.engine.olap.api.cube.IDatasetIterator;
import org.eclipse.birt.data.engine.olap.api.cube.IHierarchy;
import org.eclipse.birt.data.engine.olap.api.cube.ILevelDefn;
import org.eclipse.birt.data.engine.olap.data.api.ILevel;
import org.eclipse.birt.data.engine.olap.data.document.DocumentObjectUtil;
import org.eclipse.birt.data.engine.olap.data.document.IDocumentManager;
import org.eclipse.birt.data.engine.olap.data.document.IDocumentObject;
import org.eclipse.birt.data.engine.olap.data.impl.Constants;
import org.eclipse.birt.data.engine.olap.data.impl.NamingUtil;
import org.eclipse.birt.data.engine.olap.data.util.BufferedStructureArray;
import org.eclipse.birt.data.engine.olap.data.util.DiskIndex;
import org.eclipse.birt.data.engine.olap.data.util.DiskSortedStack;
import org.eclipse.birt.data.engine.olap.data.util.IDiskArray;
import org.eclipse.birt.data.engine.olap.data.util.IndexKey;
/**
 * Describes a hierarchy. A hierarchy is composed of multi-levels.
 */
public class Hierarchy implements IHierarchy
{
	private IDocumentManager documentManager = null;
	private IDocumentObject documentObj = null;
	private IDocumentObject offsetDocObj = null;
	private Level[] levels = null;
	private String name = null;
	private Map levelMap = new HashMap( );
	
	public Hierarchy( IDocumentManager documentManager, String name )
	{