[ 
https://issues.apache.org/jira/browse/IMPALA-12296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747083#comment-17747083
 ] 

ASF subversion and git services commented on IMPALA-12296:
----------------------------------------------------------

Commit b7dd3c267a6e5ec092297bde853681f77c0da50c in impala's branch 
refs/heads/master from Surya Hebbar
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=b7dd3c267 ]

IMPALA-12296: Fix filenames in query profile download page

The downloads of query profiles from the profile page contain ':'
in the filename, this is not supported by some filesystems
such as NTFS.

Most browsers replace it with a white-space during the download.

Hence, characters except letters and white spaces in downloaded
profile's filename should be replaced with '_'.

Tests in 'test_web_pages.py' do not need modifications as
the endpoint for profile downloads has not changed.

Change-Id: Ia170e0ae1adc6f3347b57ca8572d65a05ebf9544
Reviewed-on: http://gerrit.cloudera.org:8080/20215
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>


> Fix filenames in query profile download page
> --------------------------------------------
>
>                 Key: IMPALA-12296
>                 URL: https://issues.apache.org/jira/browse/IMPALA-12296
>             Project: IMPALA
>          Issue Type: Improvement
>            Reporter: Surya Hebbar
>            Assignee: Surya Hebbar
>            Priority: Minor
>
> The files downloaded from the profile page contain ':' in the file name, this 
> is not supported by some file systems such as NTFS. Hence, most browsers 
> replace it with a white-space during download.
> It maybe better to correct the downloaded profile names, without relying on 
> the browser.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to