[
https://issues.apache.org/jira/browse/GEODE-734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15702786#comment-15702786
]
ASF GitHub Bot commented on GEODE-734:
--------------------------------------
Github user metatype commented on the issue:
https://github.com/apache/incubator-geode/pull/297
Thanks for the contribution! However, I don't think we should require user
input in order to gather stack traces. Quite often a user will automate
collection (`gfsh export stack-traces ...`) and will not be able to provide
input.
Here's a few ways we could extend the current behavior:
- Provide an option to auto-generate a unique name
- Provide an option that would cause the export to fail if the provided
file name is already present.
> gfsh export stack-traces should not require an output file with extension .txt
> ------------------------------------------------------------------------------
>
> Key: GEODE-734
> URL: https://issues.apache.org/jira/browse/GEODE-734
> Project: Geode
> Issue Type: Improvement
> Components: gfsh
> Reporter: Jens Deppe
>
> gfsh {{export stack-traces}} requires a file with a {{.txt}} extension:
> {noformat}
> gfsh>export stack-traces --file=/tmp/trace.log
> Invalid file type, the file extension must be ".txt"
> {noformat}
> This seems like a totally arbitrary restriction. Please can it be removed.
> If the concern is that an existing file might be overwritten then we should
> have a user prompt indicating that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
