[
https://issues.apache.org/jira/browse/TS-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14091821#comment-14091821
]
Alan M. Carroll commented on TS-2362:
-------------------------------------
Final result -
This change requires no configuration, it should just work. That is, if you
install a version with this change then your old cache should be maintained.
This applies back to version 3.2.0 - and upgrade from that or later version
should preserve the cache.
Note that any cache updates are written in the current format, not the old
format. Over time this should cause a cache to be updated to the newest
version. Because this is now tracked per object, the cost of backwards
compatibility should diminish over time as new objects are updated and the
compatibility logic can easily detect that to be the case.
I incorporated the TS-2564. Previously this fix had been left on the 4.2.X
branch because (since 5.0 had a different cache version) it wasn't needed.
However, as this enables using 4.2.X caches of all formats we must be able to
do that fix up as well. Again, as per above, while the fixup will be done on
all objects, new/updatd objects will skip the fixup because the object being
permanently fixed is now trivial to detect.
> Backwards cache compatibility for 4.X (read 3.2)
> ------------------------------------------------
>
> Key: TS-2362
> URL: https://issues.apache.org/jira/browse/TS-2362
> Project: Traffic Server
> Issue Type: Improvement
> Components: Cache
> Reporter: Alan M. Carroll
> Assignee: Alan M. Carroll
> Labels: Review
> Fix For: 5.1.0
>
> Attachments: ts-2362.diff
>
>
> Enable the 4.X series to be able to read 3.2 caches.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
