bjornjorgensen commented on PR #38564:
URL: https://github.com/apache/spark/pull/38564#issuecomment-1307705463

   Yes, I agree with you @dongjoon-hyun . I will close this one.
   
   If someone else is reading this in the future.  
   This is what's marked as API changes in the release notes. 
   
   Version 1.11.0
   Additional API Changes:
   
     * **Breaking change** Deprecated authentication credential text format 
support.
   
   
   Version 1.10.0
   Additional API Changes:
   
     * Quota can now be set on the default `*` role.
     * Quota consumption metrics are now exposed by the allocator.
   
   
   
   Version 1.9.0
   Additional API Changes:
   
     * Mesos components will now forego TLS certificate validation for incoming
       connections, unless `LIBPROCESS_SSL_REQUIRE_CERT` is set to true.
   
     * The `Socket::connect(const Address&)` member function will now abort the
       program when called on a `LibeventSSLSocket`. Instead, the new overload
       `Socket::connect(const Address&, const TLSClientConfig&)` must be used.
   
       NOTE: This new overload is only available when libprocess is compiled
       with `--enable-ssl`.
   
   
   Version 1.8.0
   Additional API Changes:
     * [MESOS-9540] - Improved the experimental `DESTROY_DISK` operations so
       frameworks can now deprovision any unwanted pre-provisioned CSI volume
       directly, if they are authorized to perform `DESTROY_RAW_DISK` actions.
   
   Version 1.7.0
   Additional API Changes:
     * [MESOS-9066] - Introduced `CREATE_DISK` and `DESTROY_DISK` offer
       operations to replace `CREATE_VOLUME`, `CREATE_BLOCK`,
       `DESTROY_VOLUME` and `DESTROY_BLOCK`.
   
     * Container logger module interface has been changed. The `prepare()` 
method
       now takes `ContainerID` and `ContainerConfig` instead.
   
     * `Isolator::recover` interface has been changed to take an `std::vector`
       instead of `std::list`.
   
     * JSON endpoints now use rapidjson to provide a performance improvement,
       this means that if a client has a JSON de-serializer that does not
       conform to the ECMA-404 spec for JSON, they may break. As an example,
       Mesos would previously serialize '/' as '\/', but the spec does not
       require the escaping and rapidjson does not escape '/'.
   
   Changes to Dependencies:
     * [MESOS-8395] - Made gRPC a requirement for Mesos builds. The 
`--enable-grpc`
       Autotools option and the `-DENABLE_GRPC=ON` CMake option is now removed.
   
     * [MESOS-8064] - Mesos now requires libarchive to programmatically decode
       .zip, .tar, .gzip, and other common file compression schemes. Version 
3.3.2
       is bundled in Mesos.
   
     * [MESOS-9092] - Adopt rapidjson for improved json serialization 
performance.
       Version 1.1.0 is bundled in Mesos.
   
   Version 1.6.0
   Deprecations/Removals:
     * Support for CSI v0.1 is deprecated in favor of CSI v0.2.
   
   Additional API Changes:
     * [MESOS-8306] - Authorization of resource reservation has been updated
       to allow the restriction of which agents can statically reserve
       resources for which roles.
   
     * [MESOS-8332] - Container sandbox permissions have been changed from
       0755 to 0750.
   
     * [MESOS-8388] - Local resource provider resources are now included in
       the responses to the GET_AGENTS and GET_RESOURCE_PROVIDER calls.
   
     * [MESOS-8534] - Nested containers within a task group can now specify
       separate network namespaces.
   
   Changes to Dependencies:
     * Upgraded minimum required gRPC library to version 1.10+ for gRPC-enabled 
builds.
   
   
   
   Version 1.5.0
   Deprecations/Removals:
     * [MESOS-7305] - Some nested container agent APIs `****_NESTED_CONTAINER`
       are deprecated in favor of the new generally named agent APIs
       `****_CONTAINER`.
   
     * Agent flag `--executor_secret_key` has been deprecated. Operators
       should use `--jwt_secret_key` instead.
   
   Additional API Changes:
     * [MESOS-6406, MESOS-7215, MESOS-8337] Now when an agent is partitioned,
       the master tracks all noncompleted tasks regardless of 
partition-awareness
       so when the agent reregisters it can recover all of them and send their
       latest statuses to the scheduler. NOTE: The master now sends updates for
       tasks recovered from partitioned agents upon reregistration so the 
scheduler
       can get them before reconciliation. We also fixed the buggy semantics 
that
       exposes terminal unacknowledged tasks when partitioned as "completed" in 
the
       HTTP endpoints and the operator API, now they are shown as 
"unreachable". We
       plan to further improve the API on this in MESOS-8405.
   
     * [MESOS-7550] The fields `Resource.disk.source.path.root` and
       `Resource.disk.source.mount.root` can now be set to relative paths
       to an agent's work directory.
   
     * [MESOS-7660] `Filter::refuse_seconds` is now capped to 31536000
       seconds (365 days).
   
     * [MESOS-7941] Built-in executors will now send a TASK_STARTING
       status update when a task is starting.
   
     * [MESOS-7973] A new `catchup` method has been added to the
       `Log.Reader` interface (including Java binding).
   
     * [MESOS-8040] Return nested/standalone containers in `GET_CONTAINERS`
       API call.
   
     * [MESOS-8165] Master will now send TASK_GONE status for unknown
       tasks of PARTITION_AWARE frameworks belonging to registered agents
       during explicit reconciliation.
   
   Changes to Dependencies:
     * Upgraded minimum required Protobuf library to version 3+.
   
   
   Thank you, @dongjoon-hyun and @srowen 


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