Tejaskriya opened a new pull request, #5200:
URL: https://github.com/apache/ozone/pull/5200

   ## What changes were proposed in this pull request?
   
   Changing the regex for KEYNAME_ILLEGAL_CHARACTER_CHECK_REGEX to allow "(" 
and ")"
   
   ## What is the link to the Apache JIRA
   
   https://issues.apache.org/jira/browse/HDDS-5161
   
   ## How was this patch tested?
   
   Tested manually using Docker after setting 
ozone.om.keyname.character.check.enabled to true in ozone_deafult.xml
   ```
   bash-4.2$ ozone sh key put "s3v/buck1/k1(" k1
   bash-4.2$ ozone sh key put "s3v/buck1/k1)" k1
   bash-4.2$ ozone sh key list s3v/buck1
   [ {
     "volumeName" : "s3v",
     "bucketName" : "buck1",
     "name" : "k1(",
     "dataSize" : 3,
     "creationTime" : "2023-08-18T07:17:31.837Z",
     "modificationTime" : "2023-08-18T07:53:49.334Z",
     "replicationConfig" : {
       "replicationFactor" : "THREE",
       "requiredNodes" : 3,
       "replicationType" : "RATIS"
     },
     "metadata" : { },
     "file" : true
   }, {
     "volumeName" : "s3v",
     "bucketName" : "buck1",
     "name" : "k1)",
     "dataSize" : 3,
     "creationTime" : "2023-08-18T07:55:34.549Z",
     "modificationTime" : "2023-08-18T07:55:35.397Z",
     "replicationConfig" : {
       "replicationFactor" : "THREE",
       "requiredNodes" : 3,
       "replicationType" : "RATIS"
     },
     "metadata" : { },
     "file" : true
   } ]
   bash-4.2$ ozone sh key put "s3v/buck1/k1|" k1
   Invalid key name: k1|
   bash-4.2$ ozone sh key put "s3v/buck1/k1\\" k1
   Invalid key name: k1\
   bash-4.2$ ozone sh key put "s3v/buck1/k1^" k1
   Invalid key name: k1^
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


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

Reply via email to