Skip to content
TheChatArchiveThe Chat Archive
x-ai/grok-4.5· unknownHugging 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 explore the repository structure and how Glue actions are implemented so I can add BatchDeleteTable support.

  3. Assistant

    I'll inspect GlueService and the handler for how delete/table actions are wired.

  4. Assistant

    Reading GlueService and related tests/patterns for delete and batch operations.

  5. Assistant

    Let me read more of the GlueService especially around deleteTable.

  6. Assistant

    Checking handler patterns and other batch APIs in the codebase:

  7. Assistant

    Reviewing helper methods and similar batch-error response patterns:

  8. Assistant

    I'll inspect ECR batch-delete and end-of-file GlueService helpers for the response pattern.

  9. Assistant

    Implementing batchDeleteTables in GlueService and wiring BatchDeleteTable in the JSON handler.

  10. Assistant

    Let me also check the end of GlueService for existing records.

  11. Assistant

    Adding the service method and wiring the handler.

  12. Assistant

    Now add the record near UserDefinedFunctionPage.

  13. Assistant

    Need to goto that line first.

  14. Assistant

    Now replace.

  15. Assistant

    Updating GlueJsonHandler to handle BatchDeleteTable.

  16. Assistant

    I'll add the case and a private handler method for clarity, following the pattern of other handlers.

  17. Assistant

    Adding the handleBatchDeleteTable method near the other handlers.

  18. Assistant

    Removing the duplicated method signature.

  19. Assistant

    Adding a blank line before the new handler for consistency.

  20. Assistant

    Need to goto first

  21. Assistant

    Let me fix the blank line.

  22. Assistant

    Checking GlueServiceTest setup so I can run a temporary verification.

  23. Assistant

    Running unit tests and a temporary verification for batchDeleteTables.

  24. Assistant

    HOME isn't set — fixing that next.

  25. Assistant

    Checking the test result summary:

  26. Assistant

    Creating a temporary test script to verify batch delete behavior:

  27. Assistant

    Inspecting StorageFactory and how tests construct it:

  28. Assistant

    Compiling and running a temporary verification using the Maven classpath:

  29. Assistant

    Putting the temporary verifier in the test package so package-private constructors work:

  30. Assistant

    All checks passed. Verifying the final diff and cleaning up.

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