Skip to content
TheChatArchiveThe Chat Archive
QwenQwen/Qwen3.6-27B· alibabaHugging 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. Qwen Assistant

    I'll start by exploring the repository structure to understand how the codebase is organized and then implement the BatchDeleteTable functionality for AWS Glue.

  3. Qwen Assistant

    Let me start by examining the GlueService.java file to understand the current implementation and how other operations are implemented.

  4. Qwen Assistant

    I need to use the correct tool call format. Let me open the GlueService.java file to understand the current implementation.

  5. Qwen Assistant

    Now let me check the GlueJsonHandler to see how the API endpoints are mapped:

  6. Qwen Assistant

    Now let me check the existing tests to understand the expected behavior better:

  7. Qwen Assistant

    Now let me check the structure of the Table and Database models:

  8. Qwen Assistant

    Now I understand the structure. Let me create a test script to reproduce the error first:

  9. Qwen Assistant

    Let me explore how tests are run in this project:

  10. Qwen Assistant

    Good, it's a Maven project. Let me run the existing Glue tests first to understand the baseline:

  11. Qwen Assistant

    Tests are passing. Now let me implement the BatchDeleteTable functionality. Based on the issue description and the existing code structure, I need to:

    1. Add a batchDeleteTables method to GlueService.java
    2. Add a handler for "BatchDeleteTable" action in GlueJsonHandler.java

    Let me start by implementing the service method:

  12. Qwen Assistant

    Now let me add this method to the GlueService.java file. I'll add it right after the deleteTable method:

  13. Qwen Assistant

    Now I'll add the batchDeleteTables method after deleteTable:

  14. Qwen Assistant

    Let me use a different approach with sed:

  15. Qwen Assistant

    Now let me verify the changes were applied correctly:

  16. Qwen Assistant

    Good! Now I need to add the handler for "BatchDeleteTable" action in GlueJsonHandler.java. Let me find where DeleteTable is handled:

  17. Qwen Assistant

    Now I'll add the BatchDeleteTable handler right after DeleteTable:

  18. Qwen Assistant

    Now I need to add the handler method. Let me find a good location for it, perhaps after the handleDeleteUserDefinedFunction method:

  19. Qwen Assistant

    Now I'll add the handleBatchDeleteTable method after handleDeleteUserDefinedFunction:

  20. Qwen Assistant

    Let me verify the changes to GlueJsonHandler.java:

  21. Qwen Assistant

    I see there's a formatting issue - there's a missing closing brace and an extra closing brace. Let me fix this:

  22. Qwen Assistant

    I see the issue - the closing brace is missing from the previous method. Let me check the whole section:

  23. Qwen Assistant

    I see the problem. The closing brace for the first method is missing and there's an extra closing brace at the end. Let me fix this:

  24. Qwen Assistant

    There's an extra closing brace. Let me remove it:

  25. Qwen Assistant

    Let me verify the fix:

  26. Qwen Assistant

    Perfect! Now let me run the tests to make sure the code compiles and existing tests still pass:

  27. Qwen Assistant

    Great! The tests passed. Now let me create a test script to verify the BatchDeleteTable functionality works as expected:

  28. Qwen Assistant

    Now let me run the test to verify the batchDeleteTables functionality works:

  29. Qwen Assistant

    I need to add the Map import:

  30. Qwen Assistant

    Excellent! All tests passed. Now let me also test the JSON handler to make sure the API endpoint works correctly. Let me create a test for the JSON handler:

  31. Qwen Assistant

    Perfect! Now let me run all the existing Glue tests to make sure I didn't break anything:

  32. Qwen Assistant

    Let me remove the test files I created since the instructions say not to modify tests:

  33. Qwen Assistant

    I need to verify the changes I made and ensure everything compiles correctly. Let me check the final state of the files.

  34. Qwen Assistant

    Good, the compilation succeeded. Let me run all the Glue tests to make sure I didn't break anything.

  35. Qwen Assistant

    The grep didn't find anything. Let me try a different approach to check if the tests passed.

  36. Qwen Assistant

    Great! The tests are passing. Let me verify my implementation by reviewing the changes I made and comparing them to the expected AWS behavior described in the issue.

  37. Qwen Assistant

    The diff looks good for GlueService.java. Let me check the GlueJsonHandler.java changes.

  38. Qwen Assistant

    Let me verify the complete implementation by running all the tests:

  39. Qwen Assistant

    Let me verify the final state of my changes:

  40. Qwen Assistant

    Let me verify the implementation one more time by checking the complete diff:

  41. Qwen Assistant

    Perfect! Now let me verify everything compiles and passes tests. Let me run all Glue-related tests to make sure nothing is broken.

  42. Qwen Assistant

    Now let me create a simple test script to verify the behavior matches the expected AWS behavior described in the issue:

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