[GitHub] ignite pull request: IGNITE-2555 fix

[ruskim]

GitHub user ruskim opened a pull request:

https://github.com/apache/ignite/pull/468

IGNITE-2555 fix

 Added offheap usage (used/free/committed) to local node reports.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ruskim/ignite IGNITE-2555

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/468.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #468


commit db1417f98133d35e10ae4acd20428b51e2b1
Author: ruskim 
Date:   2016-02-09T18:06:32Z

fix IGNITE-2555




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-2369 added ability to auto close popup...

[Dmitriyff]

GitHub user Dmitriyff opened a pull request:

https://github.com/apache/ignite/pull/465

IGNITE-2369 added ability to auto close popup after broswer navigation



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Dmitriyff/ignite ignite-2369

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/465.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #465


commit 7ede9440a9fabe9a1d07d8ba38f2b4c314fc2555
Author: Dmitriyff 
Date:   2016-02-09T08:32:16Z

IGNITE-2369 added ability to auto close modal dialog, after browser 
navigation

commit d3cec64ece8e92b69c01497f84584788d07cfa88
Author: Dmitriyff 
Date:   2016-02-09T08:32:52Z

Merge remote-tracking branch 'apache/ignite-843-rc2' into ignite-2369




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Hello

[Konstantin Margorin]

Hi All,

I'm Konstantin Margorin from Anturis.

I would like to contribute my effort on Apache Ignite project and
appreciate if I could join with you.

Looking forward to your reply.

Best regards,
Konstantin

[jira] [Created] (IGNITE-2599) Unsaved changes doesn't appear on Clone cache\igfs\model

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-2599:
--

 Summary: Unsaved changes doesn't appear on Clone cache\igfs\model
 Key: IGNITE-2599
 URL: https://issues.apache.org/jira/browse/IGNITE-2599
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Konstantinov
Assignee: Andrey Novikov






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2597) rework transport layer to websocket

[Dmitriyff (JIRA)]

Dmitriyff created IGNITE-2597:
-

 Summary: rework transport layer to websocket
 Key: IGNITE-2597
 URL: https://issues.apache.org/jira/browse/IGNITE-2597
 Project: Ignite
  Issue Type: Sub-task
Reporter: Dmitriyff






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2598) Enum arguments in SQL queries are not considered with BinaryMarshaller

[Denis Magda (JIRA)]

Denis Magda created IGNITE-2598:
---

 Summary: Enum arguments in SQL queries are not considered with 
BinaryMarshaller
 Key: IGNITE-2598
 URL: https://issues.apache.org/jira/browse/IGNITE-2598
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.5.0.final
Reporter: Denis Magda
Assignee: Vladimir Ozerov
 Fix For: 1.6


Queries like the one below doesn't work with {{Enum}} returning a wrong result 
when binary marshaller is used.

{noformat}
SqlQuery query = new SqlQuery(Event.class, "type = 
?");
query.setArgs(EventType.EventA);
{noformat}

The same query works perfectly fine if optimized marshaller is enabled instead.

Attached the test that reproduces the issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] ignite pull request: IGNITE-2523

[ilantukh]

GitHub user ilantukh opened a pull request:

https://github.com/apache/ignite/pull/467

IGNITE-2523



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ilantukh/ignite ignite-2523

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/467.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #467


commit 466528329942f009c9e591a16b9453b95830b0cb
Author: vozerov-gridgain 
Date:   2016-02-03T07:24:01Z

IGNITE-2532: WIP. Only refactorings for now.

commit 29c2aee6b6ffac4f27da3732575f7d82b0e8bedd
Author: vozerov-gridgain 
Date:   2016-02-03T08:09:13Z

IGNITE-2532: WIP. Only refactorings for now.

commit 2a1a31d2d0999fdb8854a05fd7a75a4cd0b159a4
Author: vozerov-gridgain 
Date:   2016-02-03T08:36:39Z

IGNITE-2532: Single update request is finalyl wired up. Though, it is not 
optimzied yet.

commit 52d20cdcdc886c6ceaed49239e822a1d6deaa7dd
Author: vozerov-gridgain 
Date:   2016-02-03T09:03:31Z

IGNITE-2532: WIP on single message optimization.

commit 89c8074452b4bc209eb03d758e534f0ef8365d46
Author: vozerov-gridgain 
Date:   2016-02-03T09:08:18Z

IGNITE-2532: WIP on single message optimization.

commit 07c23931f9758497db50bf0851af5d6c0fb8eaa4
Author: vozerov-gridgain 
Date:   2016-02-03T09:45:42Z

IGNITE-2532: Reverting changes to GridNearAtomicUpdateFuture.

commit e066650cf4907851dca1d8ef0297f6a1522d6a87
Author: vozerov-gridgain 
Date:   2016-02-03T12:02:52Z

Merge branch 'master' into ignite-2523

commit 3967130f54fa21d25e7e284ecabaf004b937b921
Author: vozerov-gridgain 
Date:   2016-02-03T12:53:07Z

IGNITE-2523: Finalization.

commit 3d34e50c9ece0d12e35a0ff6130659cfa03bdddf
Author: vozerov-gridgain 
Date:   2016-02-04T07:44:33Z

Merge branch 'master' into ignite-2523

commit d3e1645aaeb8fd9393744cb087a9ddde27f2e95b
Author: vozerov-gridgain 
Date:   2016-02-04T07:52:48Z

IGNITE-2523: Fixed message count tests.

commit 0128f988c60cdbd9aec6996626b6ffb1ad1fa30e
Author: vozerov-gridgain 
Date:   2016-02-04T07:54:25Z

IGNITE-2523: Fixed IgniteCacheAtomicStopBusySelfTest.

commit 7e09a146acefccc885e78c57ca85f754d4db5d45
Author: vozerov-gridgain 
Date:   2016-02-04T07:59:59Z

