Hi Snigdhadeb,
Welcome to Apache Ignite Community!
Usually each contribution is related to a ticket in Jira
https://issues.apache.org/jira/projects/IGNITE. Do you have such ticket
already?
To start working on a ticket you need to get a contributor rights to assign
ticket to yourself. Please
Hi guys!
By the way, is it practically feasible to revert a single commit without
making harm? If I am getting it right in current case reverting commit will
lead to compilation errors for commits depending on commit in question.
2018-09-28 14:22 GMT+03:00 Dmitriy Pavlov :
> Hi Dmitriy S.,
>
>
ittle value nowadays. Does anyone have something against deprecating
> > > them?
> > >
> > >
> > > These events are used in a pure caching or in-memory data grid use
> cases
> > > where key-value is a primary access pattern. I personally know s
ently I do not see options
how to overcome it.
Also, I hardly imagine current use cases for cache events. I think that
understanding them is the best way for developing working solution for MVCC.
I need your opinions.
2018-09-21 12:54 GMT+03:00 Павлухин Иван :
> Hi Igniters,
>
> As
Hi Igniters,
As you might know MVCC was introduced in Apache Ignite. We started
IgniteEvents implementation for MVCC caches and faced some obstacles. I
would like to start a discussion about next steps which should be done to
deal with current problems.
--
Best regards,
Ivan Pavlukhin
Dmitry,
I cannot confirm invitation. Do I need special permissions for
dev@ignite.apache.org calendar?
2018-09-14 12:24 GMT+03:00 Dmitriy Pavlov :
> Please see the invitation as a separate thread. Could you please also
> confirm invitation came?
>
> пт, 14 сент. 2018 г. в 12:13, П
Hi guys!
Webinar sounds as good idea. But could you please shortly describe the main
webinar theme? For those who are out of context =)
2018-09-14 10:33 GMT+03:00 Dmitrii Ryabov :
> Hi, Dmitriy,
>
> Webinar is good, but we need a page on the wiki (or "help" in the bot) for
> new contributors.
RecoveryTest0%
> > * sys-#148%wal.IgniteWalRecoveryTest1%
> > * db-checkpoint-thread-#129%wal.IgniteWalRecoveryTest2%
> > Suppose everything would be OK here for `static` and `non-static` case of
> > ThreadLocal.
> >
> > [1]
> >
> > http://hg.ope
Dmitriy,
Could you point to some piece of code implementing described pattern?
2018-09-11 13:02 GMT+03:00 Павлухин Иван :
> Alex,
>
> ThreadLocal subclass is used in IgniteH2Indexing for simple access to H2
> Connection from current thread. Such subclass has a capability to create
, 11 сент. 2018 г. в 9:13, Павлухин Иван :
>
> > Guys,
> >
> > As we know ThreadLocal is an instrument which should be used with great
> > care. And I recently faced with problems related to proper cleanup of
> > ThreadLocal which is not needed anymore. In my opini
Guys,
As we know ThreadLocal is an instrument which should be used with great
care. And I recently faced with problems related to proper cleanup of
ThreadLocal which is not needed anymore. In my opinion the best thing (in
ideal world) is to get rid of ThreadLocal where possible, but I guess that
Sincerely,
> Dmitriy Pavlov
>
> чт, 16 авг. 2018 г. в 12:09, Павлухин Иван :
>
> > Vladimir,
> >
> > First of all, statements in Java 8 section [1] looks kind of prohibitive
> > for me. When a new contributor see words "preferred" and "avoided in
Hi team,
I need you opinion again. I wrote some tests for metrics and felt a
confusion with metrics count for the same key update during transaction.
Imagine following case:
BEGIN;
INSERT INTO person(id, name) VALUES(1, 'ivan');
UPDATE person SET name = 'vanya' WHERE id = 1;
COMMIT;
My
are no matching keys in the
> first remove() call should be found, remove() should return false and
> "cache removals" metric should not be affected.
>
> 2018-08-10 12:56 GMT+03:00 Павлухин Иван :
>
> > Hi,
> >
> > Dmitriy thanks for note, I will keep
Vladimir,
First of all, statements in Java 8 section [1] looks kind of prohibitive
for me. When a new contributor see words "preferred" and "avoided in most
cases" he most likely will not use such features (like I did). If a
statement is not prohibitive in practice it could be at least rephrased.
is dirty writes as additional metrics.
> >
> > Also additional metrics concerning MVCC could be:
> >
> > - Average count of the active transactions per snapshot
> >
> > - Average quantity of versions per key
> >
> >
> > --
> >
> &
; discussion started?
>
> D.
>
> On Tue, Aug 7, 2018 at 9:17 AM, Павлухин Иван wrote:
>
> > Hi Igniters,
> >
> > I am working on cache metrics support for caches with enabled MVCC. As
> you
> > may know, during MVCC transaction execution entry versions are writ
Hi Igniters,
I am working on cache metrics support for caches with enabled MVCC. As you
may know, during MVCC transaction execution entry versions are written to
storage right away (without deferring until commit). So, it is not obvious
for me if we should update writes count right away or defer
Hi Igniters,
I had a look into IgniteDataStreamer. As far as I understand, currently it
just works incorrectly for MVCC tables. It appears as a blocker for
releasing MVCC. The simplest thing is to refuse creating streamer for MVCC
tables.
Next step could be hair splitting of related use cases.
://cwiki.apache.org/confluence/display/IGNITE/Development+Process
>
> Instructions on how to contribute can be found here:
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
>
> Project setup in Intellij IDEA:
> https://cwiki.apache.org/confluence/display/IGNIT
Hi Igniters,
I would like to start working on
https://issues.apache.org/jira/browse/IGNITE-8581
My name in Jira is Pavlukhin
--
Best regards,
Ivan Pavlukhin
Hi,
Please subscribe me.
--
Best regards,
Ivan Pavlukhin
301 - 322 of 322 matches
Mail list logo
