Re: [CANCEL] [VOTE] Apache Ignite 2.1.0 RC1

Won't the release manager be the "who"? -- With regards, Konstantin (Cos) Boudnik 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 Disclaimer: Opinions expressed in this email are those of the author, and do not necessarily represent the views of any company the author might be affiliated

Pages metric report

Hi All, I have just started learning and working with Ignite and I'm about to rise IGNITE JIRAs for next requirements. Could you please check maybe there are already exists. Would it be significant overhead for a cluster? #1 For tuning system performance it'd be great to get detail information

Re: usage analytics

I would try to ping legal again and see if they respond. If not, I think we will need to come up with a simpler approach, that does not require legal approval. ⁣D.​ On Jul 18, 2017, 2:23 PM, at 2:23 PM, Nikita Ivanov wrote: >Igniters, >Just a quick update. I haven't

[jira] [Created] (IGNITE-5780) DDL: support custom schema creation

Denis Magda created IGNITE-5780: --- Summary: DDL: support custom schema creation Key: IGNITE-5780 URL: https://issues.apache.org/jira/browse/IGNITE-5780 Project: Ignite Issue Type: New Feature

Re: usage analytics

Igniters, Just a quick update. I haven't gotten response from ASF Legal on this thread and I frankly don't know how to proceed here. What's the process to arrive to a decision point here? Thanks! -- Nikita Ivanov On Mon, Jul 10, 2017 at 3:11 PM, Konstantin Boudnik wrote: > On

Re: [VOTE] Apache Ignite 2.1.0 RC2

+1 (binding) On Tue, Jul 18, 2017 at 11:40 AM, Denis Magda wrote: > +1 (binding) > > — > Denis > > > On Jul 17, 2017, at 9:42 PM, Vladimir Ozerov > wrote: > > > > Igniters! > > > > We have uploaded a 2.1.0 release candidate to > >

Re: [VOTE] Apache Ignite 2.1.0 RC2

+1 (binding) — Denis > On Jul 17, 2017, at 9:42 PM, Vladimir Ozerov wrote: > > Igniters! > > We have uploaded a 2.1.0 release candidate to > https://dist.apache.org/repos/dist/dev/ignite/2.1.0-rc2/ > > Git tag name is > 2.1.0-rc2 > > This release includes the following

Fwd: July 19 webinar: Distributed ACID transactions in Apache® Ignite™

Cross-posting to the dev list > Begin forwarded message: > > From: Dieds > Subject: July 19 webinar: Distributed ACID transactions in Apache® Ignite™ > Date: July 18, 2017 at 9:50:52 AM PDT > To: u...@ignite.apache.org > Reply-To: u...@ignite.apache.org > >

[GitHub] ignite pull request #2319: IGNITE-5775 JobsProcessor: Remove job from active...

GitHub user ezhuravl opened a pull request: https://github.com/apache/ignite/pull/2319 IGNITE-5775 JobsProcessor: Remove job from activeJobs before invoke o… …nCollision You can merge this pull request into a Git repository by running: $ git pull

Re: New method for MemoryMetrics: segment fill variance

Ivan, How about renaming it to hashFunctionScore? This will be more digestable to users. "segmentFillVariance" sounds too scientific even to me. D. On Tue, Jul 18, 2017 at 10:39 AM, Ivan Rakov wrote: > Hello Igniters, > > I want to propose one more method for memory

[jira] [Created] (IGNITE-5779) Incorrect mapping of smallint cassandra type.

Andrew Mashenkov created IGNITE-5779: Summary: Incorrect mapping of smallint cassandra type. Key: IGNITE-5779 URL: https://issues.apache.org/jira/browse/IGNITE-5779 Project: Ignite Issue

[GitHub] ignite pull request #2318: checkpoint marker guaranteed read

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/2318 checkpoint marker guaranteed read You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-12505

New method for MemoryMetrics: segment fill variance

Hello Igniters, I want to propose one more method for memory metrics - segmentFillVariance, float value from 0.0 to 1.0. Motivation: when persistence is enabled, we split memory policy into K equal segments (K = concurrency level). We calculate hash of pageId to determine segment where page