IGNITE-2523: Fixed several other tests.

commit c54873bba2b2a0777a7ade33f5ec3da82c96ce95
Author: vozerov-gridgain 
Date:   2016-02-04T08:04:58Z

IGNITE-2523: Renaming: interface -> base.

commit e83408060970aba8f3f98ec7be1d96bab4fa888c
Author: vozerov-gridgain 
Date:   2016-02-04T09:05:56Z

IGNITE-2523: Fixing tests.

commit 1491c1f494e47618191ae7e4f79c67a5fdd9a326
Author: vozerov-gridgain 
Date:   2016-02-05T07:04:04Z

IGNITE-2523: Renamings.

commit 11a27f74f5a85320f6473a4cd2e59e35459cc587
Author: vozerov-gridgain 
Date:   2016-02-05T07:07:02Z

Merge branch 'master' into ignite-2523

commit a18c352748a86ac9e48885f1b6ae93ff9ed4f4dd
Author: vozerov-gridgain 
Date:   2016-02-05T07:09:48Z

IGNITE-2523: Minors.

commit dfdd2f4f907651a86da6fd52f18d2f189f65279d
Author: Ilya Lantukh 
Date:   2016-02-08T14:23:02Z

ignite-2523 : Created SingleUpdateResponse

commit c39410a2dbbab7e8886a407a5661b29ee985adce
Author: Ilya Lantukh 
Date:   2016-02-08T15:05:34Z

ignite-2523 : SingleUpdateResponse implementation.

commit 3c8d02a00b2bcbc194fd2112d9f8cb58ab7d571a
Author: Ilya Lantukh 
Date:   2016-02-08T15:25:21Z

ignite-2523 : Generalized usage of GridNearAtomicUpdateRequest/Response.

commit cb5bdb3f19cefe14380ac169d49e6e86bde1899a
Author: Ilya Lantukh 
Date:   2016-02-08T15:51:55Z

ignite-2523 : Generalized usage of GridNearAtomicUpdateRequest/Response.

commit 4f8220e6da06443f1ef42ac3f4b4e46f5100dcd1
Author: Ilya Lantukh 
Date:   2016-02-09T11:38:12Z

ignite-2523 : finished generalization of GridNearAtomicUpdate.

commit 2f6aff8024794cd980fd77bb96e9a74876fb7442
Author: Ilya Lantukh 
Date:   2016-02-09T12:04:52Z

ignite-2523 : Fixed failing tests.

commit 6040f45eae844fd40c113de452e70078dae9a95c
Author: Ilya Lantukh 
Date:   2016-02-09T13:14:57Z

ignite-2523 : Fixed test failures.

commit 3391c847e9825405d8ca2f7df7e01ba432f60b1b
Author: Ilya Lantukh 
Date:   2016-02-09T14:43:39Z

ignite-2523 : Created GridDhtAtomicSingleUpdateRequest optimized 
implementation.

commit 

[GitHub] ignite pull request: IGNITE-2222: Implemented Date and Timestamp c...

[isapego]

GitHub user isapego opened a pull request:

https://github.com/apache/ignite/pull/466

IGNITE-: Implemented Date and Timestamp classes.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/isapego/ignite ignite-

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/466.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #466


commit a55f1b5c737e4380ee9e50c0f2bd473904ec08f8
Author: isapego 
Date:   2016-02-08T15:56:47Z

IGNITE-: Test for the Date type added.

commit 39186f4042b7453026bc7eaf088ed5c7b3462f70
Author: isapego 
Date:   2016-02-08T16:39:59Z

IGNITE-: Added ignite::Date class.

commit d7bf440fa0eff01babaf0979a4ea0827561f7500
Author: isapego 
Date:   2016-02-08T16:51:46Z

IGNITE-: Added Date reading and writing to binary utils.

commit 35a6e1edd7c9a1207b035935f86671c787618b45
Author: isapego 
Date:   2016-02-08T17:03:12Z

IGNITE-: Added Date to BinaryWriterImpl.

commit af8b0db6247352ae16c93c65a898255774773173
Author: isapego 
Date:   2016-02-08T17:19:36Z

IGNITE-: Added specialisation WriteTopObject.

commit 6f86354fd4ad3f2c0ac62ba3e5333551c6233805
Author: isapego 
Date:   2016-02-08T17:24:20Z

IGNITE-: BinaryRawWriter::WriteDate[Array] implemented.

commit 34bb1d68e096e083a85868dcf473f920e54c0af2
Author: isapego 
Date:   2016-02-08T18:05:37Z

IGNITE-: Implemented BinaryReaderImpl::ReadDate[Array].

commit b03b9bfc969d76f76e4a6e5fa401061b919cad47
Author: isapego 
Date:   2016-02-08T18:08:32Z

IGNITE-: Implemented BinaryRaqReader::ReadDate[Array].

commit e36f03bc5b16a074ab9308791d38a35b9bab1d72
Author: isapego 
Date:   2016-02-08T18:21:15Z

IGNITE-: Fix for the test.

commit 0a4b2e326b99a38336832a1289ae1461697efb3b
Author: isapego 
Date:   2016-02-08T18:28:58Z

IGNITE-: Added test for DateArray.

commit f08029aeb96a887c679f821f488b5d22b7a612fb
Author: isapego 
Date:   2016-02-08T18:44:16Z

IGNITE-: Added BinaryWriter::WriteDate[Array].

commit e80350a4a0ae7bb5ab714f0bcb21b3b14236a8d8
Author: isapego 
Date:   2016-02-08T18:47:53Z

IGNITE-: Added BinaryReader::ReadDate[Array].

commit 7428a3b1b3937d36f048916aeb773a2f058373f3
Author: isapego 
Date:   2016-02-08T19:06:36Z

