Unsubscribe

Unsubscribe, thanks.

Re: ON DUPLICATE KEY with Global Index

We do need to update the docs after PHOENIX-3925, which changed the behavior from 'recommended' to 'mandatory'. I'll update the docs now. On Tue, Oct 9, 2018 at 1:08 PM Ankit Singhal wrote: > We do not allow atomic upsert and throw the corresponding exception in the > cases documented under the

Re: ON DUPLICATE KEY with Global Index

Can you elaborate on what is unclear about the documentation? This exception and the related documentation read as being in support of each other to me. On 10/9/18 5:39 AM, Batyrshin Alexander wrote: Hello all, Documentations (http://phoenix.apache.org/atomic_upsert.html) say: "Although

ON DUPLICATE KEY with Global Index

Hello all, Documentations (http://phoenix.apache.org/atomic_upsert.html) say: "Although global indexes on columns being atomically updated are supported, it’s not recommended as a potentially a separate RPC across the wire would be made while the row is under lock to maintain the secondary

Re: Table dead lock: ERROR 1120 (XCL20): Writes to table blocked until index can be updated

I've created bug with reproduce steps: https://issues.apache.org/jira/browse/PHOENIX-4960 > On 3 Oct 2018, at 21:06, Batyrshin Alexander <0x62...@gmail.com> wrote: > > But we see that Phoenix commit() in our cases fails with "ERROR 1120 (XCL20): > Writes to table blocked until index can be