Re: optimistic lock in phenix

[James Taylor]

Another option is to upgrade to 4.8 or later and use transactions (which
uses optimistic concurrency under the covers):
https://phoenix.apache.org/transactions.html

Thanks,
James

On Wed, Aug 30, 2017 at 9:53 AM, James Taylor 
wrote:

> Upgrade to 4.9 or later and use our atomic upsert command: http://phoenix.
> apache.org/atomic_upsert.html
>
> On Wed, Aug 30, 2017 at 9:38 AM Pradheep Shanmugam <
> pradheep.shanmu...@infor.com> wrote:
>
>> hi,
>>
>>
>> we have a table in phoenix 4.4 which has a modifyrevision as a column..
>>
>> when a thread updates the row the modifyrevision has to be incremented..
>>
>> only option i can see is to use the upsert select to get the latest
>> revision but since it is not atomic how do we avoid the dirty reads?is
>> there any other way this can be done?
>>
>>
>> Thanks,
>>
>> Pradheep
>>
>

Re: optimistic lock in phenix

[James Taylor]

Upgrade to 4.9 or later and use our atomic upsert command:
http://phoenix.apache.org/atomic_upsert.html

On Wed, Aug 30, 2017 at 9:38 AM Pradheep Shanmugam <
pradheep.shanmu...@infor.com> wrote:

> hi,
>
>
> we have a table in phoenix 4.4 which has a modifyrevision as a column..
>
> when a thread updates the row the modifyrevision has to be incremented..
>
> only option i can see is to use the upsert select to get the latest
> revision but since it is not atomic how do we avoid the dirty reads?is
> there any other way this can be done?
>
>
> Thanks,
>
> Pradheep
>

optimistic lock in phenix

[Pradheep Shanmugam]

hi,


we have a table in phoenix 4.4 which has a modifyrevision as a column..

when a thread updates the row the modifyrevision has to be incremented..

only option i can see is to use the upsert select to get the latest revision 
but since it is not atomic how do we avoid the dirty reads?is there any other 
way this can be done?


Thanks,

Pradheep