Lokesh Khurana created PHOENIX-7912:
---------------------------------------
Summary: PAUSED + FAILED states clear dual-write attribution;
explicit monitor branch
Key: PHOENIX-7912
URL: https://issues.apache.org/jira/browse/PHOENIX-7912
Project: Phoenix
Issue Type: Sub-task
Reporter: Lokesh Khurana
Pause variants (create-paused via {{INDEX_CREATE_DEFAULT_STATE = CREATE_DISABLE
}}and pause-after-start via {{{}pauseTransform{}}}) leave
{{TRANSFORMING_NEW_TABLE }}link installed. Stale-cache clients keep attaching
{{TransformMaintainer}} and dual-writing to a paused/{{{}CREATE_DISABLE{}}}
shadow; mutations fail or are silently ignored. Same hole exists in FAILED
state.
*Decision:*
* Both pause variants clear the link on transition to PAUSED. Resume
re-installs.
* FAILED state gets the same treatment (link cleared on transition to FAILED,
re-installed on resume).
* New ALTER on a create-paused: implicit-abandon with WARN log.
* FAILED state symmetrical with PAUSED.
* Drop strategy when abandoning create-paused: inline drop (no UCF wait
needed; never accepted writes) .
* TransformMonitorTask's "skip if paused/failed" branch is made explicit
(named branch + log line).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
