Skip to content
TheChatArchiveThe Chat Archive
composer-2.5· unknownHugging Face ibragim-bad/swe_rebench_07_2026_trajectories

Untitled conversation

  1. User

    [BUG] Glue BatchDeleteTable is unsupported

    Service

    AWS Glue

    AWS API Action

    BatchDeleteTable

    Expected behavior

    AWS behavior supports BatchDeleteTable. When the request contains one existing table and one missing table, AWS deletes the existing table and returns an Errors entry for the missing table.

    AWS behavior verified with AWS CLI:

    {
        "Errors": [
            {
                "TableName": "missing_table",
                "ErrorDetail": {
                    "ErrorCode": "EntityNotFoundException",
                    "ErrorMessage": "Table missing_table not found"
                }
            }
        ]
    }
    

    A subsequent GetTable for the existing table returns EntityNotFoundException.

    Actual behavior

    Floci floci/floci:1.5.22 rejects BatchDeleteTable as an unsupported action.

    aws: [ERROR]: An error occurred (InvalidAction) when calling the BatchDeleteTable operation: Action BatchDeleteTable is not supported
    

    Reproduction

    endpoint=http://localhost:4566
    export AWS_ACCESS_KEY_ID=<redacted-secret> AWS_SECRET_ACCESS_KEY=<redacted-secret> AWS_DEFAULT_REGION=us-east-1
    db=test_floci_batch_delete
    
    aws --endpoint-url "$endpoint" glue create-database --database-input "Name=$db"
    aws --endpoint-url "$endpoint" glue create-table \
      --database-name "$db" \
      --table-input 'Name=existing_table,StorageDescriptor={Columns=[{Name=id,Type=int}]}'
    aws --endpoint-url "$endpoint" glue batch-delete-table \
      --database-name "$db" \
      --tables-to-delete existing_table missing_table
    

    Environment

    • Floci version / image tag: floci/floci:1.5.22
    • Java SDK version (if applicable): AWS CLI
    • How you're running Floci (Docker / native / mvn quarkus:dev): Docker

    Interface

    Type: Function Name: batchDeleteTables Path: src/main/java/io/github/hectorvent/floci/services/glue/GlueService.java Input: String databaseName, List tableNames Output: List<GlueService.BatchDeleteTableError> Description: Deletes multiple tables by name within a database, skipping and reporting errors for any tables that are not found. Use this to process the BatchDeleteTable AWS Glue API action.

  2. Assistant

    I'll implement BatchDeleteTable for Glue by following existing Glue patterns—starting with the service, controller, and similar batch operations.

  3. Assistant

    Implementing batchDeleteTables in the service and wiring it through the JSON handler.

  4. Assistant

    Implemented BatchDeleteTable support for Glue.

    Changes

    GlueService.batchDeleteTables — Deletes existing tables in a database and collects per-table errors for missing ones, matching AWS behavior:

    • Validates the database exists (throws EntityNotFoundException if missing)
    • Deletes found tables (including partitions)
    • Returns BatchDeleteTableError entries for missing tables with EntityNotFoundException and message Table {name} not found

    GlueJsonHandler — Added BatchDeleteTable action handler that reads DatabaseName and TablesToDelete, then returns the AWS-shaped response:

    {
      "Errors": [
        {
          "TableName": "missing_table",
          "ErrorDetail": {
            "ErrorCode": "EntityNotFoundException",
            "ErrorMessage": "Table missing_table not found"
          }
        }
      ]
    }
    

    Tests — Three unit tests cover the mixed success/error case, all-success case, and missing-database case.

    Docs — Updated docs/services/glue.md to list BatchDeleteTable.

    Your reproduction scenario should now work: existing_table is deleted, missing_table appears in Errors, and a follow-up GetTable on existing_table returns EntityNotFoundException.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.