[
https://issues.apache.org/jira/browse/OLIO-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757485#action_12757485
]
Akara Sucharitakul commented on OLIO-11:
----------------------------------------
This is a rather difficult one to fix. First off, the loader and the driver are
related. The loader loads the data with the same relationship as the driver
expects them. So the ScaleFactor (that sets the rules and relationships between
objects in the database for both the loader and driver). Furthermore, the
loader depends on some Faban libraries. So it won't run without. Given this
fact, we can probably provide a script to run the loader without needing a
Faban install, but we'd at least need to have the Faban libraries available on
the target system. Please respond back to let me know what you think about
just providing a script. Thanks.
> Seperate db and file loaders from the driver code and move them up
> ------------------------------------------------------------------
>
> Key: OLIO-11
> URL: https://issues.apache.org/jira/browse/OLIO-11
> Project: Olio
> Issue Type: Improvement
> Components: generic
> Environment: generic
> Reporter: Shanti Subramanyam
> Assignee: Kim LiChong
> Priority: Minor
>
> Currently, the dbloader and fileloader code is buried within the driver jar.
> The problem with this is that even if someone doesn't care to run the driver,
> they still need to install faban and deploy the driver. This also means there
> are separate copies of the loaders for each implementation. By moving the
> loaders out of the driver heirarchy (directly under trunk), they can be
> packaged either seperately or with the application and be shared by the
> implementations.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
