[fix] Remove legacy warnings for mooncake upsert API

tests/e2e/test_e2e_lifecycle_consistency.py

@@ -424,11 +424,6 @@ def test_core_consistency(e2e_client):
 def test_cross_shard_complex_update(e2e_client):
     """Cross-shard update: put A + put B, update overlapping region, verify all regions."""
 
-    # FIXME: Add data update test to MooncakeStore after Upsert function is ready
-    #        https://github.com/kvcache-ai/Mooncake/issues/1645
-    if os.environ.get("TQ_TEST_BACKEND", "SimpleStorage") == "MooncakeStore":
-        return
-
     client = e2e_client
     partition_id = "test_cross_shard_update"
     task_name = "cross_shard_task"

transfer_queue/storage/managers/mooncake_manager.py

@@ -16,22 +16,19 @@
 from typing import Any
 
 from transfer_queue.storage.managers.base import KVStorageManager, StorageManagerFactory
-from transfer_queue.utils.logging_utils import get_logger
 from transfer_queue.utils.zmq_utils import ZMQServerInfo
 
-logger = get_logger(__name__)
-
 
 @StorageManagerFactory.register("MooncakeStore")
 class MooncakeStorageManager(KVStorageManager):
-    """Storage manager for MooncakeStorage backend."""
+    """Storage manager for MooncakeStorage backend.
 
-    def __init__(self, controller_info: ZMQServerInfo, config: dict[str, Any]):
-        logger.warning(
-            "MooncakeStore backend doesn't support key update (upsert) for now. "
-            "You must delete the key before updating it. "
-            "Refer to https://github.com/kvcache-ai/Mooncake/issues/1645 for details."
-        )
+    Key update (upsert) is supported natively via the MooncakeStore client's
+    ``batch_upsert_from`` (zero-copy tensor path) and ``upsert_batch`` (raw bytes
+    path). See ``mooncake-integration/store/store_py.cpp`` upstream for the
+    pybind bindings.
+    """
 
+    def __init__(self, controller_info: ZMQServerInfo, config: dict[str, Any]):
         config["client_name"] = "MooncakeStoreClient"
         super().__init__(controller_info, config)