ISSUE DESCRIPTION [BUG] Glue BatchDeleteTable is unsupported Service AWS Glue AWS API…
- User
ISSUE DESCRIPTION
[BUG] Glue BatchDeleteTable is unsupported
Service
AWS API Action
Expected behavior
AWS behavior supports
BatchDeleteTable. When the request contains one existing table and one missing table, AWS deletes the existing table and returns anErrorsentry 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
GetTablefor the existing table returnsEntityNotFoundException.Actual behavior
Floci
floci/floci:1.5.22rejectsBatchDeleteTableas an unsupported action.aws: [ERROR]: An error occurred (InvalidAction) when calling the BatchDeleteTable operation: Action BatchDeleteTable is not supportedReproduction
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_tableEnvironment
- 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
BatchDeleteTableAWS 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 usinggit reset --hardcommand. Additionally, you can usegit stashandgit stash popto temporarily save your changes and restore them later. Finally, you can see the changes that you've made (which will be submitted when you callsubmit) usinggit statusorgit diffcommands. However you don't need to usegit addorgit commitbefore submitting your changes. In fact,submitonly submits currently unstaged changes because it usesgit diffto 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-$
- Floci version / image tag:
Assistant
I'll start by exploring the repository structure to understand how the codebase is organized and then implement the
BatchDeleteTablefunctionality for AWS Glue.Assistant
Let me start by examining the GlueService.java file to understand the current implementation and how other operations are implemented.
Assistant
I need to use the correct tool call format. Let me open the GlueService.java file to understand the current implementation.
Assistant
Now let me check the GlueJsonHandler to see how the API endpoints are mapped:
Assistant
Now let me check the existing tests to understand the expected behavior better:
Assistant
Now let me check the structure of the Table and Database models:
Assistant
Now I understand the structure. Let me create a test script to reproduce the error first:
Assistant
Let me explore how tests are run in this project:
Assistant
Good, it's a Maven project. Let me run the existing Glue tests first to understand the baseline:
Assistant
Tests are passing. Now let me implement the
BatchDeleteTablefunctionality. Based on the issue description and the existing code structure, I need to:- Add a
batchDeleteTablesmethod toGlueService.java - Add a handler for "BatchDeleteTable" action in
GlueJsonHandler.java
Let me start by implementing the service method:
- Add a
Assistant
Now let me add this method to the GlueService.java file. I'll add it right after the
deleteTablemethod:Assistant
Now I'll add the batchDeleteTables method after deleteTable:
Assistant
Let me use a different approach with sed:
Assistant
Now let me verify the changes were applied correctly:
Assistant
Good! Now I need to add the handler for "BatchDeleteTable" action in GlueJsonHandler.java. Let me find where DeleteTable is handled:
Assistant
Now I'll add the BatchDeleteTable handler right after DeleteTable:
Assistant
Now I need to add the handler method. Let me find a good location for it, perhaps after the handleDeleteUserDefinedFunction method:
Assistant
Now I'll add the handleBatchDeleteTable method after handleDeleteUserDefinedFunction:
Assistant
Let me verify the changes to GlueJsonHandler.java:
Assistant
I see there's a formatting issue - there's a missing closing brace and an extra closing brace. Let me fix this:
Assistant
I see the issue - the closing brace is missing from the previous method. Let me check the whole section:
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:
Assistant
There's an extra closing brace. Let me remove it:
Assistant
Let me verify the fix:
Assistant
Perfect! Now let me run the tests to make sure the code compiles and existing tests still pass:
Assistant
Great! The tests passed. Now let me create a test script to verify the BatchDeleteTable functionality works as expected:
Assistant
Now let me run the test to verify the batchDeleteTables functionality works:
Assistant
I need to add the Map import:
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:
Assistant
Perfect! Now let me run all the existing Glue tests to make sure I didn't break anything:
Assistant
Let me remove the test files I created since the instructions say not to modify tests:
Assistant
I need to verify the changes I made and ensure everything compiles correctly. Let me check the final state of the files.
Assistant
Good, the compilation succeeded. Let me run all the Glue tests to make sure I didn't break anything.
Assistant
The grep didn't find anything. Let me try a different approach to check if the tests passed.
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.
Assistant
The diff looks good for GlueService.java. Let me check the GlueJsonHandler.java changes.
Assistant
Let me verify the complete implementation by running all the tests:
Assistant
Let me verify the final state of my changes:
Assistant
Let me verify the implementation one more time by checking the complete diff:
Assistant
Perfect! Now let me verify everything compiles and passes tests. Let me run all Glue-related tests to make sure nothing is broken.
Assistant
Now let me create a simple test script to verify the behavior matches the expected AWS behavior described in the issue:
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.
Identical first prompt
claude-sonnet-5Compare side by side →
claude-sonnet-5Compare side by side →
claude-sonnet-5Compare side by side →
claude-sonnet-5Compare side by side →
claude-sonnet-5Compare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-27BCompare side by side →
Qwen/Qwen3.6-27BCompare side by side →