[ 
https://issues.apache.org/jira/browse/HDDS-5370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rakesh Radhakrishnan updated HDDS-5370:
---------------------------------------
    Description: 
This task is to minimize the dependency with configuration flags 
'ozone.om.enable.filesystem.paths' and 'ozone.om.metadata.layout' for 
determining the bucket layout and redirect the execution paths. Basically, the 
idea here is to use the layout stored in the bucket and dynamically determine 
the FSO or non-FSO execution flow.

Note: There will be some more follow-up tasks raised to completely remove the 
configuration flags dependency everywhere in the code.

  was:Now we determine if bucket is FSOptimized if the config 
'ozone.om.enable.filesystem.paths' is set to true. In follow-ups jiras we will 
remove this property and determine bucket type by directly comparing it with an 
enum(BucketType.FSO).


> [FSO] Handle OMClientRequest based on the bucket layout
> -------------------------------------------------------
>
>                 Key: HDDS-5370
>                 URL: https://issues.apache.org/jira/browse/HDDS-5370
>             Project: Apache Ozone
>          Issue Type: Sub-task
>          Components: Ozone Manager
>            Reporter: Aryan Gupta
>            Assignee: Aryan Gupta
>            Priority: Major
>              Labels: pull-request-available
>
> This task is to minimize the dependency with configuration flags 
> 'ozone.om.enable.filesystem.paths' and 'ozone.om.metadata.layout' for 
> determining the bucket layout and redirect the execution paths. Basically, 
> the idea here is to use the layout stored in the bucket and dynamically 
> determine the FSO or non-FSO execution flow.
> Note: There will be some more follow-up tasks raised to completely remove the 
> configuration flags dependency everywhere in the code.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to