[GitHub] ignite pull request #3154: IGNITE-369 Runtime statistics enable

Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/3154 ---

[GitHub] ignite pull request #3729: IGNITE-8069 IgniteOutOfMemoryException should be ...

Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/3729 ---

[GitHub] ignite pull request #3749: IGNITE-6892 OOM should be covered by failure hand...

Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/3749 ---

[GitHub] ignite pull request #3474: IGNITE-5265 Eviction Rate memory metric

Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/3474 ---

[GitHub] ignite pull request #3369: IGNITE-6923 Cache metrics optimization

Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/3369 ---

[GitHub] ignite pull request #3630: IGNITE-7831 Throw Exceptions instead of Assertion...

Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/3630 ---

[GitHub] ignite pull request #3195: JMX metrics implementation

Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/3195 ---

[GitHub] ignite pull request #3349: IGNITE-7346: Enable Ignite cache events per cache

Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/3349 ---

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

Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/3146 ---

[GitHub] ignite pull request #3139: IGNITE-6871 Group name added to group metrics MXB...

Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/3139 ---

[GitHub] ignite pull request #3123: IGNITE-6868 nodeId type fixed, unused methods rem...

Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/3123 ---

[GitHub] ignite pull request #3051: IGNITE-6870 Added new JMX metric for cache topolo...

Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/3051 ---

[GitHub] ignite pull request #3099: IGNITE-6871 Implement new JMX metrics for partiti...

Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/3099 ---

[GitHub] ignite pull request #3034: IGNITE-6868 Added new JMX metrics for TcpCommunic...

Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/3034 ---

[GitHub] ignite pull request #3053: IGNITE-6869 Added new JMX metric: Total jobs exec...

Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/3053 ---

[GitHub] ignite pull request #3080: IGNITE-6985 Wrong value of RebalancingStartTime c...

Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/3080 ---

[jira] [Created] (IGNITE-8287) Web console: place sign up inputs in two columns

Ilya Borisov created IGNITE-8287: Summary: Web console: place sign up inputs in two columns Key: IGNITE-8287 URL: https://issues.apache.org/jira/browse/IGNITE-8287 Project: Ignite Issue

[GitHub] ignite pull request #3836: IGNITE-8201 Refactor REST API for authentication.

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

[jira] [Created] (IGNITE-8286) ScanQuery ignore setLocal with non local partition

Alexander Belyak created IGNITE-8286: Summary: ScanQuery ignore setLocal with non local partition Key: IGNITE-8286 URL: https://issues.apache.org/jira/browse/IGNITE-8286 Project: Ignite

Re: Service grid redesign

I agree we shouldn't do anything synchronously within discovery threads. If something goes wrong, we just need to properly notify the user, logging and events seem to be right options to achieve that. BTW, with this design I'm not sure init() method makes sense, probably we should deprecate it.

[GitHub] ignite pull request #3836: IGNITE-8201 Refactor REST API for authentication.

GitHub user nva opened a pull request: https://github.com/apache/ignite/pull/3836 IGNITE-8201 Refactor REST API for authentication. You can merge this pull request into a Git repository by running: $ git pull https://github.com/apache/ignite ignite-8201 Alternatively you can

[jira] [Created] (IGNITE-8285) Web console: debug log not removed

Ilya Borisov created IGNITE-8285: Summary: Web console: debug log not removed Key: IGNITE-8285 URL: https://issues.apache.org/jira/browse/IGNITE-8285 Project: Ignite Issue Type: Bug

Re: affinityRun/Call in C++

Hi Guys, Having (very unfortunately) done a boatload of C++ programming while I was at university, there are some issues to consider here. One of the biggest is compiler name mangling . Now, I’m guessing

Proposal

Hello Greeetings to you please did you get my previous email regarding my investment proposal last week friday ? MS.Zeliha ömer faruk zeliha.omer.fa...@gmail.com

Re: Service grid redesign

Denis, In general, service initialization shouldn't prevent a node from joining the cluster or slowing down that process. Thus, I would start the initialization routines only after the node is accepted by the cluster. If the initialization fails then we need to report a respective message to the

Re: [jira] [Created] (IGNITE-8279) Clients can't operate on services after deactivation

Hi Denis, Would this be better to target 2.5? It seems like a significant regression... Thanks, Raymond. Sent from my iPhone > On 17/04/2018, at 1:46 AM, Denis Mekhanikov (JIRA) wrote: > > Denis Mekhanikov created IGNITE-8279: > > >

[GitHub] ignite pull request #3810: IGNITE-7972: Fixed NPE in TTL manager on unwindEv...

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

[GitHub] ignite pull request #3813: IGNITE-8242: Remove method GAGridUtils.getGenesFo...

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

Re: Service grid redesign

Basically, my question is: at which moment services should be deployed on connecting nodes? Should we reject a node from being included into a topology, if services, that are assigned to it, fail to deploy? It would be good to be sure, that all assigned services are initialised and working, when

[GitHub] ignite pull request #3817: IGNITE-8169: Adopt KMeans and remove FuzzyCMeans

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

[GitHub] ignite pull request #3835: IGNITE-7786 Add ping timeout and ping interval to...

GitHub user ivandasch opened a pull request: https://github.com/apache/ignite/pull/3835 IGNITE-7786 Add ping timeout and ping interval to control.sh. Also, make default values greater. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-8284) Performance SQL with distinct in subquery

Pavel Vinokurov created IGNITE-8284: --- Summary: Performance SQL with distinct in subquery Key: IGNITE-8284 URL: https://issues.apache.org/jira/browse/IGNITE-8284 Project: Ignite Issue Type:

[GitHub] ignite pull request #3816: IGNITE-8246: update print errors

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

Re: affinityRun/Call in C++

It depends on which functionality is needed, as there are several versions of those methods. Some would require implementing of Cluster API, which is not present in C++ also. Best Regards, Igor On Mon, Apr 16, 2018 at 6:41 PM, Denis Magda wrote: > Do we target it for 2.6

[jira] [Created] (IGNITE-8283) CPP: Implement 'varint' solution to be configurable via BinaryConfiguration

Vyacheslav Daradur created IGNITE-8283: -- Summary: CPP: Implement 'varint' solution to be configurable via BinaryConfiguration Key: IGNITE-8283 URL: https://issues.apache.org/jira/browse/IGNITE-8283

Re: Mass TC Run-All during this weekend

I wish this report have just 30 or 10 failures, so it would be very easy to analyse these failures. I'll think how to present some statistic or summary of all these fails. пн, 16 апр. 2018 г. в 18:40, Denis Magda : > Hi Dmitriy, > > Though it's difficult to analyze the

[GitHub] ignite pull request #3831: IGNITE-8280: fix NPE

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

Re: IGNITE-6879

Denis, module naming fixed пн, 16 апр. 2018 г. в 19:24, Denis Magda : > Roman, > > In my last reply, I voted for your approach - using "spring-data*_*2.0" for > the new Spring version. However, please note that we use "_" symbol instead > of "-" to separate a version from the

Re: affinityRun/Call in C++

Do we target it for 2.6 release? It shouldn't be time-consuming to support it, right? -- Denis On Mon, Apr 16, 2018 at 2:48 AM, Igor Sapego wrote: > Guys, > > I've created a ticket: [1] > > [1] - https://issues.apache.org/jira/browse/IGNITE-8273 > > Best Regards, > Igor > >

Re: Mass TC Run-All during this weekend

Hi Dmitriy, Though it's difficult to analyze the report, I guess the things are moving in a right direction. Probably, there is a clearer format you can come up with. Thanks for keep driving it. -- Denis On Mon, Apr 16, 2018 at 3:04 AM, Dmitry Pavlov wrote: > Hi

[GitHub] ignite pull request #3834: IGNITE-7640 done

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

Re: IGNITE-6879

Roman, In my last reply, I voted for your approach - using "spring-data*_*2.0" for the new Spring version. However, please note that we use "_" symbol instead of "-" to separate a version from the package name. -- Denis On Sun, Apr 15, 2018 at 8:17 AM, Роман Меерсон

[GitHub] ignite pull request #3833: IGNITE-8282 Direct IO: support fdatasync, which d...

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/3833 IGNITE-8282 Direct IO: support fdatasync, which does not flush meta You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #3832: IGNITE-8282 Direct IO: support fdatasync, which d...

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

[GitHub] ignite pull request #3832: IGNITE-8282 Direct IO: support fdatasync, which d...

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/3832 IGNITE-8282 Direct IO: support fdatasync, which does not flush modified metadata You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #3831: IGNITE-8280: fix NPE

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/3831 IGNITE-8280: fix NPE You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8280 Alternatively you can review

[GitHub] ignite pull request #3243: IGNITE-7182: Checkpoint pages: optimize and paral...

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

[GitHub] ignite pull request #3830: IGNITE-7182 Supported striped dirty page storage ...

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/3830 IGNITE-7182 Supported striped dirty page storage in skip list maps And quick sort with early cp pages write start You can merge this pull request into a Git repository by running: $ git

[jira] [Created] (IGNITE-8282) Direct IO: support fdatasync, which does not flush modified metadata

Dmitriy Pavlov created IGNITE-8282: -- Summary: Direct IO: support fdatasync, which does not flush modified metadata Key: IGNITE-8282 URL: https://issues.apache.org/jira/browse/IGNITE-8282 Project:

[jira] [Created] (IGNITE-8281) Add Docker image build for Apache Ignite Release

Peter Ivanov created IGNITE-8281: Summary: Add Docker image build for Apache Ignite Release Key: IGNITE-8281 URL: https://issues.apache.org/jira/browse/IGNITE-8281 Project: Ignite Issue

[jira] [Created] (IGNITE-8280) NPE on some cases at the QueryEntity.getDecimalInfo

Taras Ledkov created IGNITE-8280: Summary: NPE on some cases at the QueryEntity.getDecimalInfo Key: IGNITE-8280 URL: https://issues.apache.org/jira/browse/IGNITE-8280 Project: Ignite Issue

[GitHub] ignite pull request #3829: IGNITE-6075 'CacheLoadingConcurrentGridStartSelfT...

GitHub user 1vanan opened a pull request: https://github.com/apache/ignite/pull/3829 IGNITE-6075 'CacheLoadingConcurrentGridStartSelfTest sometimes fails' You can merge this pull request into a Git repository by running: $ git pull https://github.com/1vanan/ignite IGNITE-6075

[jira] [Created] (IGNITE-8279) Clients can't operate on services after deactivation

Denis Mekhanikov created IGNITE-8279: Summary: Clients can't operate on services after deactivation Key: IGNITE-8279 URL: https://issues.apache.org/jira/browse/IGNITE-8279 Project: Ignite

[GitHub] ignite pull request #3828: Ignite 8154

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

[GitHub] ignite pull request #3827: IGNITE-8276 : Removed incorrect assertion, fixed ...

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/3827 IGNITE-8276 : Removed incorrect assertion, fixed check for forceKeysRequest. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #3826: IGNITE-8203 Correctly handles ClosedByInterrupt e...

GitHub user ivandasch opened a pull request: https://github.com/apache/ignite/pull/3826 IGNITE-8203 Correctly handles ClosedByInterrupt exception while partition initializes. You can merge this pull request into a Git repository by running: $ git pull

Re: IEP-18: Transparent Data Encryption

Hello, Vladimir. > community is not aware of concrete architecture and proposed public API Concrete architecture is described in IEP-18 [1]. Please, tell me, what else you want to be written. I think answers to all questions have to be addressed(and discussed with community!) when we crack

[jira] [Created] (IGNITE-8278) Nightly built package does not run

Max Shonichev created IGNITE-8278: - Summary: Nightly built package does not run Key: IGNITE-8278 URL: https://issues.apache.org/jira/browse/IGNITE-8278 Project: Ignite Issue Type: Bug

RE: Efficiently determining if cache keys belong to the local server node

// Bcc’ing off dev@ignite list for now as it seems to be rather a user-space discussion. Hi, Let me take a step back first. It seems a bit like an XY problem (https://meta.stackexchange.com/questions/66377/what-is-the-xy-problem), so I’d like to clarify the goals before diving into your

[GitHub] ignite pull request #3825: IGNITE-8274 Changed invoking java in sqlline.sh

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/3825 IGNITE-8274 Changed invoking java in sqlline.sh You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8274

[jira] [Created] (IGNITE-8277) Add utilities to check and display cache info

Alexey Goncharuk created IGNITE-8277: Summary: Add utilities to check and display cache info Key: IGNITE-8277 URL: https://issues.apache.org/jira/browse/IGNITE-8277 Project: Ignite Issue

[jira] [Created] (IGNITE-8276) Cache 2 frequent suite timeout is master

Dmitriy Pavlov created IGNITE-8276: -- Summary: Cache 2 frequent suite timeout is master Key: IGNITE-8276 URL: https://issues.apache.org/jira/browse/IGNITE-8276 Project: Ignite Issue Type:

Re: IEP-18: Transparent Data Encryption

