added a comment -
05/Apr/10 4:22 PM I emailed this to Jessie, but realized I should add it here to model good JIRA behavior, and leave a paper trail on the issue.
So you totally don't need to worry about my seperate rake task for
solrmarc indexing; I thought it might be more convenient to use it, but
sounds like not, it would just less be less convenient. Some day the
two rake tasks should probably be merged to DRY things up, since they
both do essentially the same thing. But that day does not need to be
today. Meanwhile fixing the installation process is obviously a high
priority.
As far as adding the rails environment dependency to the rake task, the
only consequence will be that the rake task will take a lot longer to
start, and possibly take more memory to run, since it essentially loads
the whole Rails application before running. Probably not a big deal,
since this test data index script is going to be run only rarely (on
installation, and if the test data changes).
So you totally don't need to worry about my seperate rake task for
solrmarc indexing; I thought it might be more convenient to use it, but
sounds like not, it would just less be less convenient. Some day the
two rake tasks should probably be merged to DRY things up, since they
both do essentially the same thing. But that day does not need to be
today. Meanwhile fixing the installation process is obviously a high
priority.
As far as adding the rails environment dependency to the rake task, the
only consequence will be that the rake task will take a lot longer to
start, and possibly take more memory to run, since it essentially loads
the whole Rails application before running. Probably not a big deal,
since this test data index script is going to be run only rarely (on
installation, and if the test data changes).