Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: <CAKr8Lfyk1bqGr9j4G_7ZDC69j8+DvGD3VgZ8CbsTawtOQn84ng@mail.gmail.com>
References: <CAKr8Lfwd=p6AtqFu+jucyyAm8R0jRVuRpf2ZQkAgHcqpZ7Z__g@mail.gmail.com>
 <CAO=R_k58ZZY0OVyAMG6Cy4CeAwjHwGWxi5mOtOOAuGdkA=DvEQ@mail.gmail.com> <CAKr8Lfyk1bqGr9j4G_7ZDC69j8+DvGD3VgZ8CbsTawtOQn84ng@mail.gmail.com>
From: Alexey Goncharuk <alexey.goncharuk@gmail.com>
Date: Thu, 30 Mar 2017 11:55:35 +0300
Message-ID: <CABDss3hVfj-SJz2XaHxQkVWpQ+314LZVAJKjuZZxDdb-n9+PXw@mail.gmail.com>
Subject: Re: putting entity into cache while commiting.Why!?
To: dev@ignite.apache.org
Content-Type: multipart/alternative; boundary=94eb2c0b61743e4fd3054beedbca
archived-at: Thu, 30 Mar 2017 08:55:41 -0000

--94eb2c0b61743e4fd3054beedbca
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Can you please paste the full example?

2017-03-30 11:50 GMT+03:00 ALEKSEY KUZNETSOV <alkuznetsov.sb@gmail.com>:

> But i managed to read dirty. That is my example :
>
> Ignite ignite0 =3D ignite(0);
> IgniteTransactions transactions =3D ignite0.transactions();
> IgniteCache<String, String> cache =3D ignite0.getOrCreateCache("testCache=
");
> Object monitor =3D new Object();
>
> GridTestUtils.runAsync(new Callable<Object>() {
>     @Override
>     public Object call() throws Exception {
>         synchronized (monitor){
>             doInTransaction(ignite(1), new Callable<Object>() {
>                 @Override
>                 public Object call() throws Exception {
>                     cache.put("key1", "val1");
>                     monitor.wait();
>                     return null;
>                 }
>             });
>         }
>         return null;
>     }
> });
>
> Transaction tx =3D
> transactions.txStart(TransactionConcurrency.OPTIMISTIC,
> TransactionIsolation.READ_COMMITTED);
> cache.put("key1", "val1");
>
> And through debugging cache.put() method i can see in method
> *org.apache.ignite.internal.processors.cache.distributed.
> near.GridNearTxLocal#enlistWriteEntry*
> that "key1" already *EXISTS *in internal cache : cacheCtx.cache().entryEx=
()
> returns not null.
>
> =D1=81=D1=80, 29 =D0=BC=D0=B0=D1=80. 2017 =D0=B3. =D0=B2 20:11, Alexander=
 Fedotov <
> alexander.fedotoff@gmail.com
> >:
>
> Hello Aleksey,
>
> No, the enlisted entry won't be visible for other transactions. Dirty rea=
ds
> are not allowed in Ignite.
>
> Kind regards,
> Alex
>
> 29 =D0=BC=D0=B0=D1=80=D1=82=D0=B0 2017 =D0=B3. 7:36 PM =D0=BF=D0=BE=D0=BB=
=D1=8C=D0=B7=D0=BE=D0=B2=D0=B0=D1=82=D0=B5=D0=BB=D1=8C "ALEKSEY KUZNETSOV" =
<
> alkuznetsov.sb@gmail.com> =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB:
>
> Hello, Igniters! I have one more question to you. Will appreciate any hel=
p.
> Consider cache with near , dht configured not null.
> When we start commit transaction , in method
> *org.apache.ignite.internal.processors.cache.distributed.
> near.GridNearTxLocal#enlistWriteEntry*
> we put newly created entry into cache by executing entryEx().
> I wonder if this entry will became visible for other transactions!?
> --
>
> *Best Regards,*
>
> *Kuznetsov Aleksey*
>
> --
>
> *Best Regards,*
>
> *Kuznetsov Aleksey*
>

--94eb2c0b61743e4fd3054beedbca--