Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 8AB2C200B2D for ; Fri, 27 May 2016 02:39:14 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 89883160A18; Fri, 27 May 2016 00:39:14 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id D556D160A2B for ; Fri, 27 May 2016 02:39:13 +0200 (CEST) Received: (qmail 28661 invoked by uid 500); 27 May 2016 00:39:13 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 28613 invoked by uid 99); 27 May 2016 00:39:12 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 May 2016 00:39:12 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id DC55C2C1F56 for ; Fri, 27 May 2016 00:39:12 +0000 (UTC) Date: Fri, 27 May 2016 00:39:12 +0000 (UTC) From: "Joep Rottinghuis (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (YARN-5167) Escaping occurences of encodedValues MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 27 May 2016 00:39:14 -0000 Joep Rottinghuis created YARN-5167: -------------------------------------- Summary: Escaping occurences of encodedValues Key: YARN-5167 URL: https://issues.apache.org/jira/browse/YARN-5167 Project: Hadoop YARN Issue Type: Sub-task Components: timelineserver Reporter: Joep Rottinghuis Assignee: Sangjin Lee Priority: Critical We had earlier decided to punt on this, but in discussing YARN-5109 we thought it would be best to just be safe rather than sorry later on. Encoded sequences can occur in the original string, especially in case of "foreign key" if we decide to have lookups. For example, space is encoded as %2$. Encoding "String with %2$ in it" would decode to "String with in it". We though we should first escape existing occurrences of encoded strings by prefixing a backslash (even if there is already a backslash that should be ok). Then we should replace all unencoded strings. On the way out, we should replace all occurrences of our encoded string to the original except when it is prefixed by an escape character. Lastly we should strip off the one additional backslash in front of each remaining (escaped) sequence. If we add the following entry to TestSeparator#testEncodeDecode() that demonstrates what this jira should accomplish: {code} testEncodeDecode("Double-escape %2$ and %3$ or \\%2$ or \\%3$, nor \\\\%2$ = no problem!", Separator.QUALIFIERS, Separator.VALUES, Separator.SPACE, Separator.TAB); {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org