mkambol at gmail.com
Tue May 19 17:37:46 EDT 2009
Thanks Julian. I've added
*BTW- I made a typo in the title for the bug but could find no way to edit
it after the fact. Is there any way you are aware of?
On Tue, May 19, 2009 at 4:19 PM, Julian Hyde <jhyde at pentaho.com> wrote:
> PS See also http://jira.pentaho.com/browse/MONDRIAN-496 and related issue
> http://jira.pentaho.com/browse/MONDRIAN-557. It's possibly that these are
> causing extra work to be done at schema load time.
> *From:* Julian Hyde [mailto:jhyde at pentaho.com]
> *Sent:* Tuesday, May 19, 2009 1:00 PM
> *To:* 'Mondrian developer mailing list'
> *Subject:* RE: [Mondrian] Pool.get()
> I don't know if there would be integrity issues if two users were using
> the same URL but ended up with different schema objects. Obviously it would
> be inefficient: each schema would have its own cache.
> The ideal behavior would be for user B to wait if it needs the same schema
> that A is currently loading. But if C comes along and wants a different
> schema, there should be a very short critical section where the system
> figures out that the schema does not exist and needs to be loaded.
> Can you please log a bug for this issue?
> Mondrian mailing list
> Mondrian at pentaho.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mondrian