agora inbox for pljava-dev@postgresql.org  
help / color / mirror / Atom feed
[Pljava-dev] classloading
2+ messages / 0 participants
[nested] [flat]

* [Pljava-dev] classloading
@ 2013-02-04 11:51  
  0 siblings, 1 reply; 2+ messages in thread

From:  @ 2013-02-04 11:51 UTC (permalink / raw)

Hi all,

I was looking at pl/java since we're looking at doing something along
those lines for user-defined triggers in Cassandra [1].  Slightly
confused to only see one Loader per Schema.  Does this mean that
reloading jars is not supported?  Curious about the design tradeoffs
there because that sounds like something users would want.

Thanks for any light you can shed here!

[1] https://issues.apache.org/jira/browse/CASSANDRA-1311

-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder, http://www.datastax.com
@spyced



^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* [Pljava-dev] classloading
@ 2013-02-04 17:16  
  parent: 
  0 siblings, 0 replies; 2+ messages in thread

From:  @ 2013-02-04 17:16 UTC (permalink / raw)

Hi Jonathan,

Not sure what you mean with "reloading jars". PL/Java will give you a 
JVM session that is dedicated to your session (i.e. the database 
connection). What classes you have access to is normally something that 
someone with super privileges has decided earlier by installing jars and 
declaring the class paths. Letting normal users do this would IMO be 
dangerous. The same is true for other types of stored procedures and 
functions.

Now, if you indeed do have super user priveliges, then there's nothing 
stopping you from changing the classpath to see different classes at 
different times. There would still be only one loader though (the one 
that uses the database and effective classpath). PL/Java will not allow 
that you load classes directly from the file system.

- thomas

On 2013-02-04 12:51, Jonathan Ellis wrote:
> Hi all,
>
> I was looking at pl/java since we're looking at doing something along
> those lines for user-defined triggers in Cassandra [1].  Slightly
> confused to only see one Loader per Schema.  Does this mean that
> reloading jars is not supported?  Curious about the design tradeoffs
> there because that sounds like something users would want.
>
> Thanks for any light you can shed here!
>
> [1] https://issues.apache.org/jira/browse/CASSANDRA-1311
>




^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2013-02-04 17:16 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2013-02-04 11:51 [Pljava-dev] classloading 
2013-02-04 17:16 ` 

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox