Re: Thin Client Protocol documentation

Andrey, As I understand, you suggest to document every prospective feature right now. That would be (at least) compute, clustering, transactions, services, messages, events, failover, data structures, metrics. I don't think it makes sense to do that. Another problem is that it will take weeks :)

Re: Time and scope for Apache Ignite 2.4

On Tue, Dec 5, 2017 at 7:13 AM, Andrey Gura wrote: > Hi, > > I'm working on WAL optimizations that improve performance > significantly [1]. I believe it's important task and should be > included in Apache Ignite 2.4 release. > > [1]

RE: [jira] [Created] (IGNITE-7083) Reduce memory usage of CachePartitionFullCountersMap

I have created a pull request for my proposed change. https://github.com/apache/ignite/pull/3152 -Original Message- From: Denis Magda [mailto:dma...@apache.org] Sent: Saturday, December 02, 2017 3:10 AM To: dev@ignite.apache.org; Semen Boikov; Alexey Goncharuk Subject: Fwd: [jira]

[GitHub] ignite pull request #3152: Ignite 7083

GitHub user sunnychanwork opened a pull request: https://github.com/apache/ignite/pull/3152 Ignite 7083 The Cache Partition Exchange Manager kept a copy of the already completed exchange. However, we have found that it uses a significant amount of memory. Upon further

[GitHub] ignite pull request #3151: IGNITE-7055: Fix text query to work with a partic...

GitHub user shroman opened a pull request: https://github.com/apache/ignite/pull/3151 IGNITE-7055: Fix text query to work with a particular field. You can merge this pull request into a Git repository by running: $ git pull https://github.com/shroman/ignite IGNITE-7055

[jira] [Created] (IGNITE-7119) Web Agent: Implement support for comma-delimited list of node URIs

Alexey Kuznetsov created IGNITE-7119: Summary: Web Agent: Implement support for comma-delimited list of node URIs Key: IGNITE-7119 URL: https://issues.apache.org/jira/browse/IGNITE-7119 Project:

Apache Ignite talks in Austin, TX

Folks, The nearest couple of days I’m spending in Austin, TX in order to meet with current and believe (!) future Ignite users diving into the following topics: 1. Apache Ignite Machine Learning capabilities: https://www.meetup.com/austindata/events/245472777/

[GitHub] ignite pull request #3150: IGNITE-7015: Indexes are updated only if the inde...

GitHub user dolphin1414 opened a pull request: https://github.com/apache/ignite/pull/3150 IGNITE-7015: Indexes are updated only if the indexed fields are changed. Now if it's possible to update row in-place (without link changing), and indexed columns haven't been changed, no

[GitHub] ignite pull request #3149: [IGNITE-3935] test case implemented

GitHub user corney opened a pull request: https://github.com/apache/ignite/pull/3149 [IGNITE-3935] test case implemented You can merge this pull request into a Git repository by running: $ git pull https://github.com/corney/ignite IGNITE-3935-verification-for-deserialization

Re: Thin Client Protocol documentation

Pavel, I have absolutely no doubts that support for all those features will be added eventually. And if so, wouldn't it be the right thing to do to document the operations and their semantics right now without necessarily implementing them? It should really help to ensure that the protocol can

[jira] [Created] (IGNITE-7118) performance measurement for distributed k-means clustering

Oleg Ignatenko created IGNITE-7118: -- Summary: performance measurement for distributed k-means clustering Key: IGNITE-7118 URL: https://issues.apache.org/jira/browse/IGNITE-7118 Project: Ignite

[GitHub] ignite pull request #3148: Ignite 6846

GitHub user voipp opened a pull request: https://github.com/apache/ignite/pull/3148 Ignite 6846 You can merge this pull request into a Git repository by running: $ git pull https://github.com/voipp/ignite ignite-6846 Alternatively you can review and apply these changes as

[jira] [Created] (IGNITE-7117) .NET: IGNITE_HOME resolver relies on Java examples

Pavel Tupitsyn created IGNITE-7117: -- Summary: .NET: IGNITE_HOME resolver relies on Java examples Key: IGNITE-7117 URL: https://issues.apache.org/jira/browse/IGNITE-7117 Project: Ignite

[GitHub] ignite pull request #3147: Ignite 7050

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

[jira] [Created] (IGNITE-7116) Logging minor issue as error instead of warning or info

Kirill Danilov created IGNITE-7116: -- Summary: Logging minor issue as error instead of warning or info Key: IGNITE-7116 URL: https://issues.apache.org/jira/browse/IGNITE-7116 Project: Ignite

[GitHub] ignite pull request #3146: IGNITE-6867 JMX metrics for topology monitoring -...

GitHub user alex-plekhanov opened a pull request: https://github.com/apache/ignite/pull/3146 IGNITE-6867 JMX metrics for topology monitoring - redesign You can merge this pull request into a Git repository by running: $ git pull https://github.com/alex-plekhanov/ignite

Re: Time and scope for Apache Ignite 2.4

Hi, I'm working on WAL optimizations that improve performance significantly [1]. I believe it's important task and should be included in Apache Ignite 2.4 release. [1] https://issues.apache.org/jira/browse/IGNITE-6339 On Tue, Dec 5, 2017 at 12:11 AM, Denis Magda wrote: >

[jira] [Created] (IGNITE-7115) .NET: Thin client: performance: use buffer pool

