In this case, it means "overwrite with new value without reading".
On Wednesday, November 2, 2016 at 8:52:17 PM UTC-4, pdknsk wrote:
>
> > At the moment I can't see how to apply transactions.
>
> It depends on whether update means "read, change value, write back" or
> "overwrite with new value
ng some weird 0.01% edge behavior.
>
> Transactions are the only way to guarantee that get/update/put cycles have
> the effect you think they do. This is the first thing I would fix before
> trying anything else.
>
> Jeff
>
> On Tue, Nov 1, 2016 at 5:42 PM, Jonathan Munson
Good thought, but in this case only one user can update the entity.
On Tuesday, November 1, 2016 at 6:13:13 PM UTC-4, pdknsk wrote:
>
> If more than one user can update the same entity, the bug may be that
> you're not updating the entity atomically (as in a transaction).
>
--
You received
you schedule
> your hand-off to Java after the transaction has committed?
>
> On Monday, October 31, 2016 at 10:54:28 PM UTC-5, Jonathan Munson wrote:
>>
>> I don't believe I use Objectify, unless it's used transparently by the
>> Java Datastore API. Here's a snipp
Jeff's response. Objectify and NDB
>> do not use the same entries in Memcache. So while NDB on Python
>> invalidated *its* cache entry, Objectify used a different namespace and
>> thus the Objectify cached entry is still there.
>>
>> On Monday, October 31, 201
on is already a hard problem (that and naming things, as
> they say). If you want to access data from both python and java, best to
> disable the memcache behavior of both NDB and Objectify (don’t put @Cache
> on anything shared).
>
> Jeff
>
> On Mon, Oct 31, 2016 at 2:01
va cache may return a stale result because the
>> Python module didn't clear/update the entity on write.
>>
>> On Monday, October 31, 2016 at 8:41:07 AM UTC-5, Jonathan Munson wrote:
>>>
>>> Hi,
>>>
>>> We have an app wherein a Datastore entity
Hi,
We have an app wherein a Datastore entity is written to by a Python module
(using NDB), and then in an immediately following request, read from, using
the entity's key, by a Java module. In a situation where the app was
heavily loaded, it seemed like the Java module was reading stale data.
