[jira] [Created] (IGNITE-2894) Binary object inside of Externalizable still serialized with OptimizedMarshaller

Valentin Kulichenko created IGNITE-2894: --- Summary: Binary object inside of Externalizable still serialized with OptimizedMarshaller Key: IGNITE-2894 URL: https://issues.apache.org/jira/browse/IGNITE-2894

[GitHub] ignite pull request: IGNITE-2889 .NET: Add IBinaryNameMapper tests

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

[GitHub] ignite pull request: IGNITE-2882 .NET: Fix JNI init error propagat...

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

Re: Transactions in atomics

Here we go: https://issues.apache.org/jira/browse/IGNITE-2893 -Val On Thu, Mar 24, 2016 at 1:33 AM, Yakov Zhdanov wrote: > Val, can you please file a newbie ticket for this (if it is not there > already)? > > --Yakov > > 2016-03-11 9:51 GMT+03:00 Valentin Kulichenko < > valentin.kuliche...@gmai

[jira] [Created] (IGNITE-2893) Atomic structures should not use transactions

Valentin Kulichenko created IGNITE-2893: --- Summary: Atomic structures should not use transactions Key: IGNITE-2893 URL: https://issues.apache.org/jira/browse/IGNITE-2893 Project: Ignite

Re: Ambari Plugin

Hi Vladimir and Michael, Srimanth wrote a great wiki on how to add a service to Ambari, https://cwiki.apache.org/confluence/display/AMBARI/How-To+Define+Stacks+and +Services How is Apache Ignite packaged? You may be able to install it via RPMs or wget. What are the requirements of your service?

[jira] [Created] (IGNITE-2892) High volume data Cache with custom object

Subhasis created IGNITE-2892: Summary: High volume data Cache with custom object Key: IGNITE-2892 URL: https://issues.apache.org/jira/browse/IGNITE-2892 Project: Ignite Issue Type: Test

RE: All BinaryObjects created by BinaryObjectBuilder stored at the same partition by default

This is a nasty problem that is very difficult to track especially for beginners. But I think it's easy to solve: since the BinaryObjects are built exclusively using the BinaryObjectBuilder, you can simply implement a check in the BinaryObjectBuilder.build() to see whether or not BinaryObjectBu

RE: All BinaryObjects created by BinaryObjectBuilder stored at the same partition by default

This is a nasty problem that is very difficult to track especially for beginners. But I think it's easy to solve: since the BinaryObjects are built exclusively using the BinaryObjectBuilder, you can simply implement a check in the BinaryObjectBuilder.build() to see whether or not BinaryObjectBu

Re: IGNITE-1071 IgniteCache.metrics() method returns local metrics

On Thu, Mar 24, 2016 at 5:35 AM, Anton Vinogradov wrote: > Do we need local metrics at IgniteCache? > Yes, I don’t see any reason why not. Let’s just follow the naming pattern and prefix all local methods with the word “local”. > > On Thu, Mar 24, 2016 at 3:02 PM, Vladimir Ozerov > wrote: > >

Re: About https://apacheignite-fs.readme.io/docs

Hi, I think you are right, the content is similar. The only change is that it was separated from the main documentation. D. On Thu, Mar 24, 2016 at 5:12 AM, 李玉珏@163 <18624049...@163.com> wrote: > Hi： > > https://apacheignite-fs.readme.io/docs > This site has a similar > https://github.com/apach

[jira] [Created] (IGNITE-2891) Can't start ggvisorui.sh (ignite.sh etc) on CygWIN

knivit created IGNITE-2891: -- Summary: Can't start ggvisorui.sh (ignite.sh etc) on CygWIN Key: IGNITE-2891 URL: https://issues.apache.org/jira/browse/IGNITE-2891 Project: Ignite Issue Type: Bug A

Re: Serialization exception when migrating from 1.3 to 1.5

There turned out to be a stray Ignite instance referenced in a field in the CacheStore implementation. I've refactored to remove that and now 1.5 is working fine. -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Serialization-exception-when-migrating-from-

[GitHub] ignite pull request: IGNITE-2889 .NET: Add IBinaryNameMapper tests

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/578 IGNITE-2889 .NET: Add IBinaryNameMapper tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-2889 Alternatively you

[jira] [Created] (IGNITE-2890) .NET: Add CacheConfiguration.NodeFilter

Pavel Tupitsyn created IGNITE-2890: -- Summary: .NET: Add CacheConfiguration.NodeFilter Key: IGNITE-2890 URL: https://issues.apache.org/jira/browse/IGNITE-2890 Project: Ignite Issue Type: Impr

[GitHub] ignite pull request: IGNITE-2873 .NET: Support .NET configuration ...

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

[GitHub] ignite pull request: IGNITE-2872 .NET: Undeprecate IgniteConfigura...

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

[GitHub] ignite pull request: IGNITE-2866 .NET: Automatic JAVA_HOME detecti...

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

[GitHub] ignite pull request: IGNITE-2870 .NET: Fix index names for nested ...

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

[jira] [Created] (IGNITE-2889) .NET: Add IBinaryNameMapper tests

Pavel Tupitsyn created IGNITE-2889: -- Summary: .NET: Add IBinaryNameMapper tests Key: IGNITE-2889 URL: https://issues.apache.org/jira/browse/IGNITE-2889 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-2888) Eviction policy not called upon cache.remove()

Avihai Berkovitz created IGNITE-2888: Summary: Eviction policy not called upon cache.remove() Key: IGNITE-2888 URL: https://issues.apache.org/jira/browse/IGNITE-2888 Project: Ignite Issue

[jira] [Created] (IGNITE-2887) .NET: Add platform interoperability documentation

Pavel Tupitsyn created IGNITE-2887: -- Summary: .NET: Add platform interoperability documentation Key: IGNITE-2887 URL: https://issues.apache.org/jira/browse/IGNITE-2887 Project: Ignite Issue

Re: IGNITE-1071 IgniteCache.metrics() method returns local metrics

Do we need local metrics at IgniteCache? On Thu, Mar 24, 2016 at 3:02 PM, Vladimir Ozerov wrote: > + 1 to Anton and Alexey suggestions. Having both local and global MBeans > should do the trick. > > On Thu, Mar 24, 2016 at 2:47 PM, Alexey Kuznetsov > > wrote: > > > Could we have local and globa

Re: Ambrai Plugin

Hi Mike, Integration with widely adopted monitoring tools such as Ambari could be very valuable addition to our IGFS/Hadoop ecosystem. Probably we can start with very trivial implementation allowing to simply start/stop Ignite nodes, and then gradually improve it to a fully-fledged monitoring tool

[jira] [Created] (IGNITE-2886) IGFS: Implement INotify intergration.

Vladimir Ozerov created IGNITE-2886: --- Summary: IGFS: Implement INotify intergration. Key: IGNITE-2886 URL: https://issues.apache.org/jira/browse/IGNITE-2886 Project: Ignite Issue Type: Task

About https://apacheignite-fs.readme.io/docs

Hi： https://apacheignite-fs.readme.io/docs This site has a similar https://github.com/apacheignite/documentation/tree/v1.5 such backup? If not, is there anyone in the community can help me to get a copy of this document from readme.io and send it to my mailbox? I want to make a synchronizatio

Re: HDFS iNotify

Hi Mike, I think this in general this is very good idea. For now IGFS has a restriction that all file system operations should go through it. Otherwise IGFS will end up in inconsistent state. INofity could resolve this limitation. However, I this is not easy task for several reasons: 1) INotify is

Re: IGNITE-1071 IgniteCache.metrics() method returns local metrics

+ 1 to Anton and Alexey suggestions. Having both local and global MBeans should do the trick. On Thu, Mar 24, 2016 at 2:47 PM, Alexey Kuznetsov wrote: > Could we have local and global MBeans? > Or local and global metrics inside same MBean? > > On Thu, Mar 24, 2016 at 6:26 PM, Anton Vinogradov <

Re: IGNITE-1071 IgniteCache.metrics() method returns local metrics

Could we have local and global MBeans? Or local and global metrics inside same MBean? On Thu, Mar 24, 2016 at 6:26 PM, Anton Vinogradov wrote: > Hello, > > I'd like to discuss > IGNITE-1071 IgniteCache.metrics() method returns local metrics > >

[GitHub] ignite pull request: IGNITE-2866 .NET: Automatic JAVA_HOME detecti...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/577 IGNITE-2866 .NET: Automatic JAVA_HOME detection You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-2866 Alternatively yo

IGNITE-1071 IgniteCache.metrics() method returns local metrics

Hello, I'd like to discuss IGNITE-1071 IgniteCache.metrics() method returns local metrics I agree to make IgniteCache.metrics() global but want to keep MBeans local. According to specification: An MBean can represent a device, an application, o

Re: Serialization exception when migrating from 1.3 to 1.5

Please provide us with a full log. From this log snippet it's not clear which part of the code triggered the exception. -- Denis On 3/24/2016 1:03 PM, endianignite wrote: I am attempting to migrate from 1.3.0-incubating to 1.5.0.final. However, when I start my cache I get the following except

Re: Confusing IGNITE_ATOMIC_CACHE_DELETE_HISTORY_SIZE property

Done https://issues.apache.org/jira/browse/IGNITE-2885 On 3/24/2016 11:46 AM, Yakov Zhdanov wrote: To get rid of this completely we need to switch to fair thread-per-partition. Denis, it this queue is used in TX caches to resolve rebalancing and concurrent puts races. We can try removin it once

[jira] [Created] (IGNITE-2885) Avoid usage of GridDhtLocalPartition.rmvQueue for Transactional caches

Denis Magda created IGNITE-2885: --- Summary: Avoid usage of GridDhtLocalPartition.rmvQueue for Transactional caches Key: IGNITE-2885 URL: https://issues.apache.org/jira/browse/IGNITE-2885 Project: Ignite

[jira] [Created] (IGNITE-2884) Any exampe fails if one run after CacheHibernateStoreExample

