[Bugs] [Bug 1313310] New: [RFE]Add --no-encode option to the `glusterfind pre` command

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1313310

            Bug ID: 1313310
           Summary: [RFE]Add --no-encode option to the `glusterfind pre`
                    command
           Product: GlusterFS
           Version: 3.7.8
         Component: glusterfind
          Keywords: FutureFeature
          Severity: medium
          Priority: medium
          Assignee: bugs at gluster.org
          Reporter: avishwan at redhat.com
        QA Contact: bugs at gluster.org
                CC: avishwan at redhat.com, bugs at gluster.org,
                    khiremat at redhat.com, rnalakka at redhat.com,
                    sanandpa at redhat.com
        Depends On: 1309277, 1310080



+++ This bug was initially created as a clone of Bug #1310080 +++

+++ This bug was initially created as a clone of Bug #1309277 +++

Description of problem:

Glusterfind intentionally encodes(RFC 3986
https://www.ietf.org/rfc/rfc3986.txt) the file/dir path. Since the encoded file
names are difficult to follow, there must an option to choose not to encode the
glusterfind pre output file. 

Version-Release number of selected component (if applicable):

RHGS 3.1.1

How reproducible:

Always

Steps to Reproduce:

1. create a glusterfind session 

2. make some new directories or files with Russian name(Eg:-тестирование\
гластерфайнд)

3. Generate out file ,using glusterfind pre

Actual results:

test2%2F%2F%D1%82%D0%B5%D1%81%D1%82%D0%B8%D1%80%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D0%B5+%D0%B3%D0%BB%D0%B0%D1%81%D1%82%D0%B5%D1%80%D1%84%D0%B0%D0%B9%D0%BD%D0%B4


Expected results:

test2//тестирование гластерфайнд



Additional info:

--- Additional comment from Vijay Bellur on 2016-02-19 07:13:14 EST ---

REVIEW: http://review.gluster.org/13477 (tools/glusterfind: New option
--no-encode) posted (#1) for review on master by Aravinda VK
(avishwan at redhat.com)

--- Additional comment from Vijay Bellur on 2016-02-23 00:08:25 EST ---

REVIEW: http://review.gluster.org/13477 (tools/glusterfind: New option
--no-encode) posted (#2) for review on master by Aravinda VK
(avishwan at redhat.com)

--- Additional comment from Vijay Bellur on 2016-02-23 00:13:23 EST ---

REVIEW: http://review.gluster.org/13477 (tools/glusterfind: New option
--no-encode) posted (#3) for review on master by Aravinda VK
(avishwan at redhat.com)

--- Additional comment from Vijay Bellur on 2016-02-26 05:11:26 EST ---

COMMIT: http://review.gluster.org/13477 committed in master by Venky Shankar
(vshankar at redhat.com) 
------
commit 1b897c39ba8c0f1bf180316637cc2d87e6920800
Author: Aravinda VK <avishwan at redhat.com>
Date:   Fri Feb 19 17:08:56 2016 +0530

    tools/glusterfind: New option --no-encode

    New option added to skip encoding path in output file. Also handled
    Unicode strings.

    File paths can have newline characters, to differentiate between each
    path patch is encoded according to
    RFC3986(https://www.ietf.org/rfc/rfc3986.txt). Due to this consumer
    applications have to decode the path before consuming it. With this
    option Paths are not encoded, can be directly consumed by
    applications.

    Unicode encoding is handled automatically

    BUG: 1310080
    Change-Id: I83d59831997dbd1264b48e9b1aa732c7dfc700b5
    Signed-off-by: Aravinda VK <avishwan at redhat.com>
    Reviewed-on: http://review.gluster.org/13477
    Smoke: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Milind Changire <mchangir at redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat at redhat.com>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar at redhat.com>


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1310080
[Bug 1310080] [RFE]Add --no-encode option to the `glusterfind pre` command
-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.