[jira] [Created] (IGNITE-5778) Update JobMetrics on each job add/start/finish methods and add possibility to turn out JobMetrics and

Evgenii Zhuravlev created IGNITE-5778: - Summary: Update JobMetrics on each job add/start/finish methods and add possibility to turn out JobMetrics and Key: IGNITE-5778 URL:

[GitHub] ignite pull request #2317: IGNITE-5776 Add option to turn on filter reachabl...

GitHub user ezhuravl opened a pull request: https://github.com/apache/ignite/pull/2317 IGNITE-5776 Add option to turn on filter reachable addresses in TcpCo… …mmunicationSpi You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #2316: IGNITE-5776 Add option to turn on filter reachabl...

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

[jira] [Created] (IGNITE-5777) BLAS integration

Yury Babak created IGNITE-5777: -- Summary: BLAS integration Key: IGNITE-5777 URL: https://issues.apache.org/jira/browse/IGNITE-5777 Project: Ignite Issue Type: Task Components: ml

[GitHub] ignite pull request #2316: IGNITE-5776 Add option to turn on filter reachabl...

GitHub user ezhuravl opened a pull request: https://github.com/apache/ignite/pull/2316 IGNITE-5776 Add option to turn on filter reachable addresses in TcpCommunicationSpi You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-5776) Add option to turn out filter reachable addresses in TcpCommunicationSpi

Evgenii Zhuravlev created IGNITE-5776: - Summary: Add option to turn out filter reachable addresses in TcpCommunicationSpi Key: IGNITE-5776 URL: https://issues.apache.org/jira/browse/IGNITE-5776

[GitHub] ignite pull request #2315: IGNITE-4800: Lucene query may fails with NPE.

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/2315 IGNITE-4800: Lucene query may fails with NPE. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4800

[GitHub] ignite pull request #2314: IGNITE-5551 Optimize service deployment assignmen...

GitHub user kukushal opened a pull request: https://github.com/apache/ignite/pull/2314 IGNITE-5551 Optimize service deployment assignments object You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[jira] [Created] (IGNITE-5775) Compute runs one job in MetricsUpdateFrequency per thread after all jobs was submitted(as onCollision is not invokes)

Evgenii Zhuravlev created IGNITE-5775: - Summary: Compute runs one job in MetricsUpdateFrequency per thread after all jobs was submitted(as onCollision is not invokes) Key: IGNITE-5775 URL:

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

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

[jira] [Created] (IGNITE-5774) Print more information about long partition release future

Alexey Goncharuk created IGNITE-5774: Summary: Print more information about long partition release future Key: IGNITE-5774 URL: https://issues.apache.org/jira/browse/IGNITE-5774 Project: Ignite

[GitHub] ignite pull request #2312: IGNITE-5174, list only server nodes for specified...

GitHub user zstan opened a pull request: https://github.com/apache/ignite/pull/2312 IGNITE-5174, list only server nodes for specified topology version You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[jira] [Created] (IGNITE-5773) Scheduler throwing NullPointerException

Mikhail Cherkasov created IGNITE-5773: - Summary: Scheduler throwing NullPointerException Key: IGNITE-5773 URL: https://issues.apache.org/jira/browse/IGNITE-5773 Project: Ignite Issue

[jira] [Created] (IGNITE-5772) Race between WAL segment rollover and concurrent log

Alexey Goncharuk created IGNITE-5772: Summary: Race between WAL segment rollover and concurrent log Key: IGNITE-5772 URL: https://issues.apache.org/jira/browse/IGNITE-5772 Project: Ignite

[GitHub] ignite pull request #1910: IGNITE-5174 client nodes filter func

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

Re: New blog post: Implementing Ignite.NET Plugin, interacting with Java

Good point, done. On Tue, Jul 18, 2017 at 2:35 AM, Denis Magda wrote: > Pavel, the blog post is well deserved to be mentioned on this > documentation page! > https://apacheignite-net.readme.io/docs/plugins readme.io/docs/plugins> > > Please add it