IGNITE-: Tests for Date type reworked.

commit 14d921b89c6d89e0368a044bd3eeff4e4f6a503f
Author: isapego 
Date:   2016-02-09T13:12:26Z

IGNITE-: Added timestamp class.

commit 0263b602c85f0f5f5c94fb80d4571612fb923813
Author: isapego 
Date:   2016-02-09T13:28:56Z

IGNITE-: Added binary utils for Timestamp.

commit 937248c3ace1b070c1c558c7fe17ce2864e735a4
Author: isapego 
Date:   2016-02-09T13:36:48Z

IGNITE-: Timestamp binary type added.

commit 37db4a2a748582b7a83b51fdf46f8648e1fa4f87
Author: isapego 
Date:   2016-02-09T13:41:56Z

IGNITE-: Added BinaryWriterImpl::WriteTimestamp[Array]().

commit a5583a79bbfec3157ae595b7c22cefc3be614706
Author: isapego 
Date:   2016-02-09T13:51:03Z

IGNITE-: Added BinaryReaderImpl::ReadTimestamp[Array]().

commit 8e1a023ff3fbc480a9c6f17a239f7e11ce04f63b
Author: isapego 
Date:   2016-02-09T13:57:05Z

IGNITE-: Added BinaryWriter::WriteTimestamp[Array]().

commit 8a851fd65a69231ff7477882554143a9f085bfcb
Author: isapego 
Date:   2016-02-09T13:59:17Z

IGNITE-: Added BinaryReader::ReadTimestamp[Array]().

commit e4f2cdf5e0c7cbffd287c024191caff5e5bed9e1
Author: isapego 
Date:   2016-02-09T14:01:11Z

IGNITE-: Added BinaryRawReader::ReadTimestamp[Array]().

commit 26cd9ea51d1f627be21ad2aee3632602b3cf5126
Author: isapego 
Date:   2016-02-09T14:04:06Z

GNITE-: Added BinaryRawWriter::WriteTimestamp[Array]().

commit 67cacde49c67a5c86f88c3adf8873b27e1a4
Author: isapego 
Date:   2016-02-09T14:14:40Z

IGNITE-: Added tests for Timestamp binary type.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-2600) .NET: Do not serialize object if AtomicReference CAS succeeded.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-2600:
---

 Summary: .NET: Do not serialize object if AtomicReference CAS 
succeeded.
 Key: IGNITE-2600
 URL: https://issues.apache.org/jira/browse/IGNITE-2600
 Project: Ignite
  Issue Type: Task
  Components: platforms
Affects Versions: 1.5.0.final
Reporter: Vladimir Ozerov
Assignee: Pavel Tupitsyn
 Fix For: 1.6


See PlatformAtomicReference.processInStreamOutStream() method.
If CAS suceeded, then (cmp == res).

As such, instead of writing object in binary form to the stream, we can simply 
pass boolean flag indicating successful CAS.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Hello

[Vladimir Ozerov]

Konstantin, sorry I confused the name.

Should you have any further questions please feel free to ask.

On Tue, Feb 9, 2016 at 2:29 PM, Vladimir Ozerov 
wrote:

> Hi Carlos,
>
> Welcome to the Ignite community!
>
> You should get familiar with Ignite development process described here:
> https://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
>
> Once you got familiar and were able to run a few examples, you should pick
> a Jira ticket you would like to start on. Send an email to the dev list, so
> we can add you as a contributor in Jira.
>
> You can find interesting tickets to get started here:
> https://ignite.apache.org/community/contribute.html#pick-ticket
>
> Looking forward to your contributions!
>
> Regards,
> Vladimir.
>
>
> On Tue, Feb 9, 2016 at 12:58 PM, Konstantin Margorin 
> wrote:
>
>> Hi All,
>>
>> I'm Konstantin Margorin from Anturis.
>>
>> I would like to contribute my effort on Apache Ignite project and
>> appreciate if I could join with you.
>>
>> Looking forward to your reply.
>>
>> Best regards,
>> Konstantin
>>
>
>

Re: Hello

[Konstantin Margorin]

Hi Vladimir.

I had searched through open tickets for newbies. And looks like the only
open unassigned ticked is:
https://issues.apache.org/jira/browse/IGNITE-2049

Is this ticket right point to start?

Best regards,
Konstantin

On Tue, Feb 9, 2016 at 2:30 PM, Vladimir Ozerov 
wrote:

> Konstantin, sorry I confused the name.
>
> Should you have any further questions please feel free to ask.
>
> On Tue, Feb 9, 2016 at 2:29 PM, Vladimir Ozerov 
> wrote:
>
> > Hi Carlos,
> >
> > Welcome to the Ignite community!
> >
> > You should get familiar with Ignite development process described here:
> > https://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
> >
> > Once you got familiar and were able to run a few examples, you should
> pick
> > a Jira ticket you would like to start on. Send an email to the dev list,
> so
> > we can add you as a contributor in Jira.
> >
> > You can find interesting tickets to get started here:
> > https://ignite.apache.org/community/contribute.html#pick-ticket
> >
> > Looking forward to your contributions!
> >
> > Regards,
> > Vladimir.
> >
> >
> > On Tue, Feb 9, 2016 at 12:58 PM, Konstantin Margorin 
> > wrote:
> >
> >> Hi All,
> >>
> >> I'm Konstantin Margorin from Anturis.
> >>
> >> I would like to contribute my effort on Apache Ignite project and
> >> appreciate if I could join with you.
> >>
> >> Looking forward to your reply.
> >>
> >> Best regards,
> >> Konstantin
> >>
> >
> >
>

Re: Hello

[Vladimir Ozerov]

Konstantin,

This ticket is more about build process. You can also look at the following
ones:
https://issues.apache.org/jira/browse/IGNITE-1783
https://issues.apache.org/jira/browse/IGNITE-2555

