Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
1.2.0
-
None
-
None
-
None
Description
Currently in Ozone we have different ways of handling certain compatibility problems, the main aim of this ticket to gather all the different issues/tasks in this area.
Attached a document about the current problems, and a forward looking proposal to this JIRA that describes the problem and the plans to resolve these problems. The scope might change over time though.
As there are problems that are covered by certain other feature's sub-tasks, some of the tickets belong to here will remain sub-tasks of other features, and are just linked in here. Versioning of client-server communication in Ozone.pdf
Attachments
Attachments
Issue Links
- is a parent of
-
HDDS-6223 Ozone 1.1.0 client listKeys on FSO bucket returns empty list
- Resolved
-
HDDS-5909 EC: Onboard EC into upgrade framework
- Resolved
-
HDDS-6182 General Purpose Client Versioning
- Resolved
-
HDDS-6209 EC: [Forward compatibility issue] New client to older server could fail due to the unavailability for client default replication config
- Resolved
-
HDDS-6213 Pluggable OzoneManager request handling hooks
- Resolved
-
HDDS-6040 [FSO] Support upgrade for the bucket layout
- Open
- is required by
-
HDDS-3816 Erasure Coding
- Resolved