Uploaded image for project: 'Apache Ozone'
  1. Apache Ozone
  2. HDDS-8292

Inconsistent key name handling for FSO bucket files

    XMLWordPrintableJSON

Details

    Description

      The definition of the field OmKeyInfo.keyName is ambiguous.

      In some of the code, it is the full path to a file; in some, it is just the final part (excluding the path).

      I am looking at a cluster where some of the entries in fileTable in its OM db has full path, and some don't.

      # ozone debug ldb --db=om.db scan --column_family=fileTable -l -1 --with-keys | less
      "/-9223372036854561536/-9223372036854561024/-9223372036854525695/433dfbc470b54a0e9a23ed79240c3dc3" -> {
        "volumeName": "vol1",
        "bucketName": "bucket1",
        "keyName": "hbase/data/hbase/meta/1588230740/info/433dfbc470b54a0e9a23ed79240c3dc3",
      ...
      
      "/-9223372036854561536/-9223372036854561024/-9223372036854525695/c3a068821e7544caae7cdbaf9ca1b263" -> {
        "volumeName": "vol1",
        "bucketName": "bucket1",
        "keyName": "c3a068821e7544caae7cdbaf9ca1b263",
      

      Bug: ListStatus request returns incorrect path name, because OzoneListStatusHelper.getStatus() expects the keyName to be just the final part, and prepend the prefix, which is incorrect for the example above.

      Attachments

        1. omdb-hdds-8292.tgz
          3.53 MB
          Wei-Chiu Chuang
        2. om-audit-hdds-8292.tgz
          314 kB
          Wei-Chiu Chuang
        3. image-2023-04-03-14-23-41-579.png
          226 kB
          Sumit Agrawal

        Issue Links

          Activity

            People

              ashishk Ashish Kumar
              weichiu Wei-Chiu Chuang
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: