ryerraguntla commented on code in PR #4043:
URL: https://github.com/apache/iggy/pull/4043#discussion_r3968189968


##########
gateways/kafka/src/bridge/error.rs:
##########
@@ -0,0 +1,185 @@
+// Licensed to the Apache Software Foundation (ASF) under one
+// or more contributor license agreements.  See the NOTICE file
+// distributed with this work for additional information
+// regarding copyright ownership.  The ASF licenses this file
+// to you under the Apache License, Version 2.0 (the
+// "License"); you may not use this file except in compliance
+// with the License.  You may obtain a copy of the License at
+//
+//   http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing,
+// software distributed under the License is distributed on an
+// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+// KIND, either express or implied.  See the License for the
+// specific language governing permissions and limitations
+// under the License.
+
+use iggy::prelude::IggyError;
+use thiserror::Error;
+
+use crate::protocol::api::{
+    ERROR_INVALID_PARTITIONS, ERROR_NOT_LEADER_OR_FOLLOWER, 
ERROR_TOPIC_AUTHORIZATION_FAILED,
+    ERROR_UNKNOWN_SERVER_ERROR, ERROR_UNKNOWN_TOPIC_OR_PARTITION,
+};
+
+/// Errors from the `IggyBridge`: connection lifecycle, config, and Iggy SDK 
calls.
+#[derive(Debug, Error)]
+pub enum BridgeError {
+    /// Bridge config is structurally invalid (empty address, missing 
credentials, malformed
+    /// topic-mapping TOML) - caught before any connection attempt.
+    #[error("invalid bridge configuration: {0}")]
+    InvalidConfig(String),
+    /// The Iggy client could not connect or authenticate, or a call failed 
after connecting.
+    /// Wraps the SDK's own error rather than re-deriving a parallel taxonomy.
+    #[error("Iggy client error: {0}")]
+    Iggy(#[from] IggyError),

Review Comment:
   Documented, not fixed at the root — can't be, from this crate. 
BridgeError::Iggy's Display now carries an explicit caution (error.rs:36-42) 
that a server-round-tripped IggyError may print a defaulted payload
     (Identifier::default() = numeric 0, String::default() = ""), traced to 
IggyError::from_code (vsr.rs) reconstructing data-carrying variants from a bare 
wire status code with no payload to recover.
     
     Considered and rejected:  Didn't do it because the risk is general
     to any IggyError that crosses the wire, not just the ones this bridge 
special-cases today — that would mean auditing every fallible SDK call for 
whether its error path can carry a defaulted payload. Root fix should be   in 
the SDK in multiple ways.



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

Reply via email to