We do not deploy PVDBs to Teiid at startup. They are only deployed when a preview is
requested. The PVDBs are created locally on the client whenever a project is opened. So at
startup they would be created on the client if they don't currently exist.
----- Original Message -----
So, I spoke with Ramesh offline this morning about option 3, and it
looks like it's a no-go since all deployed PVDBs for all users would
always be in the server's memory even if not being worked on. We
talked about a solution to for this involving dynamically loading them
only when accessed (assuming they're initially stored in some other
folder besides the deploy folder), but they weren't interested in
doing that. However, after agreeing that the server needs to provide
an async way to initiate cleanup, we all agreed that there doesn't
seem to be any reason for the Designer to create/deploy PVDB at
startup either.
Can anyone shed some light on why we do this (or better yet, confirm
that we don't currently do this)?
On Jan 28, 2011, at 8:32 AM, Ramesh Reddy wrote:
Yes, it is possible. The threading needs to be in server side to make
it
work.
Ramesh..
On Fri, 2011-01-28 at 08:26 -0500, John Doyle wrote:
I also agree that we should eliminate the timer. We're making an
assumptions about the user's preference there.
Ramesh, would be possible to implement the delete such that it just
flags the VDB and DS for delete and returns, then the delete is
actually performed on another thread? I can't imagine there's much
corrective action someone is going to take through the admin API in
the event that Delete fails.
~jd
JPAV
_______________________________________________
teiid-designer-dev mailing list
teiid-designer-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/teiid-designer-dev