[Mondrian] RE: Eigenbase perforce change 11171 for review

[John V. Sichi]

Julian Hyde wrote:
> I can understand why you want that behavior, but I don't think it's useful
> to anyone besides LucidEra. As such, it shouldn't be in the Connection
> interface. Can you think of a way to get it out of the public API? Maybe you
> could add a parser or validator factory, and access it via a new connect
> string parameter.

For now, what if we just delete it from the interface (and then we'll 
downcast to ConnectionBase before calling it)?  Clumsy, but see below 
about moving to olap4j in the long term.

This seems to be in line with eigenchanges 11094 and 11139, where I see 
classes being made public without any actual references outside of the 
package, which I assume means they aren't useful to anyone but Pentaho?

> If you simply want to use the parser for validation purposes, you might
> consider using olap4j's parser & validator. The goals of the olap4j parser
> are to be extensible to handle a variety of mdx dialects, and to work in
> client environments with minimal dependencies, so it might be better for
> these purposes.

Yes, LucidEra needs to move to olap4j anyway since long-term the classic 
API is deprecated.  I've asked Rushan to take a look at how it can 
support the calc metric use cases and whether enhancements will be 
needed there.

JVS