OK. We have to change the state back and just mark it done for PHP.
As for the old loader, yes we can get rid of it. We can also take that
action as part of the same jira. Will do.
-Akara
Shanti Subramanyam wrote:
Akara,
This is great. Is there a reason to keep this file loader separate from
the older one ?
Once we integrate the 3 loaders (java,php,rails) we will also need to
change the java and rails implementations to use the new directory
structure right ? As such OLIO-40 is not fully resolved yet (it is
marked as generic).
Shanti
Akara Sucharitakul (JIRA) wrote:
[
https://issues.apache.org/jira/browse/OLIO-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akara Sucharitakul resolved OLIO-40.
------------------------------------
Resolution: Fixed
Fix tested resulting in clean runs. Issue considered resolved.
File loader is slow. Filestore architecture is problematic
----------------------------------------------------------
Key: OLIO-40
URL: https://issues.apache.org/jira/browse/OLIO-40
Project: Olio
Issue Type: Improvement
Components: generic
Affects Versions: 0.1
Reporter: Shanti Subramanyam
Assignee: Akara Sucharitakul
Fix For: 0.2
As we scale up the number of users, the fileloader takes longer and
longer to load the filestore. Further, the loader clutters the faban
log with lots of messages marking it's progress. The frequency of
these msgs need to be reduced.
In addition, the current filestore design of a single directory to
hold all the files is proving to be difficult to manage. It is
impossible to even do an 'ls' in the directory as the number of files
is large at scales beyond a few thousand users. A well-defined
directory hierarchy should be used to make access more reasonable.