Vladimir.

On Tue, Feb 9, 2016 at 2:57 PM, Konstantin Margorin 
wrote:

> Hi Vladimir.
>
> I had searched through open tickets for newbies. And looks like the only
> open unassigned ticked is:
> https://issues.apache.org/jira/browse/IGNITE-2049
>
> Is this ticket right point to start?
>
> Best regards,
> Konstantin
>
> On Tue, Feb 9, 2016 at 2:30 PM, Vladimir Ozerov 
> wrote:
>
> > Konstantin, sorry I confused the name.
> >
> > Should you have any further questions please feel free to ask.
> >
> > On Tue, Feb 9, 2016 at 2:29 PM, Vladimir Ozerov 
> > wrote:
> >
> > > Hi Carlos,
> > >
> > > Welcome to the Ignite community!
> > >
> > > You should get familiar with Ignite development process described here:
> > > https://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
> > >
> > > Once you got familiar and were able to run a few examples, you should
> > pick
> > > a Jira ticket you would like to start on. Send an email to the dev
> list,
> > so
> > > we can add you as a contributor in Jira.
> > >
> > > You can find interesting tickets to get started here:
> > > https://ignite.apache.org/community/contribute.html#pick-ticket
> > >
> > > Looking forward to your contributions!
> > >
> > > Regards,
> > > Vladimir.
> > >
> > >
> > > On Tue, Feb 9, 2016 at 12:58 PM, Konstantin Margorin  >
> > > wrote:
> > >
> > >> Hi All,
> > >>
> > >> I'm Konstantin Margorin from Anturis.
> > >>
> > >> I would like to contribute my effort on Apache Ignite project and
> > >> appreciate if I could join with you.
> > >>
> > >> Looking forward to your reply.
> > >>
> > >> Best regards,
> > >> Konstantin
> > >>
> > >
> > >
> >
>

Re: Hello

[Konstantin Margorin]

Vladimir, thank you.

I could handle this one:
https://issues.apache.org/jira/browse/IGNITE-2555

Konstantin

On Tue, Feb 9, 2016 at 3:11 PM, Vladimir Ozerov 
wrote:

> Konstantin,
>
> This ticket is more about build process. You can also look at the following
> ones:
> https://issues.apache.org/jira/browse/IGNITE-1783
> https://issues.apache.org/jira/browse/IGNITE-2555
>
> Vladimir.
>
> On Tue, Feb 9, 2016 at 2:57 PM, Konstantin Margorin 
> wrote:
>
> > Hi Vladimir.
> >
> > I had searched through open tickets for newbies. And looks like the only
> > open unassigned ticked is:
> > https://issues.apache.org/jira/browse/IGNITE-2049
> >
> > Is this ticket right point to start?
> >
> > Best regards,
> > Konstantin
> >
> > On Tue, Feb 9, 2016 at 2:30 PM, Vladimir Ozerov 
> > wrote:
> >
> > > Konstantin, sorry I confused the name.
> > >
> > > Should you have any further questions please feel free to ask.
> > >
> > > On Tue, Feb 9, 2016 at 2:29 PM, Vladimir Ozerov 
> > > wrote:
> > >
> > > > Hi Carlos,
> > > >
> > > > Welcome to the Ignite community!
> > > >
> > > > You should get familiar with Ignite development process described
> here:
> > > >
> https://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
> > > >
> > > > Once you got familiar and were able to run a few examples, you should
> > > pick
> > > > a Jira ticket you would like to start on. Send an email to the dev
> > list,
> > > so
> > > > we can add you as a contributor in Jira.
> > > >
> > > > You can find interesting tickets to get started here:
> > > > https://ignite.apache.org/community/contribute.html#pick-ticket
> > > >
> > > > Looking forward to your contributions!
> > > >
> > > > Regards,
> > > > Vladimir.
> > > >
> > > >
> > > > On Tue, Feb 9, 2016 at 12:58 PM, Konstantin Margorin <
> rus...@gmail.com
> > >
> > > > wrote:
> > > >
> > > >> Hi All,
> > > >>
> > > >> I'm Konstantin Margorin from Anturis.
> > > >>
> > > >> I would like to contribute my effort on Apache Ignite project and
> > > >> appreciate if I could join with you.
> > > >>
> > > >> Looking forward to your reply.
> > > >>
> > > >> Best regards,
> > > >> Konstantin
> > > >>
> > > >
> > > >
> > >
> >
>

RE: EntryProcessor in ATOMIC cache and CLOCK versioning mode

[Alexey Goncharuk]

Igniters,

I want to bring community attention to the ticket [1] once again since it
raises a lot of confusion among Ignite users [2] and I would like this to
be addressed in 1.6.

The alternatives for the case when entry processor is used in CLOCK mode
are:
 * Print a warning, but still allow to use invoke() since it will work if
key access is synchronized by external means.
 * Throw an exception and force users to switch to PRIMARY mode when
invoke() is used.

Any thoughts / other suggestions?

-- AG

[1] https://issues.apache.org/jira/browse/IGNITE-2088
[2]
http://apache-ignite-users.70518.x6.nabble.com/Version-issue-with-concurrent-cache-updates-EntryProcessor-td2896.html

[GitHub] ignite pull request: IGNITE-1563 .Net: Implemented "atomic" data s...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/455


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-2380 .NET: Allow Ignite configuration ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/417


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: EntryProcessor in ATOMIC cache and CLOCK versioning mode

[Alexey Goncharuk]

After a second thought, I think the warning should be printed anyways when
CLOCK versioning mode is used because it does not guarantee happens-before
relationship when cache operations are invoked on different nodes (see an
example in pseudo-code below). Essentially, when cache operations are
invoked on different nodes within a time span smaller or equal than time
sync error, they are considered to be run concurrently.

