Two minor issues regarding repository access
I am just starting to use RapidAnalytics so I discover some things. Please forgive me for opening some topics, but there are also some issues that you might want to take care of.
The first one is the browse functionality offered by RapidMiner. Both views "Repositories" and "Remote Processes" contain a button to open the web interface inside a browser window. But clicking it results in (IP address intentionally removed)
Exception: java.io.IOExceptionThe "Show Log" button from "Remote Processes" view works fine. There just seems to be a single slash missing after the server's address/port: http://x.x.x.x:8080RA/
Message: Failed to open http://x.x.x.x:8080RA/faces/restricted/browse.xhtml?location=%2Fpublic%2Ftest%2FURLCombiner. Error message: Falscher Parameter.
The second issue is not really an issue but a little contradiction between manual and reality. The manual states (page 15)
Note that RapidMiner automatically inserted ../data/Labor-Negotiations as the
repository entry parameter of the Retrieve operator or into the process context. This
is a relative addressing of the repository entry: The sequence .. navigates one folder up
(from the processes folder). This is a practice you should always use for two reasons:
- You can move around folders without destroying functionality.
- RapidAnalytics can resolve them properly. Do not use the absolute repository
name in the repository location (e.g. as //RapidAnalytics/home/data) because
RapidAnalytics is an alias that only exists on your client. RapidAnalytics does
not know that you are referencing it under this name in RapidMiner (you could,
e.g., have several RapidAnalytics instances connected), and hence cannot resolve
this name. You can, however, use absolute locations without the leading repository
reference //RapidAnalytics, i.e., only the part /home/simon/data/Labor-nego-
But when setting repository locations with the location chooser absolute references like //RapidAnalytics/... are inserted. This of course makes them not working on the server, if they are not manually corrected (root element has to be removed as noted in the manual extract above). If locations were set as promised by the manual, things might be a bit more comfortable. This is not critical but I think you might like some coherence between manual and software.