From 43a8c564a0921b9210c13d6c4532faa8e566fadb Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Fri, 19 Oct 2018 17:54:49 +0000 Subject: [PATCH] Added a comment --- ...ment_2_915c1c31fcb23455aa11331cd34aa92d._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/todo/option_to_add_user-specified_string_to_key/comment_2_915c1c31fcb23455aa11331cd34aa92d._comment diff --git a/doc/todo/option_to_add_user-specified_string_to_key/comment_2_915c1c31fcb23455aa11331cd34aa92d._comment b/doc/todo/option_to_add_user-specified_string_to_key/comment_2_915c1c31fcb23455aa11331cd34aa92d._comment new file mode 100644 index 0000000000..f0b61e3cf8 --- /dev/null +++ b/doc/todo/option_to_add_user-specified_string_to_key/comment_2_915c1c31fcb23455aa11331cd34aa92d._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="comment 2" + date="2018-10-19T17:54:49Z" + content=""" +Another use case for a user-defined string field in a key is, for URL or WORM keys, to include additional information unique to the object. E.g. for an s3:// URI (handled by an external special remote) could embed the ETag in the key. Or for a dx:// URI to include the DNAnexus file ID . + +From [[internals/key_format]], it seems like adding -uXXXXXX- (with XXXXXX a user-specified string) would not break compatibility? + + + +"""]]