prestodb/presto · error · ParseError
{parse_error} InputDistribution InputDistribution
Error message
{parse_error} InputDistribution InputDistribution What it means
Velox protocol deserialization error: extracting the subclass key of an InputDistribution from JSON threw a parse error. from_json wraps the json::parse_error with the InputDistribution tag, indicating a malformed serialized input-distribution entry in the plan fragment.
Source
Thrown at presto-native-execution/presto_cpp/presto_protocol/core/presto_protocol_core.cpp:3861
if (p == nullptr) {
return;
}
String type = p->_type;
if (type == ".BaseInputDistribution") {
j = *std::static_pointer_cast<BaseInputDistribution>(p);
return;
}
throw TypeError(type + " no abstract type InputDistribution ");
}
void from_json(const json& j, std::shared_ptr<InputDistribution>& p) {
String type;
try {
type = p->getSubclassKey(j);
} catch (json::parse_error& e) {
throw ParseError(
std::string(e.what()) + " InputDistribution InputDistribution");
}
if (type == ".BaseInputDistribution") {
std::shared_ptr<BaseInputDistribution> k =
std::make_shared<BaseInputDistribution>();
j.get_to(*k);
p = std::static_pointer_cast<InputDistribution>(k);
return;
}
throw TypeError(type + " no abstract type InputDistribution ");
}
} // namespace facebook::presto::protocol
namespace facebook::presto::protocol {
DeleteNode::DeleteNode() noexcept {
_type = ".DeleteNode";
}View on GitHub (pinned to 55bb57d202)
Solutions
- Verify the serialized JSON contains the expected type field
- Match Java and native protocol definitions for InputDistribution
- Re-run without native execution to isolate the protocol mismatch
Defensive patterns
Strategy: try-catch
When it happens
Trigger: Thrown at presto-native-execution/presto_cpp/presto_protocol/core/presto_protocol_core.cpp:3861 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of prestodb/presto@55bb57d202 (2026-09-04).
Data as JSON: /api/errors/cadc36cbc535d5e6.
Report an issue: GitHub.