[jira] [Updated] (TS-81) Have one single place to store and lookup remap rules irrespective of type
[ https://issues.apache.org/jira/browse/TS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Call updated TS-81: - Fix Version/s: (was: 7.0.0) 8.0.0 > Have one single place to store and lookup remap rules irrespective of type > -- > > Key: TS-81 > URL: https://issues.apache.org/jira/browse/TS-81 > Project: Traffic Server > Issue Type: Improvement > Components: Core, HTTP >Affects Versions: 2.0.0a >Reporter: Manjesh Nilange >Priority: Minor > Labels: incompatible > Fix For: 8.0.0 > > > Currently, remap rules are stored in different structures and looked up > separately based on type (forward, reverse, etc.). It'd be better design and > more maintainable to process (store, search) all rules in one structure and > then use type to determine action. > A fundamental problem with our current implementation is that the order in > remap.config is not honored. E.g. a map directive always takes precedence > over any redirect directives (if both matches). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-81) Have one single place to store and lookup remap rules irrespective of type
[ https://issues.apache.org/jira/browse/TS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Call updated TS-81: - Component/s: HTTP > Have one single place to store and lookup remap rules irrespective of type > -- > > Key: TS-81 > URL: https://issues.apache.org/jira/browse/TS-81 > Project: Traffic Server > Issue Type: Improvement > Components: Core, HTTP >Affects Versions: 2.0.0a >Reporter: Manjesh Nilange >Priority: Minor > Labels: incompatible > Fix For: 8.0.0 > > > Currently, remap rules are stored in different structures and looked up > separately based on type (forward, reverse, etc.). It'd be better design and > more maintainable to process (store, search) all rules in one structure and > then use type to determine action. > A fundamental problem with our current implementation is that the order in > remap.config is not honored. E.g. a map directive always takes precedence > over any redirect directives (if both matches). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-81) Have one single place to store and lookup remap rules irrespective of type
[ https://issues.apache.org/jira/browse/TS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-81: Fix Version/s: (was: 6.0.0) 7.0.0 Have one single place to store and lookup remap rules irrespective of type -- Key: TS-81 URL: https://issues.apache.org/jira/browse/TS-81 Project: Traffic Server Issue Type: Improvement Components: Core Affects Versions: 2.0.0a Reporter: Manjesh Nilange Priority: Minor Labels: incompatible Fix For: 7.0.0 Currently, remap rules are stored in different structures and looked up separately based on type (forward, reverse, etc.). It'd be better design and more maintainable to process (store, search) all rules in one structure and then use type to determine action. A fundamental problem with our current implementation is that the order in remap.config is not honored. E.g. a map directive always takes precedence over any redirect directives (if both matches). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-81) Have one single place to store and lookup remap rules irrespective of type
[ https://issues.apache.org/jira/browse/TS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-81: Assignee: (was: Sudheer Vinukonda) Have one single place to store and lookup remap rules irrespective of type -- Key: TS-81 URL: https://issues.apache.org/jira/browse/TS-81 Project: Traffic Server Issue Type: Improvement Components: Core Affects Versions: 2.0.0a Reporter: Manjesh Nilange Priority: Minor Labels: incompatible Fix For: 7.0.0 Currently, remap rules are stored in different structures and looked up separately based on type (forward, reverse, etc.). It'd be better design and more maintainable to process (store, search) all rules in one structure and then use type to determine action. A fundamental problem with our current implementation is that the order in remap.config is not honored. E.g. a map directive always takes precedence over any redirect directives (if both matches). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-81) Have one single place to store and lookup remap rules irrespective of type
[ https://issues.apache.org/jira/browse/TS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-81: Labels: incompatible (was: ) Have one single place to store and lookup remap rules irrespective of type -- Key: TS-81 URL: https://issues.apache.org/jira/browse/TS-81 Project: Traffic Server Issue Type: Improvement Components: Core Affects Versions: 2.0.0a Reporter: Manjesh Nilange Assignee: Sudheer Vinukonda Priority: Minor Labels: incompatible Fix For: 6.0.0 Currently, remap rules are stored in different structures and looked up separately based on type (forward, reverse, etc.). It'd be better design and more maintainable to process (store, search) all rules in one structure and then use type to determine action. A fundamental problem with our current implementation is that the order in remap.config is not honored. E.g. a map directive always takes precedence over any redirect directives (if both matches). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-81) Have one single place to store and lookup remap rules irrespective of type
[ https://issues.apache.org/jira/browse/TS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-81: Assignee: Sudheer Vinukonda Have one single place to store and lookup remap rules irrespective of type -- Key: TS-81 URL: https://issues.apache.org/jira/browse/TS-81 Project: Traffic Server Issue Type: Improvement Components: Core Affects Versions: 2.0.0a Reporter: Manjesh Nilange Assignee: Sudheer Vinukonda Priority: Minor Fix For: 6.0.0 Currently, remap rules are stored in different structures and looked up separately based on type (forward, reverse, etc.). It'd be better design and more maintainable to process (store, search) all rules in one structure and then use type to determine action. A fundamental problem with our current implementation is that the order in remap.config is not honored. E.g. a map directive always takes precedence over any redirect directives (if both matches). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-81) Have one single place to store and lookup remap rules irrespective of type
[ https://issues.apache.org/jira/browse/TS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-81: Fix Version/s: (was: sometime) 6.0.0 Have one single place to store and lookup remap rules irrespective of type -- Key: TS-81 URL: https://issues.apache.org/jira/browse/TS-81 Project: Traffic Server Issue Type: Improvement Components: Core Affects Versions: 2.0.0a Reporter: Manjesh Nilange Priority: Minor Fix For: 6.0.0 Currently, remap rules are stored in different structures and looked up separately based on type (forward, reverse, etc.). It'd be better design and more maintainable to process (store, search) all rules in one structure and then use type to determine action. A fundamental problem with our current implementation is that the order in remap.config is not honored. E.g. a map directive always takes precedence over any redirect directives (if both matches). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-81) Have one single place to store and lookup remap rules irrespective of type
[ https://issues.apache.org/jira/browse/TS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Susan Hinrichs updated TS-81: - Fix Version/s: (was: 5.3.0) sometime Have one single place to store and lookup remap rules irrespective of type -- Key: TS-81 URL: https://issues.apache.org/jira/browse/TS-81 Project: Traffic Server Issue Type: Improvement Components: Core Affects Versions: 2.0.0a Reporter: Manjesh Nilange Priority: Minor Labels: A Fix For: sometime Currently, remap rules are stored in different structures and looked up separately based on type (forward, reverse, etc.). It'd be better design and more maintainable to process (store, search) all rules in one structure and then use type to determine action. A fundamental problem with our current implementation is that the order in remap.config is not honored. E.g. a map directive always takes precedence over any redirect directives (if both matches). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-81) Have one single place to store and lookup remap rules irrespective of type
[ https://issues.apache.org/jira/browse/TS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Susan Hinrichs updated TS-81: - Labels: (was: A) Have one single place to store and lookup remap rules irrespective of type -- Key: TS-81 URL: https://issues.apache.org/jira/browse/TS-81 Project: Traffic Server Issue Type: Improvement Components: Core Affects Versions: 2.0.0a Reporter: Manjesh Nilange Priority: Minor Fix For: sometime Currently, remap rules are stored in different structures and looked up separately based on type (forward, reverse, etc.). It'd be better design and more maintainable to process (store, search) all rules in one structure and then use type to determine action. A fundamental problem with our current implementation is that the order in remap.config is not honored. E.g. a map directive always takes precedence over any redirect directives (if both matches). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-81) Have one single place to store and lookup remap rules irrespective of type
[ https://issues.apache.org/jira/browse/TS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-81: Fix Version/s: (was: 6.0.0) 5.3.0 Have one single place to store and lookup remap rules irrespective of type -- Key: TS-81 URL: https://issues.apache.org/jira/browse/TS-81 Project: Traffic Server Issue Type: Improvement Components: Core Affects Versions: 2.0.0a Reporter: Manjesh Nilange Priority: Minor Labels: A Fix For: 5.3.0 Currently, remap rules are stored in different structures and looked up separately based on type (forward, reverse, etc.). It'd be better design and more maintainable to process (store, search) all rules in one structure and then use type to determine action. A fundamental problem with our current implementation is that the order in remap.config is not honored. E.g. a map directive always takes precedence over any redirect directives (if both matches). -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (TS-81) Have one single place to store and lookup remap rules irrespective of type
[ https://issues.apache.org/jira/browse/TS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-81: Description: Currently, remap rules are stored in different structures and looked up separately based on type (forward, reverse, etc.). It'd be better design and more maintainable to process (store, search) all rules in one structure and then use type to determine action. A fundamental problem with our current implementation is that the order in remap.config is not honored. E.g. a map directive always takes precedence over any redirect directives (if both matches). was: Currently, remap rules are stored in different structures and looked up separately based on type (forward, reverse, etc.). It'd be better design and more maintainable to process (store, search) all rules in one structure and then use type to determine action. Have one single place to store and lookup remap rules irrespective of type -- Key: TS-81 URL: https://issues.apache.org/jira/browse/TS-81 Project: Traffic Server Issue Type: Improvement Components: Core Affects Versions: 2.0.0a Reporter: Manjesh Nilange Priority: Minor Labels: A Fix For: 6.0.0 Currently, remap rules are stored in different structures and looked up separately based on type (forward, reverse, etc.). It'd be better design and more maintainable to process (store, search) all rules in one structure and then use type to determine action. A fundamental problem with our current implementation is that the order in remap.config is not honored. E.g. a map directive always takes precedence over any redirect directives (if both matches). -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (TS-81) Have one single place to store and lookup remap rules irrespective of type
[ https://issues.apache.org/jira/browse/TS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-81: Labels: A (was: ) Have one single place to store and lookup remap rules irrespective of type -- Key: TS-81 URL: https://issues.apache.org/jira/browse/TS-81 Project: Traffic Server Issue Type: Improvement Components: Core Affects Versions: 2.0.0a Reporter: Manjesh Nilange Priority: Minor Labels: A Fix For: 3.5.0 Currently, remap rules are stored in different structures and looked up separately based on type (forward, reverse, etc.). It'd be better design and more maintainable to process (store, search) all rules in one structure and then use type to determine action. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-81) Have one single place to store and lookup remap rules irrespective of type
[ https://issues.apache.org/jira/browse/TS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-81: Fix Version/s: (was: 3.3.4) 3.5.0 Have one single place to store and lookup remap rules irrespective of type -- Key: TS-81 URL: https://issues.apache.org/jira/browse/TS-81 Project: Traffic Server Issue Type: Improvement Components: Core Affects Versions: 2.0.0a Reporter: Manjesh Nilange Priority: Minor Fix For: 3.5.0 Currently, remap rules are stored in different structures and looked up separately based on type (forward, reverse, etc.). It'd be better design and more maintainable to process (store, search) all rules in one structure and then use type to determine action. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (TS-81) Have one single place to store and lookup remap rules irrespective of type
[ https://issues.apache.org/jira/browse/TS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-81: Fix Version/s: (was: 2.1.8) 3.1 Have one single place to store and lookup remap rules irrespective of type -- Key: TS-81 URL: https://issues.apache.org/jira/browse/TS-81 Project: Traffic Server Issue Type: Improvement Components: Core Affects Versions: 2.0.0a Reporter: Manjesh Nilange Priority: Minor Fix For: 3.1 Currently, remap rules are stored in different structures and looked up separately based on type (forward, reverse, etc.). It'd be better design and more maintainable to process (store, search) all rules in one structure and then use type to determine action. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (TS-81) Have one single place to store and lookup remap rules irrespective of type
[ https://issues.apache.org/jira/browse/TS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-81: Fix Version/s: (was: 2.1.7) (was: 3.1) 2.1.8 Have one single place to store and lookup remap rules irrespective of type -- Key: TS-81 URL: https://issues.apache.org/jira/browse/TS-81 Project: Traffic Server Issue Type: Improvement Components: Core Affects Versions: 2.0.0a Reporter: Manjesh Nilange Priority: Minor Fix For: 2.1.8 Currently, remap rules are stored in different structures and looked up separately based on type (forward, reverse, etc.). It'd be better design and more maintainable to process (store, search) all rules in one structure and then use type to determine action. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (TS-81) Have one single place to store and lookup remap rules irrespective of type
[ https://issues.apache.org/jira/browse/TS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-81: Fix Version/s: 2.1.7 I'm going to target this for v2.1.x for now, maybe as an interim solution, we can use the priority numbering to decide if a map rule can be beaten by a lookup on the redirect maps (similar to how we optimize the regex mappings). Have one single place to store and lookup remap rules irrespective of type -- Key: TS-81 URL: https://issues.apache.org/jira/browse/TS-81 Project: Traffic Server Issue Type: Improvement Components: Core Affects Versions: 2.0.0a Reporter: Manjesh Nilange Priority: Minor Fix For: 3.1, 2.1.7 Currently, remap rules are stored in different structures and looked up separately based on type (forward, reverse, etc.). It'd be better design and more maintainable to process (store, search) all rules in one structure and then use type to determine action. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
