Re: Provide an option to infinite retry when updating index failed

We've been doing a ton of work to stabilize mutable secondary indexing recently (see recently resolved JIRAs). This will appear in 4.12.0 or 4.11.1. Also, a lot of work was done for local indexing in 4.11. We're still testing these at scale, so there may be more to come in 4.12 for local indexing

Re: Provide an option to infinite retry when updating index failed

Personally I don't like the idea. If one of the index regions get stuck (in transition for example), the whole cluster will be down after a while. It's better to get this index disabled rather than having cluster not working (until someone noticed that the ingestion rate dropped to zero) and down

[jira] [Resolved] (PHOENIX-4069) When use row timestamp table,del row1 by 'delete from table' , and I get failed by upsert row1 into the table.

[ https://issues.apache.org/jira/browse/PHOENIX-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal resolved PHOENIX-4069. Resolution: Won't Fix > When use row timestamp table,del row1 by 'delete from table' ,

[jira] [Commented] (PHOENIX-4069) When use row timestamp table,del row1 by 'delete from table' , and I get failed by upsert row1 into the table.

[ https://issues.apache.org/jira/browse/PHOENIX-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16119466#comment-16119466 ] Ankit Singhal commented on PHOENIX-4069: It is as per HBase semantics, so if you have row