Skip to content
TheChatArchiveThe Chat Archive
xiaomi/mimo-v2.5-pro· 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 start by exploring the repository to understand its structure and locate the Glue service implementation. Let's first list the root directory.

  3. Assistant

    Let me look at the directory structure more specifically for the Glue service.

  4. Assistant

    Let me look at the GlueService.java file to understand the current implementation and where batchDeleteTable should be added.

  5. Assistant

    Let me look at the GlueService.java file to understand its structure.

  6. Assistant

    Now let me find the API handler/controller for Glue that dispatches API actions:

  7. Assistant

    Let me look at how the Glue API actions are dispatched:

  8. Assistant

    Let me look at the GlueJsonHandler.java to understand how actions are dispatched.

  9. Assistant

    Now I understand the structure. I need to:

    1. Add a BatchDeleteTable case to the GlueJsonHandler.java switch statement
    2. Add a batchDeleteTables method to GlueService.java with a BatchDeleteTableError inner record

    Let me also check how existing tests are structured and look at the GlueServiceTest:

  10. Assistant

    Now I understand the structure. I need to:

    1. Add a batchDeleteTables method to GlueService.java with a BatchDeleteTableError record
    2. Add a BatchDeleteTable case to GlueJsonHandler.java

    Let me first add the BatchDeleteTableError record and batchDeleteTables method to GlueService:

  11. Assistant

    Let me go to the end of the file:

  12. Assistant

    Now let me look at the existing deleteTable method more closely and understand the behavior:

  13. Assistant

    I see the existing deleteTable method doesn't throw an error if the table doesn't exist (it just deletes the key and partitions). This is fine for the regular DeleteTable action, but for BatchDeleteTable, we need to report errors for missing tables.

    Now I need to:

    1. Add a batchDeleteTables method to GlueService that:

      • Takes database name and list of table names
      • For each table, check if it exists
      • If it exists, delete it (including partitions)
      • If it doesn't exist, add an error to the result
      • Return a list of BatchDeleteTableError (empty if all succeed)
    2. Add a BatchDeleteTable case to GlueJsonHandler that calls this method and formats the response.

    Let me also need to add a BatchDeleteTableError record to GlueService.

    Let me implement this step by step. First, I'll add the batchDeleteTables method and the BatchDeleteTableError record to GlueService.

    Now let me look at the AwsJson11Controller to understand how actions are dispatched:

  14. Assistant

    Now I have a good understanding of the codebase. Let me implement the BatchDeleteTable feature. I need to:

    1. Add a batchDeleteTables method and BatchDeleteTableError record to GlueService.java
    2. Add a BatchDeleteTable case to GlueJsonHandler.java

    Let me start with GlueService.java:

  15. Assistant

    Good, now let me add the BatchDeleteTable case to GlueJsonHandler.java:

  16. Assistant

    Now I need to add the BatchDeleteTable case to the switch statement. Let me add it after the DeleteTable case:

  17. Assistant

    Now let me verify the changes compile and the existing tests pass. First, let me build the project:

  18. Assistant

    Let me find the pom.xml to understand the build structure.

  19. Assistant

    Let me try to compile the project using Maven.

  20. Assistant

    Build succeeds. Now let me run the existing Glue tests:

  21. Assistant

    All 24 existing tests pass. Now let me also check the compatibility test for Glue to make sure it still works:

  22. Assistant

    Now let me create a quick test to verify the BatchDeleteTable functionality works correctly. I'll write a simple test that verifies:

    1. Deleting existing tables works
    2. Deleting missing tables returns errors
    3. The combination of existing and missing tables works correctly

    Let me create a temporary test script.

  23. Assistant

    Let me verify the implementation by examining the logic more carefully. Let me look at the code I wrote:

  24. Assistant

    Let me verify the GlueJsonHandler changes:

  25. Assistant

    Now let me check if the AWS Glue action mapping in the service catalog recognizes BatchDeleteTable. Let me look at how actions are registered:

  26. Assistant

    Let me check how the service catalog works to see if it might need registration:

  27. Assistant

    Let me check the service catalog to understand how actions are routed.

  28. Assistant

    Let me check the service descriptor for Glue to understand the target prefix:

  29. Assistant

    Good. I can see that for Glue, the target prefix is "AWSGlue.". So the target header would be "AWSGlue.BatchDeleteTable", and the action extracted would be "BatchDeleteTable". The switch statement in GlueJsonHandler handles this action correctly.

    Now let me run all the Glue tests to make sure everything passes:

  30. Assistant

    All 34 tests pass. Let me verify my changes look correct by reviewing the diff:

  31. Assistant

    The implementation looks good. Let me also run a broader set of tests to make sure nothing is broken:

  32. Assistant

    All 152 Glue-related tests pass. Let me now verify the changes one more time by looking at the final state of both files:

  33. Assistant

    Let me clean up the temporary test file and then submit:

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