Sergey Kozlov created IGNITE-2884: - Summary: Any exampe fails if one run after CacheHibernateStoreExample Key: IGNITE-2884 URL: https://issues.apache.org/jira/browse/IGNITE-2884 Project: Ignite

Re: All BinaryObjects created by BinaryObjectBuilder stored at the same partition by default

As for JdbcPojoStore it has an option to configure "hasher". On Thu, Mar 24, 2016 at 5:20 PM, Denis Magda wrote: > +1 for the improvement of JavaDoc because the problem arises only when > BinaryObjects are used as keys. > Readme.io already has a warning regarding this > > https://apacheignite.re

[GitHub] ignite pull request: IGNITE-2873 .NET: Support .NET configuration ...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/576 IGNITE-2873 .NET: Support .NET configuration in Apache.Ignite.exe You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-2873

Serialization exception when migrating from 1.3 to 1.5

I am attempting to migrate from 1.3.0-incubating to 1.5.0.final. However, when I start my cache I get the following exception Exception in thread "main" java.lang.IllegalArgumentException: This method should be accessed under org.apache.ignite.thread.IgniteThread at org.apache.ignite.internal.Ign

[GitHub] ignite pull request: Ignite 2876

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

Re: All BinaryObjects created by BinaryObjectBuilder stored at the same partition by default

+1 for the improvement of JavaDoc because the problem arises only when BinaryObjects are used as keys. Readme.io already has a warning regarding this https://apacheignite.readme.io/docs/binary-marshaller#modifying-binary-objects-using-binaryobjectbuilder -- Denis On 3/24/2016 12:38 PM, Vladimir

[GitHub] ignite pull request: Ignite 2876

GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/575 Ignite 2876 DO NOT MERGE You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-2876 Alternatively you can review and a

Re: All BinaryObjects created by BinaryObjectBuilder stored at the same partition by default

When object has been built, there is no way to know, whether hash code was set or not. Zero could be real hash code, as well as not set hash code. Random is not an option. Any kind of automatic generation is not an option as well, because we do not know, how hash code of real class instance is cal

Re: All BinaryObjects created by BinaryObjectBuilder stored at the same partition by default

Random hash code is not an option. I would suggest cache throws exception on update if binary object created with builder does not have hash code initialized. Vladimir, can we somehow make it possible to know whether hash code was or was not inited on a binary object? --Yakov 2016-03-24 11:43 G

Re: Confusing IGNITE_ATOMIC_CACHE_DELETE_HISTORY_SIZE property

To get rid of this completely we need to switch to fair thread-per-partition. Denis, it this queue is used in TX caches to resolve rebalancing and concurrent puts races. We can try removin it once partition gets loaded, btw. Can you please file a ticket? --Yakov 2016-03-09 23:12 GMT+03:00 Dmitri

All BinaryObjects created by BinaryObjectBuilder stored at the same partition by default

Hello, I found that every BinaryObject created by BinaryObjectBuilder has hashcode == 0 by default. This can cause situation that all objects created by code similar to: *BinaryObject key = builder.setField("id", i).build();* *streamer.addData(key, key);* will be stored at one partition and this

Re: Transactions in atomics

Val, can you please file a newbie ticket for this (if it is not there already)? --Yakov 2016-03-11 9:51 GMT+03:00 Valentin Kulichenko : > Folks, > > I noticed that we use pessimistic transaction to update atomic reference. > Is there any reason for that? Why don't we use atomic cache and invoke(

Re: github replication of Ignite

Thank you, Anton! -Roman On Thursday, March 24, 2016 5:11 PM, Anton Vinogradov wrote: Replication fixed. On Thu, Mar 24, 2016 at 11:04 AM, Anton Vinogradov wrote: > Roman, > > thanks for pointing this, I've created infra issue > > https://issues.apache.org/jira/browse/INFRA-11534 > >

Re: github replication of Ignite

Replication fixed. On Thu, Mar 24, 2016 at 11:04 AM, Anton Vinogradov wrote: > Roman, > > thanks for pointing this, I've created infra issue > > https://issues.apache.org/jira/browse/INFRA-11534 > > On Thu, Mar 24, 2016 at 8:53 AM, Roman Shtykh > wrote: > >> Hi Anton, >> >> I have pushed two ch

[GitHub] ignite pull request: IGNITE-2415: CacheLoadOnlyStoreAdapter use ex...

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

Re: github replication of Ignite

Roman, thanks for pointing this, I've created infra issue https://issues.apache.org/jira/browse/INFRA-11534 On Thu, Mar 24, 2016 at 8:53 AM, Roman Shtykh wrote: > Hi Anton, > > I have pushed two changes to the master this morning and see no > replication to github. Is it normal? > > It seems y

[jira] [Created] (IGNITE-2883) IGFS: IPC handled must use dedicated thread pool.

Vladimir Ozerov created IGNITE-2883: --- Summary: IGFS: IPC handled must use dedicated thread pool. Key: IGNITE-2883 URL: https://issues.apache.org/jira/browse/IGNITE-2883 Project: Ignite Issu