IgniteCache cache = ignite.cache("name");

cache.put(1, 1);

// Select a random remote node.
ClusterGroup grp = ignite.cluster().forRemotes().forRandom();

ignite.compute(grp).call(new Callable() {
public Object call() throws Exception {
cache.put(1, 2); // This does not guarantee to succeed in CLOCK
mode.
}
});

// This may fail in CLOCK mode.
assert cache.get(1) == 2;

I agree that the documentation must be updated accordingly, and I think the
warning printed should contain a link to the page.

Any other thoughts?

Re: Hello

[Vladimir Ozerov]

Hi Carlos,

Welcome to the Ignite community!

You should get familiar with Ignite development process described here:
https://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

Once you got familiar and were able to run a few examples, you should pick
a Jira ticket you would like to start on. Send an email to the dev list, so
we can add you as a contributor in Jira.

You can find interesting tickets to get started here:
https://ignite.apache.org/community/contribute.html#pick-ticket

Looking forward to your contributions!

Regards,
Vladimir.

On Tue, Feb 9, 2016 at 12:58 PM, Konstantin Margorin 
wrote:

> Hi All,
>
> I'm Konstantin Margorin from Anturis.
>
> I would like to contribute my effort on Apache Ignite project and
> appreciate if I could join with you.
>
> Looking forward to your reply.
>
> Best regards,
> Konstantin
>

[jira] [Created] (IGNITE-2602) Queries: offset does not work with negative or MAX_VALUE limit

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-2602:
--

 Summary: Queries: offset does not work with negative or MAX_VALUE 
limit
 Key: IGNITE-2602
 URL: https://issues.apache.org/jira/browse/IGNITE-2602
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.1.4
Reporter: Pavel Tupitsyn
 Fix For: 1.6


H2 allows specifying negative LIMIT with OFFSET: 
http://www.h2database.com/html/grammar.html
This does not work with Ignite (query returns empty result set).

To work around this, I tried to specify Integer.MAX_VALUE, but this causes an 
exception.

Turns out, offset+limit should be <= Integer.MAX_VALUE, which is quite 
inconvenient.

I think we should support negative LIMIT for unlimited offset queries.





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2603) OSGi support for objects passed through CacheConfiguration

[Denis Magda (JIRA)]

Denis Magda created IGNITE-2603:
---

 Summary: OSGi support for objects passed through CacheConfiguration
 Key: IGNITE-2603
 URL: https://issues.apache.org/jira/browse/IGNITE-2603
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.5.0.final
Reporter: Denis Magda
Assignee: Anton Vinogradov
 Fix For: 1.6


If a user sets a custom class loader with 
{{IgniteConfiguration.setClassLoader}} then it always has to be used when the 
following objects passed to {{CacheConfiguration}} are being deserialized:

- CacheStore factory;
- CacheStoreSessionListener factory;
- CachePluginConfiguration;
- AffinityKeyMapper;
- IgnitePredicate (as a node filter in CacheConfiguration.setNodeFilter(...));
- CacheEntryListenerConfiguration class with factories for CacheEntryListener 
and CacheEntryEventFilter;

In case of OSGi class loaders can be quite exotic. As an example {{CacheStore}} 
factory loaded from bundle A, can contain objects loaded from bundle B and 
bundle C. When such class loader is set as 
{{IgniteConfiguration.setClassLoader}} then deserialization of the 
{{CacheStore}} factory must work fine as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2604) CacheContinuousQueryBatchAck is sent to nodes that doesn't hold cache data

[Denis Magda (JIRA)]

Denis Magda created IGNITE-2604:
---

 Summary: CacheContinuousQueryBatchAck is sent to nodes that 
doesn't hold cache data
 Key: IGNITE-2604
 URL: https://issues.apache.org/jira/browse/IGNITE-2604
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.5.0.final
Reporter: Denis Magda
Assignee: Nikolay Tikhonov
 Fix For: 1.6


Presently {{CacheContinuousQueryBatchAck}} is sent to every node of the cluster 
including client nodes but in fact it has to be sent to backup nodes only. The 
reason is that the list of the backups is retrieved with 
{{ctx.discovery().cacheNodes(topVer)}} method which returns all the nodes where 
at least one cache is registered.

Refer to {{CacheContinuousQueryHandler.sendBackupAcknowledge}} method body
{noformat}
for (AffinityTopologyVersion topVer : t.get2())
nodes.addAll(ctx.discovery().cacheNodes(topVer));
{noforma}

The list has to be formed by remote nodes that contain only a particular cache

{noformat}
for (AffinityTopologyVersion topVer : t.get2())
nodes.addAll(ctx.discovery().remoteCacheNodes(cctx.name(), topVer));
{noformat}

and finally the ack has to be sent only if a node is not a client node

