Fix Hive cleanup error: use DROP VIEW when check_timestamps fails #63
+4
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hive throws
WRONG_COMMAND_FOR_OBJECT_TYPEwhen attemptingDROP TABLEon a VIEW during cleanup aftercheck_timestampsfails.Root Cause
In
apply_mapping, whenoutput_file is None:create_materialized_view(line 229-232)create_table(line 234)The exception handler unconditionally used
DROP TABLE, which fails for Hive VIEWs.Changes
src/chronify/time_series_mapper_base.py:149-152
Detect engine type and use appropriate DROP command:
Matches existing pattern in the
finallyblock (line 156-157) and elsewhere in the codebase.Original prompt
This pull request was created from Copilot chat.
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.