Pavel Tupitsyn created IGNITE-7115: -- Summary: .NET: Thin client: performance: use buffer pool Key: IGNITE-7115 URL: https://issues.apache.org/jira/browse/IGNITE-7115 Project: Ignite Issue

Re: Ignite Enhancement Proposal #6 (Metrics)

Why it should not be open? That's just a tool allows to merge something. Since we're not using PR's in github's way - I see no reason to close them. On Tue, Dec 5, 2017 at 4:11 PM, Pavel Tupitsyn wrote: > > Could you please explain profit of doing this? > The point is that

Re: Ignite Enhancement Proposal #6 (Metrics)

> Could you please explain profit of doing this? The point is that pull requests should not be left open. Either close them manually or use that autoclose feature. On Tue, Dec 5, 2017 at 4:02 PM, Anton Vinogradov wrote: > Pavel, > > >> There is corresponding > >>

Re: Ignite Enhancement Proposal #6 (Metrics)

Pavel, >> There is corresponding >> modules\platforms\dotnet\Apache.Ignite.Core\Cluster\IClusterMetrics.cs in >> .NET. Got it. >> PS Looks like you don't close pull requests when merging them to master. >> Please make sure to include "This closes #prnum" in the commit messages, >> as the

[GitHub] ignite pull request #3142: IGNITW-7093 added plugin to build test.jar to ign...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3142 ---

[GitHub] ignite pull request #3145: Test necessity to keep NOOP txEntry for READs.

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/3145 Test necessity to keep NOOP txEntry for READs. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-12885-master

[GitHub] ignite pull request #3144: IGNITE-7112 More informative: Failed to wait PME

GitHub user zstan opened a pull request: https://github.com/apache/ignite/pull/3144 IGNITE-7112 More informative: Failed to wait PME You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7112

[jira] [Created] (IGNITE-7114) C++ node can't start without java examples folder

Evgenii Zhuravlev created IGNITE-7114: - Summary: C++ node can't start without java examples folder Key: IGNITE-7114 URL: https://issues.apache.org/jira/browse/IGNITE-7114 Project: Ignite

[jira] [Created] (IGNITE-7113) "Key is missing from query" when creating table with key_type=java.lang.String

Ilya Kasnacheev created IGNITE-7113: --- Summary: "Key is missing from query" when creating table with key_type=java.lang.String Key: IGNITE-7113 URL: https://issues.apache.org/jira/browse/IGNITE-7113

[GitHub] ignite pull request #3143: IGNITE-7085 When PDS is enabled and IGNITE_BINARY...

GitHub user asfedotov opened a pull request: https://github.com/apache/ignite/pull/3143 IGNITE-7085 When PDS is enabled and IGNITE_BINARY_SORT_OBJECT_FIELDS … …is set and IgniteCache#put is called node hangs You can merge this pull request into a Git repository by running:

Re: Ignite Enhancement Proposal #6 (Metrics)

Anton, https://issues.apache.org/jira/browse/IGNITE-6869 adds new properties to ClusterMetrics. There is corresponding modules\platforms\dotnet\Apache.Ignite.Core\Cluster\IClusterMetrics.cs in .NET. Actually, IGNITE-6869 has a comment from Vladimir about this. Same thing for IGNITE-6870,

[GitHub] ignite pull request #3142: IGNITW-7093 added plugin to build test.jar to ign...

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/3142 IGNITW-7093 added plugin to build test.jar to ignite-compatibility po… …m.xml You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-7112) Non informative "Failed to wait for partition map exchange" message.

Stanilovsky Evgeny created IGNITE-7112: -- Summary: Non informative "Failed to wait for partition map exchange" message. Key: IGNITE-7112 URL: https://issues.apache.org/jira/browse/IGNITE-7112

[jira] [Created] (IGNITE-7111) NPE in ignite.dataRegionMetrics() on INACTIVE cluster

Alexey Kuznetsov created IGNITE-7111: Summary: NPE in ignite.dataRegionMetrics() on INACTIVE cluster Key: IGNITE-7111 URL: https://issues.apache.org/jira/browse/IGNITE-7111 Project: Ignite

[GitHub] ignite pull request #3141: IGNITE-7095: close & cleanup internal H2 JDBC Con...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/3141 IGNITE-7095: close & cleanup internal H2 JDBC Connection You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: Ignite Enhancement Proposal #6 (Metrics)

Pavel, These changes mostly about JMX Beans. Could you please explain what should be added to .Net? Provide some examples please. On Tue, Dec 5, 2017 at 10:40 AM, Pavel Tupitsyn wrote: > Hi Anton, > > Looks like none of the new metrics are added on .NET side. > Please

[GitHub] ignite pull request #3140: IGNITE-7017: Archiver disabled WAL mode in case f...

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/3140 IGNITE-7017: Archiver disabled WAL mode in case folders are equal You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: Thin Client Protocol documentation

Andrey, All of this is to come :) Prachi, 1) There are no flags, see the doc 2) String is simply 4 byte length (n) + n bytes 3) Op codes have changed writeByteLittleEndian(1051, out); // Type code writeIntLittleEndian(20, out); // String length out.writeUTF("myNewCache"); // Cache name On

[GitHub] ignite pull request #3119: IGNITE-7002 .NET: Add cross-platform examples on ...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3119 ---