Re: Cluster group affinity

Andrey, > 1) I'm expected to return an instance of the internal class > AffinityTopologyVersion. If you are talking about AffinityContextFunction.currentTopologyVersion method then for now this method is nowhere uses. But it make sense to return non null value in order to avoid problems in the

Re: Cluster group affinity

On Tue, Oct 6, 2015 at 8:46 AM, Andrey Kornev wrote: > Thanks, Andrey! This definitely helps. > > It's just that implementing such a simple feature in the "user space" > feels awkward and requires intimate knowledge of fairly low-level details > of how things work in

Re: Why portable marshaller handle Date and Timestamp in the same way?

I would definitely remove such a mapping if no one explains a reason we have it. -- Denis On 10/6/2015 10:26 AM, Vladimir Ozerov wrote: Igniters, For some reason we "merged" Date and Timestamp types in portable marshaller. They are both written in the same format with the same type ID. And

Re: Why portable marshaller handle Date and Timestamp in the same way?

Keep in mind that separating them can introduce difficulties for other platforms. For example, DateTime in .Net has more precision (100ns vs 1ms in Java). Serializing this in Java format will lead to data loss. Serializing .Net DateTime as Timestamp will preserve precision, but may hurt

Re: Why portable marshaller handle Date and Timestamp in the same way?

On Tue, Oct 6, 2015 at 2:42 AM, Vladimir Ozerov wrote: > This doesn't answers the question. First, Java Timestamp has greater > precision than .Net DateTime, so silent data loss could happen in this case > as well. Second, "use timestamp" is defined on class level. It means

Re: Cluster group affinity

Maybe I don't quite get your point, Andrey, but to me, the cache affinity nodes could just be equally expressed as a ClusterGroup.forCache(...) cluster group. Then, why can't Ignite expose just a single method that takes a cluster group (rather than a cache name) as a parameter and returns an

Re: Why portable marshaller handle Date and Timestamp in the same way?

Yakov, this could work in .Net where you have real generics. But it will not work in Java in general case due to type erasure - you simply cannot infer the type. Let's look closely to this: Date Java: 10^-3 Timestamp Java: 10^-9 DateTime .Net: 10^-7 What we see here, is that mapping Java

Re: 'How to Contribute' wiki page updated.

Dmitriy, I've fixed page according to your request except: >- "Release Process" section should be a numbered list describing steps >(including QA branch) necessary to create a release. As far as I understans there is no QA's at Ignite community. GridGain QAs can provide some help, but

Re: Cluster group affinity

Andrey, See AffinityFunction.assignPartitions method. It returns assignment list as List where index of element in returned list corresponds to partition number. Assignment for each partition represented as list of nodes where primary node is always the first. So you can use existing

Re: Why portable marshaller handle Date and Timestamp in the same way?

On 06.10.2015 12:26, Vladimir Ozerov wrote: > Yakov, this could work in .Net where you have real generics. But it will > not work in Java in general case due to type erasure - you simply cannot > infer the type. > > Let's look closely to this: > Date Java: 10^-3 > Timestamp Java: 10^-9 >

[GitHub] ignite pull request: IGNITE-1619 Platform .Net: Generic type is lo...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/136 IGNITE-1619 Platform .Net: Generic type is lost during array/collection serialization You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request: IGNITE-638: Implements cache distributed sema...

GitHub user vladisav reopened a pull request: https://github.com/apache/ignite/pull/120 IGNITE-638: Implements cache distributed semaphore This interface provides a rich API for working with distributed semaphore. Distributed semaphore provides functionality similar to

[GitHub] ignite pull request: IGNITE-638: Implements cache distributed sema...

Github user vladisav closed the pull request at: https://github.com/apache/ignite/pull/120 --- 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