You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2015/05/29 02:36:32 UTC
[jira] [Commented] (TS-3643) TS-2944 changes logging format /
breaks compatibility
[ https://issues.apache.org/jira/browse/TS-3643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14563996#comment-14563996 ]
Leif Hedstrom commented on TS-3643:
-----------------------------------
What do we do with this? Do we want to try to unbreak this in a 5.3.1 ? I'm gonna target this for v5.3.1, and let you duke this out with the RM and the community.
> TS-2944 changes logging format / breaks compatibility
> -----------------------------------------------------
>
> Key: TS-3643
> URL: https://issues.apache.org/jira/browse/TS-3643
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration, Logging
> Affects Versions: 5.3.0
> Reporter: David Carlin
> Fix For: 5.3.1
>
>
> TS-2944 broke our log processing by changing cache result code from TCP_HIT to TCP_MEM_HIT for the majority of our responses.
> Additionally, TS-3036 is better.
> https://issues.apache.org/jira/browse/TS-3036?focusedCommentId=14561404&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14561404
> Should TS-2944 be reverted since its redundant and breaks compatibility?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)