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 locate the Glue service implementation and see how similar batch operations are wired so we can add BatchDeleteTable.

  3. Assistant

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

  4. Assistant

    Implemented BatchDeleteTable support for AWS Glue.

    Changes

    1. GlueService.batchDeleteTables — Deletes existing tables (including partitions) and collects per-table errors for missing tables without failing the whole request. Verifies the database exists first.

    2. GlueJsonHandler — Added BatchDeleteTable handler that reads DatabaseName and TablesToDelete, returning AWS-shaped Errors with TableName and ErrorDetail (ErrorCode, ErrorMessage).

    3. Tests — Unit tests in GlueServiceTest and an integration test in GlueBatchDeleteTableIntegrationTest covering the reported scenario.

    Behavior (matches AWS)

    • One existing + one missing table → existing table deleted, missing table reported in Errors
    • Error format: EntityNotFoundException with message Table {name} not found
    • Case-insensitive table lookup; error responses use the requested table name
    • Subsequent GetTable on the deleted table returns EntityNotFoundException

    Your reproduction flow should now work against a build that includes this change.

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