{noformat}
for (ClusterNode node : nodes) {
if (!node.isClient()) {
try {
cctx.io().send(node, msg, 
GridIoPolicy.SYSTEM_POOL);
{noformat}

Next, in my understanding there is no need to register 
CacheContinuousQueryBatchAck handler on the client side. Presently it's 
registered in {{CacheContinuousQueryManager.start0}} method.

Finally, since currently the ack is sent to clients as well the following 
warning floods logs in some unclear cases

{noformat}
20160208 12:56:30.301 WARN [sys-#7%null%] 
org.apache.ignite.internal.processors.cache.GridCacheIoManager [] - Received 
message without registered handler (will ignore) 
[msg=CacheContinuousQueryBatchAck 
[routineId=df328a9f-6a63-40f7-8a1b-923cfadb6337, updateCntrs={193=1455, 
898=1434, 581=307, 584=159, 75=376, 331=233, 652=434, 13=420, 910=923, 143=249, 
147=619, 150=1185, 598=338, 728=1168, 90=598, 346=1169, 283=214, 934=388, 
615=310, 807=140, 1002=1132, 555=344, 365=215, 941=342, 946=515, 1015=635, 
56=614, 378=1130, 827=720, 956=5675}], 
nodeId=d78ac9e5-60dd-4fa9-a8eb-7c5c36e189af, locTopVer=AffinityTopologyVersion 
[topVer=248, minorTopVer=1], msgTopVer=AffinityTopologyVersion [topVer=-1, 
minorTopVer=0], cacheDesc=DynamicCacheDescriptor 
[deploymentId=b8776e0c251-eb7db0e0-c35f-4a05-af44-5295c4cfdc01, locCfg=false, 
staticCfg=true, started=true, cacheType=USER, template=false, 
pluginMgr=GridCacheManagerAdapter [starting=false], updatesAllowed=true, 
startTopVer=null, rcvdOnDiscovery=true, cacheName=GETS_ORDER_MAP]]
{noformat}




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Hello

[Denis Magda]

Hi Konstantin, welcome!

Added you to the contributors list in JIRA. So for now you're able to 
assign tickets by yourself.


I've seen your pull-request. However please get to know the details of 
pull-request based contribution

https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-1.CreateGitHubpull-request

and when everything is ready please move the ticket, as the doc says, to 
"patch available" state and ask for the review on the dev list.


Thanks,
Denis

On 2/9/2016 8:43 PM, Konstantin Margorin wrote:

I created account "ruskim" in jira.

Should I ask someone to assign ticket IGNITE-2555 to me, or I could create
pull request as is?

On Tue, Feb 9, 2016 at 3:25 PM, Konstantin Margorin 
wrote:


Vladimir, thank you.

I could handle this one:
https://issues.apache.org/jira/browse/IGNITE-2555

Konstantin

On Tue, Feb 9, 2016 at 3:11 PM, Vladimir Ozerov 
wrote:


Konstantin,

This ticket is more about build process. You can also look at the
following
ones:
https://issues.apache.org/jira/browse/IGNITE-1783
https://issues.apache.org/jira/browse/IGNITE-2555

Vladimir.

On Tue, Feb 9, 2016 at 2:57 PM, Konstantin Margorin 
wrote:


Hi Vladimir.

I had searched through open tickets for newbies. And looks like the only
open unassigned ticked is:
https://issues.apache.org/jira/browse/IGNITE-2049

Is this ticket right point to start?

Best regards,
Konstantin

On Tue, Feb 9, 2016 at 2:30 PM, Vladimir Ozerov 
wrote:


Konstantin, sorry I confused the name.

Should you have any further questions please feel free to ask.

On Tue, Feb 9, 2016 at 2:29 PM, Vladimir Ozerov 

[jira] [Created] (IGNITE-2606) Drop in Replacement for Apache YARN

[Suminda Dharmasena (JIRA)]

Suminda Dharmasena created IGNITE-2606:
--

 Summary: Drop in Replacement for Apache YARN
 Key: IGNITE-2606
 URL: https://issues.apache.org/jira/browse/IGNITE-2606
 Project: Ignite
  Issue Type: New Feature
Reporter: Suminda Dharmasena






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2607) Drop in Replacement for ZooKeeper

[Suminda Dharmasena (JIRA)]

Suminda Dharmasena created IGNITE-2607:
--

 Summary: Drop in Replacement for ZooKeeper
 Key: IGNITE-2607
 URL: https://issues.apache.org/jira/browse/IGNITE-2607
 Project: Ignite
  Issue Type: New Feature
Reporter: Suminda Dharmasena






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Hello

[Pavel Konstantinov]

Konstantin, could you please add one more metric - node up time.
I think this metric may be added to the first row:

 ^-- Node [id=41b12e0f, name=null]


On Wed, Feb 10, 2016 at 4:59 AM, Denis Magda  wrote:

> Hi Konstantin, welcome!
>
> Added you to the contributors list in JIRA. So for now you're able to
> assign tickets by yourself.
>
> I've seen your pull-request. However please get to know the details of
> pull-request based contribution
>
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-1.CreateGitHubpull-request
>
> and when everything is ready please move the ticket, as the doc says, to
> "patch available" state and ask for the review on the dev list.
>
> Thanks,
> Denis
>
>
> On 2/9/2016 8:43 PM, Konstantin Margorin wrote:
>
>> I created account "ruskim" in jira.
>>
>> Should I ask someone to assign ticket IGNITE-2555 to me, or I could create
>> pull request as is?
>>
>> On Tue, Feb 9, 2016 at 3:25 PM, Konstantin Margorin 
>> wrote:
>>
>> Vladimir, thank you.
>>>
>>> I could handle this one:
>>> https://issues.apache.org/jira/browse/IGNITE-2555
>>>
>>> Konstantin
>>>
>>> On Tue, Feb 9, 2016 at 3:11 PM, Vladimir Ozerov 
>>> wrote:
>>>
>>> Konstantin,

 This ticket is more about build process. You can also look at the
 following
 ones:
 https://issues.apache.org/jira/browse/IGNITE-1783
 https://issues.apache.org/jira/browse/IGNITE-2555

 Vladimir.

 On Tue, Feb 9, 2016 at 2:57 PM, Konstantin Margorin 
 wrote:

 Hi Vladimir.
>
> I had searched through open tickets for newbies. And looks like the
> only
> open unassigned ticked is:
> https://issues.apache.org/jira/browse/IGNITE-2049
>
> Is this ticket right point to start?
>
> Best regards,
> Konstantin
>
> On Tue, Feb 9, 2016 at 2:30 PM, Vladimir Ozerov 
> wrote:
>
> Konstantin, sorry I confused the name.
>>
>> Should you have any further questions please feel free to ask.
>>
>> On Tue, Feb 9, 2016 at 2:29 PM, Vladimir Ozerov > wrote:
>>
>> Hi Carlos,
>>>
>>> Welcome to the Ignite community!
>>>
>>> You should get familiar with Ignite development process described
>>>
>> here:
 https://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

> Once you got familiar and were able to run a few examples, you
>>>
>> should

> pick
>>
>>> a Jira ticket you would like to start on. Send an email to the dev
>>>
>> list,
>
>> so
>>
>>> we can add you as a contributor in Jira.
>>>
>>> You can find interesting tickets to get started here:
>>> https://ignite.apache.org/community/contribute.html#pick-ticket
>>>
>>> Looking forward to your contributions!
>>>
>>> Regards,
>>> Vladimir.
>>>
>>>
>>> On Tue, Feb 9, 2016 at 12:58 PM, Konstantin Margorin <
>>>
>> rus...@gmail.com

> wrote:
>>>
>>> Hi All,

 I'm Konstantin Margorin from Anturis.

 I would like to contribute my effort on Apache Ignite project and
 appreciate if I could join with you.

 Looking forward to your reply.

 Best regards,
 Konstantin


>>>
>>>
>


-- 
Pavel Konstantinov, QA Engineer
GridGain Systems
www.gridgain.com

Re: Hello

[Konstantin Margorin]

Sure, I'll do that.

Just a small question: is everything ok with my pull request, or I missed
something in documentation?

On Wed, Feb 10, 2016 at 9:00 AM, Pavel Konstantinov <
pkonstanti...@gridgain.com> wrote:

> Konstantin, could you please add one more metric - node up time.
> I think this metric may be added to the first row:
>
>  ^-- Node [id=41b12e0f, name=null]
>
>
> On Wed, Feb 10, 2016 at 4:59 AM, Denis Magda  wrote:
>
> > Hi Konstantin, welcome!
> >
> > Added you to the contributors list in JIRA. So for now you're able to
> > assign tickets by yourself.
> >
> > I've seen your pull-request. However please get to know the details of
> > pull-request based contribution
> >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-1.CreateGitHubpull-request
> >
> > and when everything is ready please move the ticket, as the doc says, to
> > "patch available" state and ask for the review on the dev list.
> >
> > Thanks,
> > Denis
> >
> >
> > On 2/9/2016 8:43 PM, Konstantin Margorin wrote:
> >
> >> I created account "ruskim" in jira.
> >>
> >> Should I ask someone to assign ticket IGNITE-2555 to me, or I could
> create
> >> pull request as is?
> >>
> >> On Tue, Feb 9, 2016 at 3:25 PM, Konstantin Margorin 
> >> wrote:
> >>
> >> Vladimir, thank you.
> >>>
> >>> I could handle this one:
> >>> https://issues.apache.org/jira/browse/IGNITE-2555
> >>>
> >>> Konstantin
> >>>
> >>> On Tue, Feb 9, 2016 at 3:11 PM, Vladimir Ozerov 
> >>> wrote:
> >>>
> >>> Konstantin,
> 
>  This ticket is more about build process. You can also look at the
>  following
>  ones:
>  https://issues.apache.org/jira/browse/IGNITE-1783
>  https://issues.apache.org/jira/browse/IGNITE-2555
> 
>  Vladimir.
> 
>  On Tue, Feb 9, 2016 at 2:57 PM, Konstantin Margorin  >
>  wrote:
> 
>  Hi Vladimir.
> >
> > I had searched through open tickets for newbies. And looks like the
> > only
> > open unassigned ticked is:
> > https://issues.apache.org/jira/browse/IGNITE-2049
> >
> > Is this ticket right point to start?
> >
> > Best regards,
> > Konstantin
> >
> > On Tue, Feb 9, 2016 at 2:30 PM, Vladimir Ozerov <
> voze...@gridgain.com>
> > wrote:
> >
> > Konstantin, sorry I confused the name.
> >>
> >> Should you have any further questions please feel free to ask.
> >>
> >> On Tue, Feb 9, 2016 at 2:29 PM, Vladimir Ozerov <
> voze...@gridgain.com
> >> wrote:
> >>
> >> Hi Carlos,
> >>>
> >>> Welcome to the Ignite community!
> >>>
> >>> You should get familiar with Ignite development process described
> >>>
> >> here:
> 
> https://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
> 
> > Once you got familiar and were able to run a few examples, you
> >>>
> >> should
> 
> > pick
> >>
> >>> a Jira ticket you would like to start on. Send an email to the dev
> >>>
> >> list,
> >
> >> so
> >>
> >>> we can add you as a contributor in Jira.
> >>>
> >>> You can find interesting tickets to get started here:
> >>> https://ignite.apache.org/community/contribute.html#pick-ticket
> >>>
> >>> Looking forward to your contributions!
> >>>
> >>> Regards,
> >>> Vladimir.
> >>>
> >>>
> >>> On Tue, Feb 9, 2016 at 12:58 PM, Konstantin Margorin <
> >>>
> >> rus...@gmail.com
> 
> > wrote:
> >>>
> >>> Hi All,
> 
>  I'm Konstantin Margorin from Anturis.
> 
>  I would like to contribute my effort on Apache Ignite project and
>  appreciate if I could join with you.
> 
>  Looking forward to your reply.
> 
>  Best regards,
>  Konstantin
> 
> 
> >>>
> >>>
> >
>
>
> --
> Pavel Konstantinov, QA Engineer
> GridGain Systems
> www.gridgain.com
>

[jira] [Created] (IGNITE-2609) Add validation on new name of clon object

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-2609:
-

 Summary: Add validation on new name of clon object 
 Key: IGNITE-2609
 URL: https://issues.apache.org/jira/browse/IGNITE-2609
 Project: Ignite
  Issue Type: Sub-task
  Components: wizards
Affects Versions: 1.6
Reporter: Vasiliy Sisko
Assignee: Vasiliy Sisko


# Domain models: On clone new name should be a valid Java class name.
# On input of already exist name extend name to make it unique. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2608) Add key fields into valu fields while importing model from DB in corner case

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-2608:
--

 Summary: Add key fields into valu fields while importing model 
from DB in corner case
 Key: IGNITE-2608
 URL: https://issues.apache.org/jira/browse/IGNITE-2608
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Konstantinov
Assignee: Vasiliy Sisko
Priority: Minor


I'm imported model from some database and faced with tables which has only 
primary key fields. In this case we currently don't generate value fields at 
all. In run time in visor I got an NPE exception.
In this corner case we should add all key fields into value fields 
automatically.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2610) Excessive memory usage in GridCacheTtlManager.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-2610:
---

 Summary: Excessive memory usage in GridCacheTtlManager.
 Key: IGNITE-2610
 URL: https://issues.apache.org/jira/browse/IGNITE-2610
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.5.0.final
Reporter: Vladimir Ozerov
Priority: Critical
 Fix For: 1.6


*Problem*
When key is updated with new value and new expiry policy, old entry is not 
removed from "pendingEntries". It leads to excessive memory consumption.

*Steps to reproduce*
1) Create a cache
2) Put a lot of entries with same key, but different expiry policies one by one.
3) Observe trashed "pendingEntries".

