Untitled conversation
- User
[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. - Floci version / image tag:
- Assistant
I'll locate the Glue service implementation and see how similar batch operations are wired so we can add
BatchDeleteTable. - Assistant
Implementing
batchDeleteTablesin the service and wiring it through the JSON handler. - Assistant
Implemented
BatchDeleteTablesupport for AWS Glue.Changes
-
GlueService.batchDeleteTables— Deletes existing tables (including partitions) and collects per-table errors for missing tables without failing the whole request. Verifies the database exists first. -
GlueJsonHandler— AddedBatchDeleteTablehandler that readsDatabaseNameandTablesToDelete, returning AWS-shapedErrorswithTableNameandErrorDetail(ErrorCode,ErrorMessage). -
Tests — Unit tests in
GlueServiceTestand an integration test inGlueBatchDeleteTableIntegrationTestcovering the reported scenario.
Behavior (matches AWS)
- One existing + one missing table → existing table deleted, missing table reported in
Errors - Error format:
EntityNotFoundExceptionwith messageTable {name} not found - Case-insensitive table lookup; error responses use the requested table name
- Subsequent
GetTableon the deleted table returnsEntityNotFoundException
Your reproduction flow should now work against a build that includes this change.
-
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
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- fable-5Compare side by side →
- fable-5Compare side by side →