You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "Hans Zeller (JIRA)" <ji...@apache.org> on 2016/05/04 18:21:13 UTC

[jira] [Resolved] (TRAFODION-1964) Cannot run SPJs after an trafodion upgrade

     [ https://issues.apache.org/jira/browse/TRAFODION-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hans Zeller resolved TRAFODION-1964.
------------------------------------
    Resolution: Won't Fix

See previous comment.

For end-users, the recommendation is to create libraries with a fully qualified name, outside of the Trafodion install directory. This way, you can upgrade Trafodion without losing access to the library files.


> 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.3.4#6332)