Concrete fix is to be defined.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: EntryProcessor in ATOMIC cache and CLOCK versioning mode

[Dmitriy Setrakyan]

I don’t think there is anything else that can be done in addition to
printing our a warning and fixing documentation. Looks like an easy fix, I
marked it with “newbie”, so some of the new community members could pick it
up.

On Tue, Feb 9, 2016 at 5:17 AM, Alexey Goncharuk  wrote:

> After a second thought, I think the warning should be printed anyways when
> CLOCK versioning mode is used because it does not guarantee happens-before
> relationship when cache operations are invoked on different nodes (see an
> example in pseudo-code below). Essentially, when cache operations are
> invoked on different nodes within a time span smaller or equal than time
> sync error, they are considered to be run concurrently.
>
> IgniteCache cache = ignite.cache("name");
>
> cache.put(1, 1);
>
> // Select a random remote node.
> ClusterGroup grp = ignite.cluster().forRemotes().forRandom();
>
> ignite.compute(grp).call(new Callable() {
> public Object call() throws Exception {
> cache.put(1, 2); // This does not guarantee to succeed in CLOCK
> mode.
> }
> });
>
> // This may fail in CLOCK mode.
> assert cache.get(1) == 2;
>
> I agree that the documentation must be updated accordingly, and I think the
> warning printed should contain a link to the page.
>
> Any other thoughts?
>

