slug: hadoop
provider: Apache Hadoop
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 2
edges:
- tag: WebHDFS
  spec_file: hadoop-webhdfs-api-openapi.yml
  capability_id: BC-600.50
  capability_id_l1: BC-600
  capability_name: IT Infrastructure Management
  confidence: 0.7
  evidence: 'GET /webhdfs/v1/{path} WebHDFS GET operations; description: ''Includes WebHDFS for filesystem
    operations'''
  reason: WebHDFS exposes distributed filesystem read/write/delete operations on HDFS storage — platform
    storage infrastructure, i.e. IT Infrastructure Management. It is a devtool/infrastructure surface,
    not a data-governance one.
- tag: YARN Applications
  spec_file: hadoop-yarn-applications-api-openapi.yml
  capability_id: BC-600
  capability_id_l1: BC-600
  capability_name: Information Technology Management
  confidence: 0.7
  evidence: POST /ws/v1/cluster/apps Submit a new application; PUT /ws/v1/cluster/apps/{appid}/queue Move
    application to a different queue
  reason: Submitting and controlling the state, queue and priority of distributed compute workloads is
    IT platform/workload operations. Kept at L1 because the evidence does not cleanly separate IT Operations
    from IT Infrastructure Management.