Hi Nikolay, I noticed that some tickets have been created for this feature. Hopefully, you haven't started implementation yet, because at this point community is not aware of concrete architecture and proposed public API. We need to continue discussion and come up with detailed design. Of most

Re: Mass TC Run-All during this weekend

Hi Igniters, New mass run results from this weekend: tests 309 suites 24 It does not mean 97 tests were fixed (it can be muted, not reproduced during these 30 runs, fixied, etc), but result is relatively positive. Full report can be found in MTCGA wiki attachments:

[jira] [Created] (IGNITE-8275) PDS (Compatibility): FoldersReuseCompatibilityTest

Peter Ivanov created IGNITE-8275: Summary: PDS (Compatibility): FoldersReuseCompatibilityTest Key: IGNITE-8275 URL: https://issues.apache.org/jira/browse/IGNITE-8275 Project: Ignite Issue

[jira] [Created] (IGNITE-8274) Wrong invoking of java in sqlline.sh

Pavel Konstantinov created IGNITE-8274: -- Summary: Wrong invoking of java in sqlline.sh Key: IGNITE-8274 URL: https://issues.apache.org/jira/browse/IGNITE-8274 Project: Ignite Issue

[jira] [Created] (IGNITE-8273) CPP: Implement AffinityRun and AffinityCall Compute methods

Igor Sapego created IGNITE-8273: --- Summary: CPP: Implement AffinityRun and AffinityCall Compute methods Key: IGNITE-8273 URL: https://issues.apache.org/jira/browse/IGNITE-8273 Project: Ignite

Re: affinityRun/Call in C++

Guys, I've created a ticket: [1] [1] - https://issues.apache.org/jira/browse/IGNITE-8273 Best Regards, Igor On Wed, Apr 11, 2018 at 2:44 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Is there a ticket? Let's create one if not. > > -Val > > On Tue, Apr 10, 2018 at 6:17 AM,

[GitHub] ignite pull request #3824: IGNITE-7778 User's authentication data must be pe...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/3824 IGNITE-7778 User's authentication data must be persisted on cluster with disabled persistence You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #3822: IGNITE-8097 Java thin client: throw handshake exc...

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

Re: Apache Ignite nightly release builds

Hi, Igniters! I’m glad to inform that starting today Apache Ignite Nightly Builds provide Nuget and Maven stagings at MyGet [1]. Instructions on connecting to these feeds are here: — Nuget [2] — Maven [3] Enjoy. [1] https://www.myget.org/gallery/apache-ignite-nightly

[GitHub] ignite pull request #3795: IGNITE-8129: fix test: setup default SSL context ...

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

[jira] [Created] (IGNITE-8272) Add documentation for normalization preprocessor (release 2.5)

Anton Dmitriev created IGNITE-8272: -- Summary: Add documentation for normalization preprocessor (release 2.5) Key: IGNITE-8272 URL: https://issues.apache.org/jira/browse/IGNITE-8272 Project: Ignite

[jira] [Created] (IGNITE-8271) Add documentation for partition based dataset (release 2.5)

Anton Dmitriev created IGNITE-8271: -- Summary: Add documentation for partition based dataset (release 2.5) Key: IGNITE-8271 URL: https://issues.apache.org/jira/browse/IGNITE-8271 Project: Ignite

[jira] [Created] (IGNITE-8270) Add documentation for MLP (release 2.5)

Anton Dmitriev created IGNITE-8270: -- Summary: Add documentation for MLP (release 2.5) Key: IGNITE-8270 URL: https://issues.apache.org/jira/browse/IGNITE-8270 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-8269) Add documentation to decision tree (release 2.5)

Anton Dmitriev created IGNITE-8269: -- Summary: Add documentation to decision tree (release 2.5) Key: IGNITE-8269 URL: https://issues.apache.org/jira/browse/IGNITE-8269 Project: Ignite Issue

[jira] [Created] (IGNITE-8268) Add documentation for linear regression (release 2.5)

Anton Dmitriev created IGNITE-8268: -- Summary: Add documentation for linear regression (release 2.5) Key: IGNITE-8268 URL: https://issues.apache.org/jira/browse/IGNITE-8268 Project: Ignite

Re: Apache Ignite RPM packaging (Stage II)

> On 15 Apr 2018, at 10:19, Ilya Kasnacheev wrote: > > Hello! > > With existing binary archive, user can move directories from > apache-ignite-fabric/libs/optional to apache-ignite-fabric/libs to activate > them. > > But with RPM, user should not contemplate moving