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 this

Re: OptimizedClassDescriptor verifyChecksum object set as optional

Hi, +1 to Val. Actually if you have different class names on different machines (DataEntity, ServiceEntity) I don't realize how you can get to the checksum validation stage. In my understanding you should have caught ClassNotFoundException. Provide me with a full runnable example, I'll run a

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 th

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

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 RandomEvictionPolicy from Ignite Con

Random eviction policy

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 RandomEvictionPolicy from Ignite Console UI / code generation too. Am I right? -- Alexey Kuznetsov Grid

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 Kuznets

Re: OSGi migration may require a special marshaller

Thanks Raul, great points! I have created a ticket for the class-loader-detection design, described on wiki: https://issues.apache.org/jira/browse/IGNITE-1877 D. On Mon, Nov 9, 2015 at 3:42 PM, Raul Kripalani wrote: > Hey Romain, > > I've updated the design proposal in the Wiki with my input.

[jira] [Created] (IGNITE-1877) Add ClassLoaderCodec for OSGI support

Dmitriy Setrakyan created IGNITE-1877: - Summary: Add ClassLoaderCodec for OSGI support Key: IGNITE-1877 URL: https://issues.apache.org/jira/browse/IGNITE-1877 Project: Ignite Issue Type:

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){ if(in.re

Re: Web console - No java code on summary page?

Prach, It looks like a bug. It seems like latest changes in java code generator lack "null/undefined" checks in special cases. Will be fixed today. Thanks. On Tue, Nov 10, 2015 at 5:44 AM, Prachi Garg wrote: > Hi, > > On the 'Summary' page, I don't see any Java code for the Server and Client

Re: OSGi migration may require a special marshaller

Hey Romain, I've updated the design proposal in the Wiki with my input. Could you please have a look and let me know what you think? I'll implement a proof of concept of my proposed marshalling/unmarshalling strategy and push it to Git so you can take it for a spin. Regards, *Raúl Kripalani* PM

Web console - No java code on summary page?

Hi, On the 'Summary' page, I don't see any Java code for the Server and Client configuration anymore. It was fine before. In fact, there is no XML code for client configuration when I land on that page, unless I set the near cache configuration. Is this a bug or this is how it is supposed to behav

Re: IGNITE-1527 Add OSGi manifest headers

By the way, I'm working on the OSGi integration actively. I just had to take a break last week, but I'm on it. On 9 Nov 2015 18:02, "Raul Kripalani" wrote: > 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

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)

Thanks Anton! It is always exhilarating to see performance improvements :) On Mon, Nov 9, 2015 at 7:30 AM, Anton Vinogradov wrote: > Hello, > I've finished work on IGNITE-1093 & merged changes to master & 1.5. > Results listed at Issue > > > M

[GitHub] ignite pull request: IGNITE-1845 .Net: Adopt portable API changes.

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/210 IGNITE-1845 .Net: Adopt portable API changes. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-1845-1 Alternatively yo

IGNITE-1527 Add OSGi manifest headers

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

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

Re: GIT branch audit

Artem, sounds good. Maybe we should add "Reason for deletion"? On Mon, Nov 9, 2015 at 5:59 PM, Artem Shutak wrote: > Igniters, > > Since no one can delete any branch Apache Git repo I've been created > https://cwiki.apache.org/confluence/display/IGNITE/Git+branches+to+delete > with information

[jira] [Created] (IGNITE-1876) Access to a non-existing entry produces events

Sergey Kozlov created IGNITE-1876: - Summary: Access to a non-existing entry produces events Key: IGNITE-1876 URL: https://issues.apache.org/jira/browse/IGNITE-1876 Project: Ignite Issue Type:

Re: GIT branch audit

Igniters, Since no one can delete any branch Apache Git repo I've been created https://cwiki.apache.org/confluence/display/IGNITE/Git+branches+to+delete with information about "out-dated" branches. I think we should track "Branches to delete" there and then ask Apache Infra for batch deletion bas

[jira] [Created] (IGNITE-1875) SCAN for default cache does not work

Pavel Konstantinov created IGNITE-1875: -- Summary: SCAN for default cache does not work Key: IGNITE-1875 URL: https://issues.apache.org/jira/browse/IGNITE-1875 Project: Ignite Issue Type

[GitHub] ignite pull request: IGNITE-1428 .Net: Use struct with fixed layou...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/209 IGNITE-1428 .Net: Use struct with fixed layout for InteropMemory operations. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite

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

[jira] [Created] (IGNITE-1873) .Net: Investigate BinaryFormatter vs DataContractSerializer vs XmlSerializer

Pavel Tupitsyn created IGNITE-1873: --- Summary: .Net: Investigate BinaryFormatter vs DataContractSerializer vs XmlSerializer Key: IGNITE-1873 URL: https://issues.apache.org/jira/browse/IGNITE-1873 Pr

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 entries are not plain > Java be

[jira] [Created] (IGNITE-1872) Remove Binaries.builder(int) method.

Vladimir Ozerov created IGNITE-1872: --- Summary: Remove Binaries.builder(int) method. Key: IGNITE-1872 URL: https://issues.apache.org/jira/browse/IGNITE-1872 Project: Ignite Issue Type: Task