Re: OptimizedClassDescriptor verifyChecksum object set as optional

Hi, As I understand both servers have different implementations but the names of those implementations are the same, correct? Because otherwise I don't see how your code could get to the point of checksum validation if one implementation's name is ServiceEntity while the other's is

Re: Random eviction policy

On Mon, Nov 9, 2015 at 7:22 PM, Alexey Kuznetsov wrote: > I see that we have this issue: > *IGNITE-1817 Deprecate RandomEvictionPolicy and IgniteCache.randomEntry > method * > https://issues.apache.org/jira/browse/IGNITE-1817 > > It seems that we should remove

Re: Do we really need separate class for store configuration?

Alexey, I agree with you. I think it make sense to abandon CacheJdbcPojoStoreConfiguration and move all the configuration properties directly to the factory. It looks like there are no objections, so please go ahead and update the ticket. Thanks, D. On Thu, Nov 5, 2015 at 6:28 AM, Alexey

[GitHub] ignite pull request: IGNITE-1853 added ability to inject extension...

GitHub user Dmitriyff opened a pull request: https://github.com/apache/ignite/pull/211 IGNITE-1853 added ability to inject extension for app You can merge this pull request into a Git repository by running: $ git pull https://github.com/Dmitriyff/ignite ignite-1853

Re: IGNITE-1527 Add OSGi manifest headers

Yes, it's done. Please check the branch. I'm working on finishing the features.xml. Hopefully done this evening or tomorrow. On 9 Nov 2015 16:47, "Romain Gilles" wrote: > Hi Raoul, > Did you start on this task? I will be please to help you on it. > > Romain. >

Re: Rebalancing speedup (IGNITE-1093)

Hello, I've finished work on IGNITE-1093 & merged changes to master & 1.5. Results listed at Issue Main results are: - Speed of rebalancing in case node joined increased ~twice (default settings) at the same grid throughput, - No GC hell happens

About the newbie bug #IGNITE-881

Hi Yakov Zhdanov, I am going to work on the bug https://issues.apache.org/jira/browse/IGNITE-881. you commented as # Move handling logic to GridCacheCommandHandler but I found there is already a class do the same thing in the DataStructuresCommandHandler.java Can you give more clue about

Re: OptimizedClassDescriptor verifyChecksum object set as optional

Hi, I'm against optional checksum verification. It's not safe, adds one more configuration property and I don't see any use case that can require this. I also don't completely understand what you're trying to achieve. Can you please describe the sequence of serialization/deserialization events

Re: LOCAL cache serializes the entries?

On Sat, Nov 7, 2015 at 8:28 AM, Andrey Kornev wrote: > Dmitriy, > > How would that help me if, for example, my cache entries held references > to some other non-"binarylizable" ;) resources (like JDBC connection, > socket, etc)? In other words, in my case the cache

[jira] [Created] (IGNITE-1874) Adjust initial placement and size of metadada popup on SQL

Pavel Konstantinov created IGNITE-1874: -- Summary: Adjust initial placement and size of metadada popup on SQL Key: IGNITE-1874 URL: https://issues.apache.org/jira/browse/IGNITE-1874 Project:

Re: OptimizedClassDescriptor verifyChecksum object set as optional

Hi: The implementations name maybe not same. Like my example: class DataEntity { Integer id; string name; Integer age; ….. and other Externalizable.read(in){