Re: ignite-4823 - ready for review (SpringCache#putIfAbsent - wrong implementation)

Hi Vyacheslav, I reviewed and merged you changes to master. Thanks for the contribution! -Val On Fri, Mar 17, 2017 at 12:06 AM, Vyacheslav Daradur wrote: > Valentin, ok, thank you. > > 2017-03-16 18:39 GMT+03:00 Valentin Kulichenko < > valentin.kuliche...@gmail.com>: > > > Vyacheslav, > > > >

[GitHub] ignite pull request #1624: IGNITE-4823

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

Re: IGNITE-2766 Spring Cache Manager ReConnect Issue

Hi Rishi, I looked at your changes and added a comment in the ticket. -Val On Wed, Mar 29, 2017 at 10:04 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Hi Rishi, > > I will review in next couple of days. > > -Val > > On Tue, Mar 28, 2017 at 8:24 PM, Rishi Yagnik > wrote: > >

[jira] [Created] (IGNITE-4903) More SQL side tests for CREATE/DROP INDEX

Alexander Paschenko created IGNITE-4903: --- Summary: More SQL side tests for CREATE/DROP INDEX Key: IGNITE-4903 URL: https://issues.apache.org/jira/browse/IGNITE-4903 Project: Ignite Issu

Re: one point optimisation

Here is a good blog post about 1phase commit impl in Ignite and its advantages: http://gridgain.blogspot.com/2014/09/one-phase-commit-fast-transactions-for.html Took a reference to it from there: https://apacheign

[GitHub] ignite pull request #1719: https://issues.apache.org/jira/browse/IGNITE-4890

GitHub user venky1963 opened a pull request: https://github.com/apache/ignite/pull/1719 https://issues.apache.org/jira/browse/IGNITE-4890 Support older versions of Cassandra where the table not exists message comes out as 'unconfigured columnfamily' instead of the newer 'unco

Re: IGNITE-4878 ready for review

Replied in "Distribution of keys to partitions” discussion. — Denis > On Mar 31, 2017, at 3:21 AM, michael.griggs > wrote: > > https://issues.apache.org/jira/browse/IGNITE-4878 > > https://github.com/apache/ignite/pull/1692 > > > > -- > View this message in context: > http://apache-ignite

Re: IGNITE-4188, thoughts about realisation

Sam, Yakov, Alex G., Could you chime in and discuss implementation details with Dmitriy S. to make sure he is not moving in a wrong direction? — Denis > On Mar 31, 2017, at 9:34 AM, Дмитрий Рябов wrote: > > Hello, community. > > try (Transaction tx = ignite.transactions().txStart()) { >

Re: IGNITE-4052 ready for review - what can I improve

Sure! On Fri, Mar 31, 2017 at 8:13 PM, Denis Magda wrote: > Nick, Vadim, > > Please don’t forget to update Mesos doc once this contribution gets merged: > https://apacheignite.readme.io/docs/mesos-deployment > > — > Denis > > On Mar 31, 2017, at 4:07 AM, Вадим Опольский wrote: > > Hello communi

Re: IGNITE-4052 ready for review - what can I improve

Nick, Vadim, Please don’t forget to update Mesos doc once this contribution gets merged: https://apacheignite.readme.io/docs/mesos-deployment — Denis > On Mar 31, 2017, at 4:07 AM, Вадим Опольский wrote: > > Hello community! > > I want t

Re: Distribution of keys to partitions

Michael, thanks. I did minor improvements and merged them to IGNITE-4828 branch and triggered TeamCity tests: http://ci.ignite.apache.org/viewQueued.html?itemId=526101&tab=queuedBuildOverviewTab *Michael*, please check the tests results lately. I won’t be available in the nearest 4 days. *Ilya

Re: Distribution of keys to partitions

Vova, Not sure I understand what you mean. I believe that we just agreed that if the partition count is set to the power of 2, then we can improve the performance with a better hashing algorithm. D. On Fri, Mar 31, 2017 at 1:46 AM, Vladimir Ozerov wrote: > In order to overcome this problem, Ha

Re: one point optimisation

On Fri, Mar 31, 2017 at 9:25 AM, ALEKSEY KUZNETSOV wrote: > Igniters! What is the point of one phase optimisation? > Performance

Re: NearCache transaction qeustion

On Fri, Mar 31, 2017 at 6:29 AM, ALEKSEY KUZNETSOV wrote: > Hi all! > Consider we have 4 nodes. Node1 contains key1, Node2 contains key1 backup, > and Node3 near-contains (contains in near cache) key1. > Now we commit key1 value change like the following : Node4Cache.put(key1, > updatedValue); >

one point optimisation

Igniters! What is the point of one phase optimisation? -- *Best Regards,* *Kuznetsov Aleksey*

Fwd: Getting Started with Apache Ignite - Part 1

Posted the blog on DZone today; It should get published by Monday/Tuesday. -P -- Forwarded message -- From: Denis Magda Date: Tue, Mar 28, 2017 at 4:22 PM Subject: Re: Getting Started with Apache Ignite - Part 1 To: dev@ignite.apache.org Dani, excellent job! *Prachi*, could yo

[jira] [Created] (IGNITE-4902) .NET: StartFromApplicationConfiguration does not work in ASP.NET

Pavel Tupitsyn created IGNITE-4902: -- Summary: .NET: StartFromApplicationConfiguration does not work in ASP.NET Key: IGNITE-4902 URL: https://issues.apache.org/jira/browse/IGNITE-4902 Project: Ignite

[jira] [Created] (IGNITE-4901) Decrease logging level for DataStremer retry

Nikolay Tikhonov created IGNITE-4901: Summary: Decrease logging level for DataStremer retry Key: IGNITE-4901 URL: https://issues.apache.org/jira/browse/IGNITE-4901 Project: Ignite Issue

[GitHub] ignite pull request #1718: IGNITE-4699 Introduce custom configurable executo...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/1718 IGNITE-4699 Introduce custom configurable executors. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-469

Re: IGNITE-1948 ClusterTopologyCheckedException can return null for retryReadyFuture()

Alexey, I just remind you about issue. 2017-02-20 16:42 GMT+03:00 Александр Меньшиков : > Alexey, > > I'm ready to make some conclusions. You can see result immediately here: > PR: https://github.com/apache/ignite/pull/1537/files > CI Tests: http://ci.ignite.apache.org/project.html?proj

[jira] [Created] (IGNITE-4900) org.apache.ignite.spi.discovery.tcp.TcpDiscoverySelfTest#testFailedNodes4 periodically fails in master

Yakov Zhdanov created IGNITE-4900: - Summary: org.apache.ignite.spi.discovery.tcp.TcpDiscoverySelfTest#testFailedNodes4 periodically fails in master Key: IGNITE-4900 URL: https://issues.apache.org/jira/browse/IGNI

Re: ignite-4884 - ready for review (Visorcmd - minor text mistake)

Merged to master. Thanks, for your contribution. On Thu, Mar 30, 2017 at 6:29 PM, Vyacheslav Daradur wrote: > Hello everyone. > > Looks like minor mistake. > > Please review if someone has time. > > -- > Best Regards, Vyacheslav > -- Alexey Kuznetsov

[GitHub] ignite pull request #1698: IGNITE-4884

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

[jira] [Created] (IGNITE-4899) .NET: Review Dictionary usage in APIs

Pavel Tupitsyn created IGNITE-4899: -- Summary: .NET: Review Dictionary usage in APIs Key: IGNITE-4899 URL: https://issues.apache.org/jira/browse/IGNITE-4899 Project: Ignite Issue Type: Improv

IGNITE-4188, thoughts about realisation

Hello, community. try (Transaction tx = ignite.transactions().txStart()) { c.put(1, 1); tx.savepoint("mysavepoint"); c.put(2, 2); tx.rollbackToSavepoint("mysavepoint"); c.put(3, 3); tx.commit(); } I want to make it in such way: When user calls tx.savepoint(""), Tran

[GitHub] ignite pull request #1664: IGNITE-2703 .NET: Dynamic type registration

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

NearCache transaction qeustion

Hi all! Consider we have 4 nodes. Node1 contains key1, Node2 contains key1 backup, and Node3 near-contains (contains in near cache) key1. Now we commit key1 value change like the following : Node4Cache.put(key1, updatedValue); >From my point of view Node1 receives prepare request and send DhtTxPre

[GitHub] ignite pull request #1717: IGNITE-4524: Index direct lookup for SQL function...

GitHub user skalashnikov opened a pull request: https://github.com/apache/ignite/pull/1717 IGNITE-4524: Index direct lookup for SQL functions MIN() and MAX() You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #1716: IGNITE-4625 .NET: MixedClusterTest leaves Java-on...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/1716 IGNITE-4625 .NET: MixedClusterTest leaves Java-only node running You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-4625

[GitHub] ignite pull request #1715: Ignite 4891 Fix. Key is deserialized during trans...

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/1715 Ignite 4891 Fix. Key is deserialized during transactional get() even if withKeepBinary is set You can merge this pull request into a Git repository by running: $ git pull https://githu

[GitHub] ignite pull request #1714: Sync with upstream master

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

[GitHub] ignite pull request #1714: Sync with upstream master

GitHub user rmohta opened a pull request: https://github.com/apache/ignite/pull/1714 Sync with upstream master Sync with upstream master You can merge this pull request into a Git repository by running: $ git pull https://github.com/rmohta/ignite master Alternatively you can r

[GitHub] ignite pull request #1713: IGNITE-3585 CPP: Container-based methods now acce...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/1713 IGNITE-3585 CPP: Container-based methods now accept iterators. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-35

[jira] [Created] (IGNITE-4898) Add path to ODBC driver installers to platforms\cpp\odbc\README.txt

Irina Zaporozhtseva created IGNITE-4898: --- Summary: Add path to ODBC driver installers to platforms\cpp\odbc\README.txt Key: IGNITE-4898 URL: https://issues.apache.org/jira/browse/IGNITE-4898 Pro

[GitHub] ignite pull request #1712: ignite-4847 : implemented

GitHub user endian675 opened a pull request: https://github.com/apache/ignite/pull/1712 ignite-4847 : implemented You can merge this pull request into a Git repository by running: $ git pull https://github.com/endian675/ignite ignite-4847-4 Alternatively you can review and ap

[GitHub] ignite pull request #1695: IGNITE-3506 .NET: Fix ContinuousQuery, QueryBase,...

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

[GitHub] ignite pull request #1711: Ignite 4896

Github user akuznetsov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/1711 --- 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 f

[GitHub] ignite pull request #1711: Ignite 4896

GitHub user akuznetsov-gridgain opened a pull request: https://github.com/apache/ignite/pull/1711 Ignite 4896 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4896 Alternatively you can review and ap

[GitHub] ignite pull request #1710: Ignite 4477 Fix IgniteFuture.listen() and IgniteF...

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/1710 Ignite 4477 Fix IgniteFuture.listen() and IgniteFuture.chain() semantics You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-

[jira] [Created] (IGNITE-4897) Web console: Do not escape optional symbols in XML

Vasiliy Sisko created IGNITE-4897: - Summary: Web console: Do not escape optional symbols in XML Key: IGNITE-4897 URL: https://issues.apache.org/jira/browse/IGNITE-4897 Project: Ignite Issue T

[jira] [Created] (IGNITE-4896) OptimizedMarshaller should not failed on GridClientNodeBean serialization

Alexey Kuznetsov created IGNITE-4896: Summary: OptimizedMarshaller should not failed on GridClientNodeBean serialization Key: IGNITE-4896 URL: https://issues.apache.org/jira/browse/IGNITE-4896 Pro

TC should fail on AssertionError in logs

Guys, I see couple of tests which have assertion error in some background Ignite threads that may not cause test to fail. https://issues.apache.org/jira/browse/IGNITE-4895 Anton V, can you please take a look? --Yakov

[jira] [Created] (IGNITE-4895) TC should fail suite if AssertionError is output to logs

Yakov Zhdanov created IGNITE-4895: - Summary: TC should fail suite if AssertionError is output to logs Key: IGNITE-4895 URL: https://issues.apache.org/jira/browse/IGNITE-4895 Project: Ignite I

Re: ignite-3592 is ready fo review (Provide some kind of pluggable compression SPI support)

Hello everyone. I have prepared the raw evaluation (marshaller layer) of compression. (GZIP implementation) https://github.com/daradurvs/ignite-compression/tree/master/src/main/resources/result In plans for evaluation: 1. Deflater compressor implementation; 2. Snappy compressor implementation; 3.

Re: Distribution of keys to partitions

In order to overcome this problem, Hazelcast guys set non-power-of-two partition count by default - 257. On Fri, Mar 31, 2017 at 9:59 AM, michael.griggs wrote: > The change is now ready for review: > > https://github.com/apache/ignite/pull/1707 > > > > -- > View this message in context: http://a

[GitHub] ignite pull request #1607: IGNITE-4803

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

[GitHub] ignite pull request #1703: IGNITE-4888

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

[GitHub] ignite pull request #1597: IGNITE-4779 Missed discovery data snapshot during...

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

[GitHub] ignite pull request #1709: IGNITE-2313

GitHub user SomeFire opened a pull request: https://github.com/apache/ignite/pull/1709 IGNITE-2313 You can merge this pull request into a Git repository by running: $ git pull https://github.com/SomeFire/ignite ignite-2313 Alternatively you can review and apply these changes

IGNITE-4052 ready for review - what can I improve

Hello community! I want to add ability to connect to MESOS cluster via user name and role from system env properties and to add JUnit test. Review please pull request, what can I improve ? How correctly to test methods work? https://github.com/apache/ignite/pull/1662 Vadim Opolski 2017-03-30

Re: distributed transaction of non-single coordinator

sorry for misleading you. We planned to support multi-node transactions, but failed. пт, 31 мар. 2017 г. в 10:51, Alexey Goncharuk : > Well, now the scenario is more clear, but it has nothing to do with > multiple coordinators :) Let me think a little bit about it. > > 2017-03-31 9:53 GMT+03:00 A

Re: Apache Ignite 2.0 Release

Another big merge - now almost all our setters on public configuration return "this" instance to allow for convenient chaining [1]. Big thanks to *Andrew Mashenkov* for making this happen. Ideally I would also try to replace "set(Collection)" with " set(Something...)". This should make configuratio

[GitHub] ignite pull request #1449: IGNITE-4564: Ensure that builder approach is used...

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

Re: distributed transaction of non-single coordinator

Well, now the scenario is more clear, but it has nothing to do with multiple coordinators :) Let me think a little bit about it. 2017-03-31 9:53 GMT+03:00 ALEKSEY KUZNETSOV : > so what do u think on the issue ? > > чт, 30 Мар 2017 г., 17:49 ALEKSEY KUZNETSOV : > > > Hi ! Thanks for help. I've cre

