Re: Annoying extra steps for enabling metrics

Due to holidays I can start work on this ticket only after 8 jan 2018 2017-12-30 2:12 GMT+03:00 Denis Magda : > Good, closed the original ticket. > > Alex P, do you have time to work on IGNITE-7346 instead to address the > issue with the cache events per cache in 2.4 release?

Re: Spark data frames integration merged

Thank you, guys. Val, thanks for all reviews, advices and patience. Anton, thanks for ignite wisdom you share with me. Looking forward for next issues :) P.S Happy New Year for all Ignite community! В Пт, 29/12/2017 в 13:22 -0800, Valentin Kulichenko пишет: > Igniters, > > Great news! We

[GitHub] ignite pull request #3135: IGNITE-6903: Indexes size metric implemented.

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

Re: Annoying extra steps for enabling metrics

Good, closed the original ticket. Alex P, do you have time to work on IGNITE-7346 instead to address the issue with the cache events per cache in 2.4 release? — Denis > On Dec 29, 2017, at 3:10 PM, Valentin Kulichenko > wrote: > > Agree. > > -Val > > On

Re: Annoying extra steps for enabling metrics

Agree. -Val On Fri, Dec 29, 2017 at 3:08 PM, Denis Magda wrote: > Now I see. Seems I was doing something wrong in my initial reproducer. > > Updated cache metrics readme doc by purging any events related parameters > from there: >

Re: Annoying extra steps for enabling metrics

Now I see. Seems I was doing something wrong in my initial reproducer. Updated cache metrics readme doc by purging any events related parameters from there: https://apacheignite.readme.io/v2.3/docs/cache-metrics The events readme doc

[jira] [Created] (IGNITE-7346) Enable Ignite cache events per cache

Denis Magda created IGNITE-7346: --- Summary: Enable Ignite cache events per cache Key: IGNITE-7346 URL: https://issues.apache.org/jira/browse/IGNITE-7346 Project: Ignite Issue Type: Improvement

Re: Annoying extra steps for enabling metrics

Valentine, yes, that's exactly what I'm trying to say. I don't see direct dependencies between these properties (when a property must be set in all cases another property is set). 2017-12-29 22:10 GMT+03:00 Valentin Kulichenko < valentin.kuliche...@gmail.com>: > Guys, > > I'm not sure what issue

Re: Spark data frames integration merged

Great news, Thanks Nikolay and Val! Nikolay, could you document the feature before the release [1]? I’ve granted you required permission. More on the doc process can be found here [2]. [1] https://issues.apache.org/jira/browse/IGNITE-7345

[jira] [Created] (IGNITE-7345) Spark Data Frames and Ignite Documentation

Denis Magda created IGNITE-7345: --- Summary: Spark Data Frames and Ignite Documentation Key: IGNITE-7345 URL: https://issues.apache.org/jira/browse/IGNITE-7345 Project: Ignite Issue Type: Task

Spark data frames integration merged

Igniters, Great news! We completed and merged first part of integration with Spark data frames [1]. It contains implementation of Spark data source which allows to use DataFrame API to query Ignite data, as well as join it with other data frames originated from different sources. Next planned

[GitHub] ignite pull request #2742: IGNITE-3084: Implementation of Spark DataFrame fo...

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

Re: Annoying extra steps for enabling metrics

Guys, I'm not sure what issue we're trying to solve. Basically, we have three different functionality parts here: 1. Cache metrics exposed via CacheMetrics interface and MBeans (number of puts, average put time, this kind of stuff). These are controlled on per cache level by

[GitHub] ignite pull request #3323: ignite-2.4.1-p7

GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/3323 ignite-2.4.1-p7 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.4.1-p7 Alternatively you can review and

Fwd: Request for contributors permissions

Make sure you are subscribed to both dev and user to receive the email: https://ignite.apache.org/community/resources.html#mail-lists > Begin forwarded message: > > From: Denis Magda > Subject: Re: Request for contributors permissions > Date: November 23, 2017 at 7:33:21 AM

Re: hi

Hello and welcome! Please get familiar with Ignite development process described here: https://cwiki.apache.org/confluence/display/IGNITE/Development+Process Subscribe to both dev and user lists: https://ignite.apache.org/community/resources.html#mail-lists

Re: Annoying extra steps for enabling metrics

Alexey, I think we should enable memoryEventStorageSPI automatically whenever statisticsEnabled is toggled on. A special message has to be added to the log pointing out that the automatic activation happened. Does it sound like a good solution? — Denis > On Dec 29, 2017, at 3:51 AM, Alexey

