how many version of okapi do you maintain?

[Jim Hargrave]

Curious how many versions of okapi you all maintain currently. How do you migrate customers off of older versions? The main issue for customers is if they see a change in TM exact matches (because of tag or other filter changes) they freak out. Understandable, but it's a hard to tell engineering they have to keep all okapi versions and support them.

I remember being the WordServer admin in my previous job and when they had a filter upgrade (roughly annually) that expected you to bite the bullet and update your TM. My memory is vague but I don't think WS kept old filter versions around very long, if at all.

Jim

[Chase Tingley]

Starting in reverse order -- in the older versions of WorldServer (before they started embedding the SDL Studio filters), they never kept old versions of the filter around.  However they didn't need to, because the contract of those versions of WorldServer was that the filters always had to be able to reconstruct the original document entirely from the segment data.  In other words, they captured the skeleton during extraction.  It was also a requirement that if you updated a filter, it had to be able to merge and export files that had been extracted based on previous versions of its own code, just from processing the skeleton.  

This was sort of messy to implement, however it did mean that WorldServer avoided the issue Okapi has.  Since we don't store the skeleton, we need to regenerate it during merge by re-parsing the original file, and that means that the code we extract with and the code we merge with has to be aligned.

To answer your original question, the answer is quite a few.  Most are rarely if ever used, however they're there in case somebody decides they need to re-export a file from long in the past.

--
You received this message because you are subscribed to the Google Groups "okapi-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to okapi-devel...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/okapi-devel/3fb3ae60-85de-43d0-aa89-f8ef5c0a2b22%40gmail.com.

[Jim Hargrave]

Thanks Chase. Now I remember the WorldServer mantra "skeleton+TM=document". But I remember we still had issues during upgrade.

I know we have discussed this to death and even had a complex skeleton Jackson serialization format at one point that mostly worked. But it would have been a bear to maintain - probably more difficult as juggling multiple filter versions. I've heard others have found a way to save skeleton objects to avoid needed multiple filter versions.

Fortunately many filters don't change enough to pose many issues. The real problem as I mentioned is TM. We are wondering if we could use AI to transform the TM mismatches on the fly. Sort of a smart TM leverage match repair.

Jim

To view this discussion visit https://groups.google.com/d/msgid/okapi-devel/CAGRYq4jOWAHb7%2Bf1t%2B_CDUM8dvW7t63%3D%2B-oRW6yRnHUPd3JLxQ%40mail.gmail.com.