Skip to content
TheChatArchiveThe Chat Archive
gpt-5.6-luna· openaiHugging Face ibragim-bad/swe_rebench_07_2026_trajectories

ISSUE DESCRIPTION [BUG] Glue BatchDeleteTable is unsupported Service AWS Glue AWS API…

  1. User

    ISSUE DESCRIPTION

    [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.

    ADDITIONAL ADVICE

    Since you are given a git repository, you can use git commands to simplify your work. For example, if you made a mistake and want to revert your changes, you can use git checkout <file> to restore the file to its original state. You can also reset all changes in the repository using git reset --hard command. Additionally, you can use git stash and git stash pop to temporarily save your changes and restore them later. Finally, you can see the changes that you've made (which will be submitted when you call submit) using git status or git diff commands. However you don't need to use git add or git commit before submitting your changes. In fact, submit only submits currently unstaged changes because it uses git diff to get the changes that need to be submitted.

    CHECKLIST

    Before submitting your solution, please go over the following checklist and make sure you've done everything:

    • If an error was reported in the issue description, I have successfully reproduced it.
    • If an error was reported in the issue description, I have confirmed that my fix resolves the error.
    • I have thought about edge cases and made sure my fix handles them as well.
    • I have run existing tests in the repository that might have been affected by the change I made and confirmed that they pass. I want you to list every bullet from this checklist and write your reasoning for why you think you did it or didn't need to.

    Repository has been uploaded and your shell is currently at the repository root. Time to solve the issue!

    (Current directory: /floci, current file: none) bash-$

  2. Assistant

    I’ll trace the Glue service and request routing/handlers, identify how table deletion is currently exposed, then implement the service interface and API action consistently with existing Glue conventions. I’ll run focused tests and inspect the diff before submitting.

  3. Assistant

    The unsupported action is isolated in GlueJsonHandler. I’ll add a service-level result record with the three AWS-relevant error fields, validate the database once, delete only existing tables (including partitions through the existing deletion path), and map missing tables to AWS’s nested ErrorDetail response shape. This preserves the existing single-table behavior while making batch processing partial-success tolerant.

  4. Assistant

    The implementation compiles and the existing GlueServiceTest suite passes. The service normalizes names through tableKey, so mixed-case inputs work; duplicate/missing names are handled independently, and a missing database still raises the normal database error. The response always includes an Errors array, with each missing table represented using TableName and nested ErrorDetail. I’m doing the final diff/status check and then submitting.

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