[GitHub] ignite pull request #3314: IGNITE-7214 performance measurement for FCM and K...

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

[jira] [Created] (IGNITE-7344) Fix yardstick devnotes

Oleg Ostanin created IGNITE-7344: Summary: Fix yardstick devnotes Key: IGNITE-7344 URL: https://issues.apache.org/jira/browse/IGNITE-7344 Project: Ignite Issue Type: Improvement

Re: Request for contributors permissions

up 2017-11-23 13:34 GMT+03:00 Alexander Kazantsev : > > Hello! > I want to fix one of ignite issue, but have not access to take issue. > Could you give me access or tell how to do it? > My nick is heruv1m in jira and email is a.u.kazant...@gmail.com >

[jira] [Created] (IGNITE-7343) Add guard to prevent concurrent usage the JDBC thin connection

Taras Ledkov created IGNITE-7343: Summary: Add guard to prevent concurrent usage the JDBC thin connection Key: IGNITE-7343 URL: https://issues.apache.org/jira/browse/IGNITE-7343 Project: Ignite

hi

Hello all I would like to join the dev group and contribute on ignite project.

[GitHub] ignite pull request #3322: IGNITE-7335: add multi-tread guard

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/3322 IGNITE-7335: add multi-tread guard You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7335 Alternatively

[jira] [Created] (IGNITE-7342) SQL TX: Fix checking whether currently updating row is updated after it pass query filter

Igor Seliverstov created IGNITE-7342: Summary: SQL TX: Fix checking whether currently updating row is updated after it pass query filter Key: IGNITE-7342 URL: https://issues.apache.org/jira/browse/IGNITE-7342

[GitHub] ignite pull request #3241: IGNITE-7097 performance measurement for SparseDis...

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

Re: Annoying extra steps for enabling metrics

Denis, I start working on the issue https://issues.apache.org/jira/browse/IGNITE-6925 and now I don't understand why these properties must be bound to each other? • If we enable statistics on caches, this does not necessarily mean, that we wanted to get some events, we can enable statistics for

[jira] [Created] (IGNITE-7341) Inconsistent data in case of error during rebalance

Semen Boikov created IGNITE-7341: Summary: Inconsistent data in case of error during rebalance Key: IGNITE-7341 URL: https://issues.apache.org/jira/browse/IGNITE-7341 Project: Ignite Issue

[GitHub] ignite pull request #3321: Ignite-2.4-java9

GitHub user agura opened a pull request: https://github.com/apache/ignite/pull/3321 Ignite-2.4-java9 You can merge this pull request into a Git repository by running: $ git pull https://github.com/agura/incubator-ignite ignite-2.4-java9 Alternatively you can review and apply

RE: Handling slashes in cache names

> I would surround such replacements with "_", e.g. "myCacheName_somesymbol_". Looks nice, will do. > Here I am confused. I think the cache names should be case insensitive at > all times. I seriously doubt enforcing this rule would cause problems. If > we enforce this rule at cache creation

[GitHub] ignite pull request #3320: Gg 13139

GitHub user slukyano opened a pull request: https://github.com/apache/ignite/pull/3320 Gg 13139 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite gg-13139 Alternatively you can review and apply these

[GitHub] ignite pull request #3319: IGNITE-7340 - Fix flaky GridServiceProcessorMulti...

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/3319 IGNITE-7340 - Fix flaky GridServiceProcessorMultiNodeConfigSelfTest#c… …heckDeployOnEachNodeUpdateTopology You can merge this pull request into a Git repository by running: $ git

[jira] [Created] (IGNITE-7340) Fix flaky org.apache.ignite.internal.processors.service.GridServiceProcessorMultiNodeConfigSelfTest#checkDeployOnEachNodeUpdateTopology

Dmitry Karachentsev created IGNITE-7340: --- Summary: Fix flaky org.apache.ignite.internal.processors.service.GridServiceProcessorMultiNodeConfigSelfTest#checkDeployOnEachNodeUpdateTopology Key: IGNITE-7340

[jira] [Created] (IGNITE-7339) RENTING partition is not evicted after restore from storage

Semen Boikov created IGNITE-7339: Summary: RENTING partition is not evicted after restore from storage Key: IGNITE-7339 URL: https://issues.apache.org/jira/browse/IGNITE-7339 Project: Ignite