hemantk-12 commented on code in PR #7400:
URL: https://github.com/apache/ozone/pull/7400#discussion_r1832178544


##########
hadoop-ozone/dist/src/main/smoketest/compatibility/write.robot:
##########
@@ -40,3 +44,13 @@ FSO Bucket Can Be Created and Used
     Execute    ozone sh bucket create --layout FILE_SYSTEM_OPTIMIZED 
/vol1/fso-bucket-${SUFFIX}
     Execute    ozone fs -mkdir -p ofs://om/vol1/fso-bucket-${SUFFIX}/dir/subdir
     Execute    ozone fs -put ${TESTFILE} 
ofs://om/vol1/fso-bucket-${SUFFIX}/dir/subdir/file
+
+HSync Can Be Used To Create Keys
+    Pass Execution If    '${CLIENT_VERSION}' < '${HSYNC_VERSION}'    Client 
does not support HSYNC
+    Pass Execution If    '${CLUSTER_VERSION}' < '${HSYNC_VERSION}'   Cluster 
does not support HSYNC
+    Execute             ozone sh volume create /${VOL}
+    Execute             ozone sh bucket create /${VOL}/${BUCK}
+    ${o3fspath} =   Format FS URL         o3fs     ${VOL}    ${BUCK}
+    Freon DFSG      sync=HSYNC    path=${o3fspath}
+    ${pfspath} =    Format FS URL         ofs      ${VOL}    ${BUCK}
+    Freon DFSG      sync=HSYNC    path=${pfspath}

Review Comment:
   Initially, I used the `vol1` and `bucket1` 
https://github.com/hemantk-12/ozone/commit/7e9eed7b9070c703d11d1df0dc3d585713e14ec5
 but `Dir Can Be Listed Using Shell` test was failing in the [workflow 
run](https://github.com/hemantk-12/ozone/actions/runs/11695970086/job/32573194067).
 So rather than fixing `Dir Can Be Listed Using Shell` test, I created new 
volume and bucket for hsync test case.
   I guess I can change `Dir Can Be Listed Using Shell` test to list only 
`dir-${SUFFIX}` dir rather than all the dirs in the bucket. I'll test it out 
and submit a follow-up PR.



-- 
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