[GitHub] ignite pull request: IGNITE-2555 fix

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

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

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

Hello

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 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

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

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

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

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

[GitHub] ignite pull request: IGNITE-2523

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

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

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

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

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:

Re: Hello

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

Re: Hello

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

Re: Hello

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

Re: Hello

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: >

RE: EntryProcessor in ATOMIC cache and CLOCK versioning mode

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

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

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

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

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

Re: EntryProcessor in ATOMIC cache and CLOCK versioning mode

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

Re: Hello

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:

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

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

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

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

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

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:

Re: Hello

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

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

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:

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

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:

Re: Hello

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

Re: Hello

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

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

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:

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

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

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

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

Re: EntryProcessor in ATOMIC cache and CLOCK versioning mode

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

Re: Hello

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: >