[OPEN-ILS-DEV] 2.6 to 2.7 upgrade records re-ingest?

[Ben Shum]

Actually, I take it back.  There appears to have been a missed
reingest needed to combat an ingest function that was repaired during
2.6.3's time.

We're going to coordinate some new maintenance releases shortly, and
this will be reflected then.

-- Ben

On Tue, Feb 3, 2015 at 3:31 PM, Ben Shum <bshum at biblio.org> wrote:
> Hi Jesse,
>
> Surprisingly enough, I just went back through the upgrade scripts so
> far from 2.6 to 2.7, and I cannot find anything that explicitly
> requires a reingest action.  Which is probably why there's no mention
> of it in the existing upgrade scripts or instructions.
>
> That said, I usually recommend that between major versions it does not
> hurt to use the opportunity (and the downtime you're probably using to
> perform the upgrade anyways) to check all your indexing and see if you
> require any adjustments and changes that might require a good clean
> reingest.
>
> -- Ben
>
> On Tue, Feb 3, 2015 at 2:57 PM, Jesse McCarty <jessem at burlingtonwa.gov> wrote:
>> Hello All,
>>
>>
>>
>> I have recently upgraded a test server from 2.6.3 to 2.7.2 and with the
>> database upgrades there was no prompt for a records re-ingest. I remember
>> upgrades to 2.4 required the re-ingest and so did the upgrade to 2.5/2.6.
>> Does the upgrade from 2.6 to 2.7 not require the re-ingest or is there a bug
>> in the upgrade scripts?
>>
>>
>>
>> Thanks,
>>
>>
>>
>> Jesse McCarty
>>
>> City of Burlington
>>
>> IT Technical Assistant
>>
>>
>
>
>
> --
> Benjamin Shum
> Evergreen Systems Manager
> Bibliomation, Inc.
> 24 Wooster Ave.
> Waterbury, CT 06708
> 203-577-4070, ext. 113



-- 
Benjamin Shum
Evergreen Systems Manager
Bibliomation, Inc.
24 Wooster Ave.
Waterbury, CT 06708
203-577-4070, ext. 113