[
https://issues.apache.org/jira/browse/TRAFODION-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hans Zeller reopened TRAFODION-1964:
------------------------------------
Sorry, I misunderstood Venkat's bug description. The key is that he said the
_system_ SPJs. I was thinking of regular user SPJs, which are also often put
under $TRAF_HOME. We do need to keep track of the system SPJs, and I should not
have closed this JIRA.
> Cannot run SPJs after an trafodion upgrade
> -------------------------------------------
>
> Key: TRAFODION-1964
> URL: https://issues.apache.org/jira/browse/TRAFODION-1964
> Project: Apache Trafodion
> Issue Type: Bug
> Reporter: Venkat Muthuswamy
> Assignee: Hans Zeller
>
> The system and user SPJ jar files are now stored under
> $MY_SQROOT/udr/lib/<user>.
> The CREATE LIBRARY/ALTER LIBRARY commands use the fully qualified linux
> directory paths (the environment variables are expanded).
> For example, if current trafodion build is installed under
> /home/trafodion/build1, the files are stored under
> /home/trafodion/build1/udr/lib/user1
> When the user upgrades and installs a new build, let's say trafodion is
> installed under /home/trafodion/build2.
> If the user removes this old trafodion installation, the libraries and SPJs
> defined using build1 no longer work, because the UDR tries to load the jar
> file from /home/trafodion/build1/udr/lib/user1 folder because that's what is
> stored in the metadata.
> Even if the folder exists, any system created library would be pointing to an
> older version of the jar file even though the new install might include fixes
> to the system library jar.
> 1. Can the CREATE and ALTER LIBRARY commands use relative paths to something
> like $MY_UDR_ROOT and not required the fully qualified paths?
> 2. Can the UDR runtime be modified to look at the relative paths $MY_UDR_ROOT.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