Re: Hello

[Konstantin Margorin]

I created account "ruskim" in jira.

Should I ask someone to assign ticket IGNITE-2555 to me, or I could create
pull request as is?

On Tue, Feb 9, 2016 at 3:25 PM, Konstantin Margorin 
wrote:

> Vladimir, thank you.
>
> I could handle this one:
> https://issues.apache.org/jira/browse/IGNITE-2555
>
> Konstantin
>
> On Tue, Feb 9, 2016 at 3:11 PM, Vladimir Ozerov 
> wrote:
>
>> Konstantin,
>>
>> This ticket is more about build process. You can also look at the
>> following
>> ones:
>> https://issues.apache.org/jira/browse/IGNITE-1783
>> https://issues.apache.org/jira/browse/IGNITE-2555
>>
>> Vladimir.
>>
>> On Tue, Feb 9, 2016 at 2:57 PM, Konstantin Margorin 
>> wrote:
>>
>> > Hi Vladimir.
>> >
>> > I had searched through open tickets for newbies. And looks like the only
>> > open unassigned ticked is:
>> > https://issues.apache.org/jira/browse/IGNITE-2049
>> >
>> > Is this ticket right point to start?
>> >
>> > Best regards,
>> > Konstantin
>> >
>> > On Tue, Feb 9, 2016 at 2:30 PM, Vladimir Ozerov 
>> > wrote:
>> >
>> > > Konstantin, sorry I confused the name.
>> > >
>> > > Should you have any further questions please feel free to ask.
>> > >
>> > > On Tue, Feb 9, 2016 at 2:29 PM, Vladimir Ozerov > >
>> > > wrote:
>> > >
>> > > > Hi Carlos,
>> > > >
>> > > > Welcome to the Ignite community!
>> > > >
>> > > > You should get familiar with Ignite development process described
>> here:
>> > > >
>> https://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
>> > > >
>> > > > Once you got familiar and were able to run a few examples, you
>> should
>> > > pick
>> > > > a Jira ticket you would like to start on. Send an email to the dev
>> > list,
>> > > so
>> > > > we can add you as a contributor in Jira.
>> > > >
>> > > > You can find interesting tickets to get started here:
>> > > > https://ignite.apache.org/community/contribute.html#pick-ticket
>> > > >
>> > > > Looking forward to your contributions!
>> > > >
>> > > > Regards,
>> > > > Vladimir.
>> > > >
>> > > >
>> > > > On Tue, Feb 9, 2016 at 12:58 PM, Konstantin Margorin <
>> rus...@gmail.com
>> > >
>> > > > wrote:
>> > > >
>> > > >> Hi All,
>> > > >>
>> > > >> I'm Konstantin Margorin from Anturis.
>> > > >>
>> > > >> I would like to contribute my effort on Apache Ignite project and
>> > > >> appreciate if I could join with you.
>> > > >>
>> > > >> Looking forward to your reply.
>> > > >>
>> > > >> Best regards,
>> > > >> Konstantin
>> > > >>
>> > > >
>> > > >
>> > >
>> >
>>
>
>