prestodb/presto · error · ParseError

{parse_error} ConnectorInsertTableHandle ConnectorInsertTab

Error message

{parse_error} ConnectorInsertTableHandle  ConnectorInsertTableHandle

What it means

This ParseError is thrown while deserializing JSON into a shared_ptr<ConnectorInsertTableHandle>. getSubclassKey(j) threw a json::parse_error, re-thrown as ParseError with 'ConnectorInsertTableHandle' appended. The insert table handle JSON is syntactically invalid, blocking identification of the connector-specific insert handle.

Source

Thrown at presto-native-execution/presto_cpp/presto_protocol/core/presto_protocol_core.cpp:6627

      "TupleDomain<std::shared_ptr<ColumnHandle>>",
      "currentConstraint");
}
} // namespace facebook::presto::protocol
namespace facebook::presto::protocol {
void to_json(json& j, const std::shared_ptr<ConnectorInsertTableHandle>& p) {
  if (p == nullptr) {
    return;
  }
  String type = p->_type;
  getConnectorProtocol(type).to_json(j, p);
}

void from_json(const json& j, std::shared_ptr<ConnectorInsertTableHandle>& p) {
  String type;
  try {
    type = p->getSubclassKey(j);
  } catch (json::parse_error& e) {
    throw ParseError(
        std::string(e.what()) +
        " ConnectorInsertTableHandle  ConnectorInsertTableHandle");
  }

  if (j.contains("customSerializedValue")) {
    VELOX_CHECK(
        !type.empty() && type[0] != '$',
        "Internal handle type '{}' should not have customSerializedValue",
        type);
    std::string binaryData = velox::encoding::Base64::decode(
        j["customSerializedValue"].get<std::string>());
    getConnectorProtocol(type).deserialize(binaryData, p);
    return;
  }

  getConnectorProtocol(type).from_json(j, p);
}
} // namespace facebook::presto::protocol

View on GitHub (pinned to 55bb57d202)

Solutions

1. Re-parse the insert table handle fragment with a strict JSON parser to locate the error
2. Check the connector's ConnectorInsertTableHandle serialization on the coordinator
3. Verify coordinator and native sidecar/worker versions match
4. Log and validate the whole plan JSON before native deserialization

Example fix

// before
proto::from_json(insertHandleJson, insertHandle);
// after
json j = json::parse(insertHandleJson); // throws with position info
proto::from_json(j, insertHandle);

json j = json::parse(insertHandleJson);
if (!j.is_object() || !j.contains("type")) {
  throw std::runtime_error("ConnectorInsertTableHandle JSON invalid: missing 'type'");
}

bool isWellFormedInsertHandleJson(const json& j) {
  return j.is_object() && j.contains("type") && j["type"].is_string();
}

try {
  proto::from_json(j, insertHandle);
} catch (const ParseError& e) {
  LOG(ERROR) << "bad ConnectorInsertTableHandle JSON: " << e.what();
  throw;
}

When it happens

Trigger: from_json called during TableWriter/Insert plan deserialization where the ConnectorInsertTableHandle JSON fragment is malformed (truncation, invalid escapes, non-JSON bytes).

Common situations: Connector emitting a badly serialized insert handle; coordinator/native version mismatch on create/insert paths; corrupted or manually edited plan JSON.

Understand the failure class

Background: JSON parse error: "Unexpected token" / "not valid JSON" / "failed to parse" — what JSON parsers are really complaining about — this error's family across 45 libraries.

Related errors

• {parse_error} ConnectorIndexHandle ConnectorIndexHandle
• {parse_error} ColumnHandle ColumnHandle
• {parse_error} ConnectorTableLayoutHandle ConnectorTableLayo
• {parse_error} ConnectorMergeTableHandle ConnectorMergeTable
• (JsonMappingException cause message)

AI-assisted analysis of prestodb/presto@55bb57d202 (2026-09-04). Data as JSON: /api/errors/5923811c542a2c68. Report an issue: GitHub.