[Bugs] [Bug 1453151] glusterfind pre session gives wrong output when using a windows client to copy and rename a file
bugzilla at redhat.com
bugzilla at redhat.com
Mon Jun 12 04:48:59 UTC 2017
https://bugzilla.redhat.com/show_bug.cgi?id=1453151
--- Comment #9 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/17481 committed in master by Aravinda VK
(avishwan at redhat.com)
------
commit 64588d4f6d69ce6e9b82335d12fa6c42794c38fa
Author: Milind Changire <mchangir at redhat.com>
Date: Tue Jun 6 23:43:54 2017 +0530
tools/glusterfind: add --field-separator option
Problem:
Default field separator is a space character.
This gets in the way if the file name itself has embedded spaces.
Solution:
Add --field-separator option to "pre" and "query" commands.
The field separator string will be used to separate strings in the
output lines that get written to the output file.
eg.
old output:
NEW file1.txt
RENAME file2 Copy.txt file3.txt
with --field-separator as "==="
new output:
NEW===file1.txt
RENAME===file2 Copy.txt===file3.txt
Change-Id: I71e878fed58ba1113d97044ac9f6404ee66227c7
BUG: 1453151
Signed-off-by: Milind Changire <mchangir at redhat.com>
Reviewed-on: https://review.gluster.org/17481
Smoke: Gluster Build System <jenkins at build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
Reviewed-by: Aravinda VK <avishwan at redhat.com>
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
More information about the Bugs
mailing list