Re: Hello

Hi Putin, Welcome to Ignite community! We definitely can use your help. The best way to get started, is to download the project and play with examples: https://github.com/apache/ignite/tree/master/examples You should also get familiar with available Ignite resources, like Wiki, Jira, etc:

Re: Hello Igniters

Hi Saikat, Welcome to the Ignite community! We definitely can use your help. The best way to get started, is to download the project and play with examples: https://github.com/apache/ignite/tree/master/examples You should also get familiar with available Ignite resources, like Wiki, Jira, etc:

[jira] [Created] (IGNITE-1731) [Test Failed] GridCacheTxNodeFailureSelfTest.testPrimaryNodeFailureBackupRollbackOptimistic

Artem Shutak created IGNITE-1731: Summary: [Test Failed] GridCacheTxNodeFailureSelfTest.testPrimaryNodeFailureBackupRollbackOptimistic Key: IGNITE-1731 URL: https://issues.apache.org/jira/browse/IGNITE-1731

Re: Hello

On Mon, Oct 19, 2015 at 1:09 AM, Dmitriy Setrakyan wrote: > Hi Putin, > Sorry for the typo, I meant to say “Hi, Pulin” > Welcome to Ignite community! We definitely can use your help. > > The best way to get started, is to download the project and play with > examples: >

[GitHub] ignite pull request: ignite-1718 Fix of 'Not enough data to read t...

GitHub user agura opened a pull request: https://github.com/apache/ignite/pull/165 ignite-1718 Fix of 'Not enough data to read the value' and 'No class definition for typeId: 0' in portable marshaller You can merge this pull request into a Git repository by running: $ git

[jira] [Created] (IGNITE-1733) ComputeScheduleExample should be removed into example-lgpl project

Vasilisa Sidorova created IGNITE-1733: -- Summary: ComputeScheduleExample should be removed into example-lgpl project Key: IGNITE-1733 URL: https://issues.apache.org/jira/browse/IGNITE-1733

withKeepIgniteObject behavior

Igniters, As a part of work on IGNITE-950 [1] ticket we wanted to implement a functionality which would allow users to plug their own implementation of IgniteObject, which in turn would allow to introspect objects for fields without deserialization and use of reflection. The design draft is

[jira] [Created] (IGNITE-1734) ScalarCachePopularNumbersExample fails and loops when it's running with jdkMarshaller

Vasilisa Sidorova created IGNITE-1734: -- Summary: ScalarCachePopularNumbersExample fails and loops when it's running with jdkMarshaller Key: IGNITE-1734 URL:

[GitHub] ignite pull request: Fixed GridUriDeploymentClassLoaderSelfTest#te...

GitHub user ashutakGG opened a pull request: https://github.com/apache/ignite/pull/166 Fixed GridUriDeploymentClassLoaderSelfTest#testNestedJarClassloading Fixed test after https://issues.apache.org/jira/browse/IGNITE-1559. You can merge this pull request into a Git repository by

Re: withKeepIgniteObject behavior

Alexey, I am not sure what will be passed into the EntryProcessor, specifically in your example, EP and EP2. Will it be an instance of IgniteObject or a deserialized instance? In my view, we must support both, because server side may not, and most likely, will not have client-side class

Asc and desc index on same field.

Igniters, I found that I cannot have asc and desc index on same field (exception will be thrown). This happen because we give index name as field name without Asc/Desc/UUID/global_Id suffix. All databases allow to have asc and desc index on same field. We could easily support this in Ignite too.