Alexey Goncharuk created IGNITE-5797:
Summary: Add latency tracing capability for cache operations
Key: IGNITE-5797
URL: https://issues.apache.org/jira/browse/IGNITE-5797
Project: Ignite
Alexey Goncharuk created IGNITE-5774:
Summary: Print more information about long partition release future
Key: IGNITE-5774
URL: https://issues.apache.org/jira/browse/IGNITE-5774
Project: Ignite
Alexey Goncharuk created IGNITE-5772:
Summary: Race between WAL segment rollover and concurrent log
Key: IGNITE-5772
URL: https://issues.apache.org/jira/browse/IGNITE-5772
Project: Ignite
Alexey Goncharuk created IGNITE-5757:
Summary: RENT partition state is set before exchange is completed
Key: IGNITE-5757
URL: https://issues.apache.org/jira/browse/IGNITE-5757
Project: Ignite
Alexey Goncharuk created IGNITE-5686:
Summary: Endless partition eviction during node shutdown
Key: IGNITE-5686
URL: https://issues.apache.org/jira/browse/IGNITE-5686
Project: Ignite
Alexey Goncharuk created IGNITE-5662:
Summary: Primary index name should contain type ID or name
Key: IGNITE-5662
URL: https://issues.apache.org/jira/browse/IGNITE-5662
Project: Ignite
Alexey Goncharuk created IGNITE-5613:
Summary: AtomicSequence usage inside transactions may cause
deadlock
Key: IGNITE-5613
URL: https://issues.apache.org/jira/browse/IGNITE-5613
Project: Ignite
Alexey Goncharuk created IGNITE-5593:
Summary: Affinity change message leak on massive topology updates
Key: IGNITE-5593
URL: https://issues.apache.org/jira/browse/IGNITE-5593
Project: Ignite
Alexey Goncharuk created IGNITE-5580:
Summary: Improve node failure cause information
Key: IGNITE-5580
URL: https://issues.apache.org/jira/browse/IGNITE-5580
Project: Ignite
Issue Type
Alexey Goncharuk created IGNITE-5579:
Summary: Make sure identical binary metadata updates from the same
node do not happen twice
Key: IGNITE-5579
URL: https://issues.apache.org/jira/browse/IGNITE-5579
Alexey Goncharuk created IGNITE-5578:
Summary: Discovery events coalescing
Key: IGNITE-5578
URL: https://issues.apache.org/jira/browse/IGNITE-5578
Project: Ignite
Issue Type: Improvement
Alexey Goncharuk created IGNITE-5569:
Summary: TCP Discovery SPI allows multiple NODE_JOINED /
NODE_FAILED leading to a cluster DDoS
Key: IGNITE-5569
URL: https://issues.apache.org/jira/browse/IGNITE-5569
Alexey Goncharuk created IGNITE-5564:
Summary: Race between read-through and topology version update
Key: IGNITE-5564
URL: https://issues.apache.org/jira/browse/IGNITE-5564
Project: Ignite
Alexey Goncharuk created IGNITE-5562:
Summary: Assertions in TCP discovery SPI when NTP is moving time
backwards
Key: IGNITE-5562
URL: https://issues.apache.org/jira/browse/IGNITE-5562
Project
Alexey Goncharuk created IGNITE-5561:
Summary: Warn about long-running cache store operations
Key: IGNITE-5561
URL: https://issues.apache.org/jira/browse/IGNITE-5561
Project: Ignite
Alexey Goncharuk created IGNITE-5560:
Summary: A failed service must be redeployed when possible
Key: IGNITE-5560
URL: https://issues.apache.org/jira/browse/IGNITE-5560
Project: Ignite
Alexey Goncharuk created IGNITE-5558:
Summary: Add ability to read WAL outside of an Ignite node
Key: IGNITE-5558
URL: https://issues.apache.org/jira/browse/IGNITE-5558
Project: Ignite
Alexey Goncharuk created IGNITE-5554:
Summary: ServiceProcessor may process failed reassignments in
timeout thread
Key: IGNITE-5554
URL: https://issues.apache.org/jira/browse/IGNITE-5554
Project
Alexey Goncharuk created IGNITE-5552:
Summary: ServiceProcessor recalculates all service assignments
even if there is a pending topology change
Key: IGNITE-5552
URL: https://issues.apache.org/jira/browse
Alexey Goncharuk created IGNITE-5551:
Summary: Optimize service deployment assignments object
Key: IGNITE-5551
URL: https://issues.apache.org/jira/browse/IGNITE-5551
Project: Ignite
Alexey Goncharuk created IGNITE-5528:
Summary: IS_EVICT_DISABLED flag is not cleared when cache store
throws an exception
Key: IGNITE-5528
URL: https://issues.apache.org/jira/browse/IGNITE-5528
Alexey Goncharuk created IGNITE-5521:
Summary: Large near caches lead to cluster instability with
metrics enabled
Key: IGNITE-5521
URL: https://issues.apache.org/jira/browse/IGNITE-5521
Project
Alexey Goncharuk created IGNITE-5496:
Summary: Externalizable classes get registered twice
Key: IGNITE-5496
URL: https://issues.apache.org/jira/browse/IGNITE-5496
Project: Ignite
Issue
Alexey Goncharuk created IGNITE-5473:
Summary: Create ignite troubleshooting logger
Key: IGNITE-5473
URL: https://issues.apache.org/jira/browse/IGNITE-5473
Project: Ignite
Issue Type
still used and in particular we depend on it in
> IGFS inetrnals. It will require some time to refactor IGFS.
> Let's just throw an exception if both AffinityKeyMapper and affinity fields
> mappings are defined?
>
> On Thu, Jun 8, 2017 at 3:45 PM, Alexey Goncharuk <
Vladimir,
Your concerns sound reasonable to me. However, I have a feeling that there
was a specific reason why added CacheKeyConfiguration to the
IgniteConfiguration and not to the CacheConfiguration. Looks like indeed,
our original approach is not flexible enough anymore and I am +1 for the
sugge
Hi Alexey,
I've added you to the contributors' list. Please assign the issue to
yourself.
--AG
2017-06-07 14:47 GMT+03:00 Alexey Ivanov :
> Hi, everybody
>
> I'd like fix this issue:
>
> https://issues.apache.org/jira/browse/IGNITE-5432
>
> Alexey Ivanov (a1vanov)
>
>
Denis,
Thanks for the review. I addressed your comments and merged the changes to
ignite-5267 branch.
2017-06-06 22:56 GMT+03:00 Denis Magda :
> > On Jun 5, 2017, at 8:02 PM, Konstantin Boudnik wrote:
> >
> > On Mon, Jun 05, 2017 at 07:41PM, Dmitriy Setrakyan wrote:
> >> On Mon, Jun 5, 2017 at
I am currently in the middle of the debugging - the issue does not look
related to the persistent store changes now.
2017-06-07 5:47 GMT+03:00 Dmitriy Setrakyan :
> On Tue, Jun 6, 2017 at 1:21 AM, Semyon Boikov
> wrote:
>
> > Does anybody monitor TeamCity for ignite-5267? I see suite 'Ignite PDS
Alexey Goncharuk created IGNITE-5427:
Summary: Add cluster activation/deactivation events
Key: IGNITE-5427
URL: https://issues.apache.org/jira/browse/IGNITE-5427
Project: Ignite
Issue
Hi Semyon,
Given that both ServiceDescriptors and service assignments are stored in
the system cache, services should survive the cluster restart, but this
needs to be double-checked because service assignments become obsolete and
need to be fully recalculated.
I will check this and give an updat
Guyd,
I've extended the set of metrics a little bit and pushed my changes to
ignite-5375 branch. Can you please review the metrics and see if we are now
ok with the interfaces?
2017-06-01 21:04 GMT+03:00 Denis Magda :
> Sergey, thanks,
>
> You get a green light from my side. Please go ahead and
Alexey Goncharuk created IGNITE-5398:
Summary: Optimize allocations in RendezvousAffinityFunction
Key: IGNITE-5398
URL: https://issues.apache.org/jira/browse/IGNITE-5398
Project: Ignite
Dmitriy,
The original idea behind moving persistence to a separate module was
easiness of review and the fact that it is likely that in the future it
will have some external dependencies. I guess we can have those
dependencies as a separate module and move persistence to the core module.
2017-06-
Alexey Goncharuk created IGNITE-5395:
Summary: Move ignite-ps module to ignite-core
Key: IGNITE-5395
URL: https://issues.apache.org/jira/browse/IGNITE-5395
Project: Ignite
Issue Type
soon". We never add suche messages without reference to JIRA issue, please
> fix.
>
> Thanks!
>
> On Thu, Jun 1, 2017 at 7:22 PM, Alexey Goncharuk <
> alexey.goncha...@gmail.com
> > wrote:
>
> > Guys,
> >
> > I merged recent changes from the master
Guys,
I merged recent changes from the master branch (SQL-related changes) to the
integration branch, we need another TC run to see if the merge broke
something.
2017-06-01 19:14 GMT+03:00 Dmitriy Setrakyan :
> BTW, can anyone explain to me why do we keep the new persistence code in a
> separate
I do not like this change - we intentionally separated a few properties in
AtomicConfiguration that make sense for Atomics, there is not need to get
back to cache configuration again. In my understanding, we only need to add
groupName to Atomics and Collection configuration.
Thoughts?
2017-06-01
Same think stays for the full-text indexes which are currently stored in
Lucene.
2017-05-24 21:56 GMT+03:00 Dmitriy Setrakyan :
> Sergi,
>
> While we are figuring this out, what happens to the GeoSpatial
> functionality in the mean time? Is it going to work at all? If not, should
> we throw some
I am fine with this javadoc change as long as there is no confusion between
Ignite page memory buffers and the OS Virtual Memory concept.
2017-06-01 2:07 GMT+03:00 Dmitriy Setrakyan :
> Igniters,
>
> With the newly donated persistence functionality in Ignite, I have been
> struggling a bit on how
Aleksey,
Generally, this decision cannot be made on a single node because a
transaction may affect multiple nodes, and one node may have already
committed the transaction and the other - not. There is a dependant ticket
in the ticket you are currently working on which will cover all the caes.
Mea
Alexey Goncharuk created IGNITE-5324:
Summary: Move volatile data structures into a separate cache
Key: IGNITE-5324
URL: https://issues.apache.org/jira/browse/IGNITE-5324
Project: Ignite
Alexey Goncharuk created IGNITE-5323:
Summary: Move record serializer version from file name to file
header
Key: IGNITE-5323
URL: https://issues.apache.org/jira/browse/IGNITE-5323
Project: Ignite
Alexey Goncharuk created IGNITE-5322:
Summary: Improve WAL record/iterator structure
Key: IGNITE-5322
URL: https://issues.apache.org/jira/browse/IGNITE-5322
Project: Ignite
Issue Type
Hi Igor,
The current implementation assumes that compactFooters should be disabled,
we did not enforce this configuration yet. However, generally, you are
right, and we must have a local-only metadata storage which will keep
binary metadata.
2017-05-25 14:46 GMT+03:00 Seliverstov Igor :
> Hi guy
Guys, I think it makes little or no sense to keep blocks on-heap. If I
understand correctly, the eviction policy was used in combined modes where
partial data eviction is allowed. To make this work in the new PageMemory
architecture, we only need to make sure that IGFS block size equals to the
data
I think it makes sense to switch non-heap memory metrics to new page memory
semantics, this should show a clean picture in the node output and will
also protect us from ambiguous -1 output.
2017-05-24 18:45 GMT+03:00 Dmitry Pavlov :
> Igniters,
>
>
>
> On my jdk 1.8.0_131 there is negative amount
Alexey Goncharuk created IGNITE-5286:
Summary: Reconsider deferredDelete implementation
Key: IGNITE-5286
URL: https://issues.apache.org/jira/browse/IGNITE-5286
Project: Ignite
Issue Type
Igniters,
Since we removed OptimizedMarshaller in Ignite 2.0 from the PublicAPI, we
had a chance to remove several unnecessary test suites from the build plan
from Ignite 2.0. I pushed the changes for IGNITE-4947 ticket. From this
moment you should run tests from Ignite 2.0 project, which is 14 te
Guys,
As discussed, pushed the branch being stabilized to ignite-5267 (and
created the corresponding ticket).
2017-05-21 6:48 GMT+03:00 Denis Magda :
> Sounds good to me.
>
> To keep all of you in the loop, eventually, the *IP clearance vote* has
> been initiated on @incubator-general. Here is t
Alexey Goncharuk created IGNITE-5267:
Summary: Persistent storage migration
Key: IGNITE-5267
URL: https://issues.apache.org/jira/browse/IGNITE-5267
Project: Ignite
Issue Type: New
running tests with similar results in TC Run configs
> "Ignite 2.0 Tests" as it is in "Ignite Tests".
>
> Best regards,
> Dmitry Pavlov
>
> ср, 17 мая 2017 г. в 20:52, Alexey Goncharuk :
>
> > Great news! Looking forward to getting rid of the unneces
That's not entirely true, unfortunately. Note that there may be registered
a number of extensions, which may theoretically conflict with already
listed IDs. I think we should create some sort of lookup table and make
sure that there are no duplicates after all extensions are registered, this
will s
KUZNETSOV :
>
> > Ok, i pick it
> >
> > пт, 19 мая 2017 г. в 14:39, Alexey Goncharuk >:
> >
> >> Well,
> >>
> >> I don't have any clear plan for now on how to approach this issue, so
> if I
> >> were you, I would pick something
to do.
2017-05-19 14:29 GMT+03:00 ALEKSEY KUZNETSOV :
> Now i see. So, may be i should drop the ticket and pick smth else ?
>
> пт, 19 мая 2017 г. в 13:20, Alexey Goncharuk :
>
> > As I described before, one of the reasons behind the waiting is to switch
> > primary node
ired a lock and a new node is joining cluster, should it wait
> for
> > lock release?
> > May be it could proceed joining ?
> > The question comes from my ticket
> > https://issues.apache.org/jira/browse/IGNITE-2671
> >
> > чт, 18 мая 2017 г. в 20:05, Alexey Gonc
Done!
2017-05-18 20:33 GMT+03:00 Denis Magda :
> Alex,
>
> Can you add this excellent explanation as a part of the method Javadoc?
> That will simplify a lot the life of future contributors.
>
> —
> Denis
>
> > On May 18, 2017, at 1:05 PM, Alexey Goncharuk <
&g
Hi Aleksey,
The main purpose of this method is to wait for all ongoing updates
(transactional and atomic), initiated on the previous topology version, to
finish to prevent inconsistencies during rebalancing and to prevent two
different simultaneous owners of the same lock.
We will be adding docum
Great news! Looking forward to getting rid of the unnecessary TC
configurations.
Once this is done, I think we should also work out if we can use build
once, run tests approach for RunAll configuration. Does anybody have a clue
if this is possible?
2017-05-17 20:46 GMT+03:00 Dmitry Pavlov :
> Hi
Alexey Goncharuk created IGNITE-5248:
Summary: Best effort check to detect a 32-bit JVM trying to
allocate too big amount of memory
Key: IGNITE-5248
URL: https://issues.apache.org/jira/browse/IGNITE-5248
Sure, those classes will be renamed to use Ignite* prefix.
Any other comments regarding Configuration or public API changes?
2017-05-16 17:12 GMT+03:00 Alexey Kuznetsov :
> Alexey Goncharuk,
>
> I take a look at source code and noticed classes with nam
Denis,
Headers are updated, RAT check is passing now.
2017-05-16 2:37 GMT+03:00 Denis Magda :
> The receipt of the software grant (the persistent store) was acknowledged
> by Craig Russel.
>
> Now, we need to move on with this
>
> > In the meanwhile, I’ve prepared the IP Clearance page referring
Alexey Goncharuk created IGNITE-5227:
Summary: StackOverflowError in
GridCacheMapEntry#checkOwnerChanged()
Key: IGNITE-5227
URL: https://issues.apache.org/jira/browse/IGNITE-5227
Project: Ignite
Sasha,
The idea behind the ticket was as follows: currently, the rebalanceDelay
property is set in CacheConfiguration, which is not very flexible. In
certain circumstances, a user might expect particularly large load on some
segments of the cluster and want to disable rebalancing for those
(existi
Alexey Goncharuk created IGNITE-5110:
Summary: Topology version should be included in synchronous
continuous message
Key: IGNITE-5110
URL: https://issues.apache.org/jira/browse/IGNITE-5110
Alexey Goncharuk created IGNITE-5107:
Summary: Remove nonHeapMemoryCommitted and nonHeapMemoryUsed from
cluster metrics
Key: IGNITE-5107
URL: https://issues.apache.org/jira/browse/IGNITE-5107
Guys,
First of all, great job on the contribution!
I took a brief look at the source of ML lib and have a comment regarding
the SparseDistributedMatrixStorage. It looks like it will create a new
cache for every new matrix. This sounds a little bit excessive to me,
because (at least in my understa
Alexey Goncharuk created IGNITE-5094:
Summary: Eviction tracker does not evict data pages when near
cache is enabled
Key: IGNITE-5094
URL: https://issues.apache.org/jira/browse/IGNITE-5094
Alexey Goncharuk created IGNITE-5090:
Summary: Get rid of CacheConfiguration#startSize
Key: IGNITE-5090
URL: https://issues.apache.org/jira/browse/IGNITE-5090
Project: Ignite
Issue Type
can handle the documentation separately as a subtask of this umbrella
> >> ticket:
> >>> https://issues.apache.org/jira/browse/IGNITE-4960
> >>>
> >>> —
> >>> Denis
> >>>
> >>>> On Apr 19, 2017, at 7:03 AM, Roman S
Igniters,
Since we moved to the PageMemory architecture, several ClusterMetrics
methods became questionable, so I would like to discuss this before the
release. Currently, ClusterMetrics contains the following methods:
getNonHeapMemoryCommitted(),
getNonHeapMemoryUsed(),
getNonHeapMemoryInitialize
Alexey Goncharuk created IGNITE-5078:
Summary: Partition lost event is fired only on coordinator when
partition loss policy is IGNORE
Key: IGNITE-5078
URL: https://issues.apache.org/jira/browse/IGNITE-5078
Alexey Goncharuk created IGNITE-5072:
Summary: Move memory metrics to snapshots
Key: IGNITE-5072
URL: https://issues.apache.org/jira/browse/IGNITE-5072
Project: Ignite
Issue Type
Agree, I overlooked this during the review. However, the changes to fix
this is pretty simple - we just move all mutator methods to MBean, like
Vladimir suggested and make MBean return the live data, while the public
API will return a serializable snapshot.
Agreed?
2017-04-24 19:33 GMT+03:00 Vlad
Alexey Goncharuk created IGNITE-5061:
Summary: Add ability to enable and disable rebalancing per-node
Key: IGNITE-5061
URL: https://issues.apache.org/jira/browse/IGNITE-5061
Project: Ignite
Denis,
Semantically nothing changed for expiry policies, it applies for all local
entries.
2017-04-21 2:17 GMT+03:00 Denis Magda :
> Alex G., Igniters,
>
> What’s a scope of expiration policy applicability in Ignite 2.0? Does it
> work for all the entries in the page memory or only for those tha
y I'm
> > also
> > > > suggesting to introduce one more configuration property to specify
> > > default
> > > > MemoryPolicy's size in bytes without having to use verbose syntax of
> > > > *memoryPolicyConfiguration
> > > > *sec
introduce one more configuration property to specify
> > default
> > > MemoryPolicy's size in bytes without having to use verbose syntax of
> > > *memoryPolicyConfiguration
> > > *section.
> > >
> > > Any thoughts on this?
> > >
> >
Denis,
This suite is currently Work In Progress and should be ready shortly. The
goal is to get rid of 9 test suites which became obsolete since we moved
optimized marshaller off the public API.
Please validate your PRs against regular set of tests. We will let
community know when the project is
; Fixed now. Thanks for checking!
> Roman
>
>
> On Tuesday, April 18, 2017 10:17 PM, Alexey Goncharuk <
> alexey.goncha...@gmail.com> wrote:
>
>
> Hi Roman,
>
> I tried to run tests for RocketMQ streamer, but they failed for me (I've
> added a comment in the
gt; Binary key representation is stable when we always have
> > equal
> > >>>>>>>>>>>>> serialized
> > >>>>>>>>>>>>>>> bytes when the original keys are e
> https://github.com/apache/
> > > ignite/pull/1759>.
> > > > > Pavel, thank you very much for bringing that to my attention.
> > > > >
> > > > > - Alex
> > > > >
> > > > > 2017-04-07 20:28 GMT+03:00 Sergi Vlad
GNITE-4921
2017-04-18 12:04 GMT+03:00 Dmitriy Setrakyan :
> Thanks, Alexey, got it. What happens if a user starts multiple nodes on the
> same box? Will it work the way Denis suggested?
>
> On Tue, Apr 18, 2017 at 1:47 AM, Alexey Goncharuk <
> alexey.goncha...@gmail.com> wrote:
The reason we cannot add another memory region to page memory is
performance. Currently, the translation of a page ID to a virtual address
is basically a no-op. If we add dynamic memory expansion, we need to
maintain some sort of page ID mapping, which adds significant (in my view,
about 10%) overh
Agree, I will rename it if there are no objections.
2017-04-17 14:31 GMT+03:00 Vladimir Ozerov :
> Guys,
>
> I see that we throw our own "OutOfMemoryException" in this case. I think we
> should rename it to "IgniteOufOfMemoryException" to avoid confusion with
> JDK's "OutOfMemoryError". E.g. I lo
Alexey Goncharuk created IGNITE-4989:
Summary: Assertion error in BPlusTree#finishTail
Key: IGNITE-4989
URL: https://issues.apache.org/jira/browse/IGNITE-4989
Project: Ignite
Issue Type
Alexey Goncharuk created IGNITE-4986:
Summary: .NET possible affinity resource leak
Key: IGNITE-4986
URL: https://issues.apache.org/jira/browse/IGNITE-4986
Project: Ignite
Issue Type
Alexey Goncharuk created IGNITE-4985:
Summary: Atomic cache operations acquire backpressure semaphore on
retries
Key: IGNITE-4985
URL: https://issues.apache.org/jira/browse/IGNITE-4985
Project
That is cool, completely forgot about it :)
2017-04-13 14:07 GMT+03:00 Pavel Tupitsyn :
> Alexey, we can read fields in any order in non-raw mode.
> Dmitriy's suggestion would work.
>
> On Thu, Apr 13, 2017 at 1:56 PM, Alexey Goncharuk <
> alexey.goncha...@gmail.co
Dmitriy,
How would then reader determine which field to read (a and b could the of
different size)? c in this case must be written first.
2017-04-13 0:29 GMT+03:00 Dmitriy Setrakyan :
> Vladimir,
>
> Would this be valid?
>
> *void writeBinary(BinaryWriter w) {*
>
> *if (c)*
> *w.writ
Folks,
The status of ignite-3477 is as follows: we've fixed almost all tests and
currently waiting for ignite-4535 and ignite-4534 to be merged, which will
happen once TC for those branches is completed. This should happen over the
weekend.
2017-04-06 19:12 GMT+03:00 Alexey Kuznetsov :
> I've p
Aleksey,
This issue is a part of a more global task:
https://issues.apache.org/jira/browse/IGNITE-3478 which is currently being
designed by the community [1], Sergi Vladykin is driving the process. For
some reason, this ticket was not linked to the first issue, I've fixed that.
Once we all agree o
Yes, this can happen if caches were created on different versions of
topology, because FairAffinityFunction is stateful and requires previous
affinity assignment state.
Generally, this can be fixed by introducing cache groups that use the same
affinity and use this shared state across all caches.
e then it’s fine but if you suggest
> removing identity resolvers public interfaces then it might be a haste
> decision.
>
> —
> Denis
>
> > On Apr 5, 2017, at 7:42 AM, Alexey Goncharuk
> wrote:
> >
> > +1, I see no other reasons to keep it.
> >
> >
This optimization does not work when near cache is enabled because we need
the same ordering on near nodes. You should see the expected number of
messages with near cache disabled.
2017-04-05 15:09 GMT+03:00 ALEKSEY KUZNETSOV :
> yes
>
> ср, 5 апр. 2017 г. в 15:07, Alexey Goncharuk :
sponse.class, 1);
>
> ср, 5 апр. 2017 г. в 14:53, Alexey Goncharuk :
>
> > Aleksey,
> >
> > Can you elaborate on which of the extra messages you observe?
> >
> > --AG
> >
> > 2017-04-04 14:17 GMT+03:00 ALEKSEY KUZNETSOV :
> >
> >
Aleksey,
Can you elaborate on which of the extra messages you observe?
--AG
2017-04-04 14:17 GMT+03:00 ALEKSEY KUZNETSOV :
> any thoughts on one phase commit realization ?
>
> пн, 3 апр. 2017 г. в 19:35, ALEKSEY KUZNETSOV :
>
> > I've attached test that prints messages exchange . Which shows us
+1, I see no other reasons to keep it.
2017-04-05 13:59 GMT+03:00 Sergi Vladykin :
> +1
>
> Lets drop them.
>
> Sergi
>
> 2017-04-05 13:50 GMT+03:00 Dmitriy Govorukhin <
> dmitriy.govoruk...@gmail.com>
> :
>
> > Hi guys, i implemented proxy for IgniteCache in hibernate integration,
> this
> > pro
nks for help. I've created ticket :
> > https://issues.apache.org/jira/browse/IGNITE-4887
> > and a commit :
> > https://github.com/voipp/ignite/commit/aa3487bd9c203394f534c605f84e06
> 436b638e5c
> > We really need this feature
> >
> > чт, 30 мар. 20
t; String key1Value = cache.get("key1");
> if(key1Value.equals("val1!"))
> throw new RuntimeException("dirty read!");<-- exception does
> happen!
> cache.put("key1", "val1");
> cache.put("key2", "val2"
701 - 800 of 1062 matches
Mail list logo