[GitHub] ignite pull request #1696: IGNITE-4847 integrate log4j2 2.8.1

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

[GitHub] ignite pull request #1708: Ignite-4847 integrate log4j2 version 2.8.1

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

[GitHub] ignite pull request #1708: Ignite-4847 integrate log4j2 version 2.8.1

GitHub user endian675 opened a pull request: https://github.com/apache/ignite/pull/1708 Ignite-4847 integrate log4j2 version 2.8.1 You can merge this pull request into a Git repository by running: $ git pull https://github.com/endian675/ignite ignite-4847-2 Alternatively you

IGNITE-4878 ready for review

https://issues.apache.org/jira/browse/IGNITE-4878 https://github.com/apache/ignite/pull/1692 -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/IGNITE-4878-ready-for-review-tp16007.html Sent from the Apache Ignite Developers mailing list archive at Nabble.co

[jira] [Created] (IGNITE-4894) Yardstick-Cassandra

Oleg Ostanin created IGNITE-4894: Summary: Yardstick-Cassandra Key: IGNITE-4894 URL: https://issues.apache.org/jira/browse/IGNITE-4894 Project: Ignite Issue Type: New Feature Repo

Re: Distribution of keys to partitions

The change is now ready for review: https://github.com/apache/ignite/pull/1707 -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Distribution-of-keys-to-partitions-tp15455p16005.html Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

[GitHub] ignite pull request #1707: Ignite-4828

GitHub user endian675 opened a pull request: https://github.com/apache/ignite/pull/1707 Ignite-4828 Improve the distribution of keys within partitions You can merge this pull request into a Git repository by running: $ git pull https://github.com/endian675/ignite IGNITE-4828 A