[GitHub] ignite pull request #2306: Ignite 1.8.9

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

[jira] [Created] (IGNITE-5761) Add correct message when entries does not mapped to even one node (and avoid hang on rollback any way).

Igor Seliverstov created IGNITE-5761: Summary: Add correct message when entries does not mapped to even one node (and avoid hang on rollback any way). Key: IGNITE-5761 URL: https://issues.apache.org/jira/brows

[GitHub] ignite pull request #2307: ignite-5733: add http rest to activate/deactivate...

GitHub user abeliak opened a pull request: https://github.com/apache/ignite/pull/2307 ignite-5733: add http rest to activate/deactivate/checkState You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5733

HttpRest API with active/inactive/currentState commands

Hi, I'v made small branch with new http rest api commands to activate, deactivate and check current state of cluster. review link: http://reviews.ignite.apache.org/ignite/review/IGNT-CR-234 apache issue link: https://issues.apache.org/jira/browse/IGNITE-5733 can anyone review&merge this? Best regar

[jira] [Created] (IGNITE-5762) Skip deploy lgpl modules into repositiry

Oleg Ostanin created IGNITE-5762: Summary: Skip deploy lgpl modules into repositiry Key: IGNITE-5762 URL: https://issues.apache.org/jira/browse/IGNITE-5762 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request #2308: IGNITE-5762 skipping lgpl and examples deploy

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/2308 IGNITE-5762 skipping lgpl and examples deploy You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5762 Alternat

[GitHub] ignite pull request #2309: IGNITE-5761

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

[jira] [Created] (IGNITE-5763) Race in concurrent client cache start

Semen Boikov created IGNITE-5763: Summary: Race in concurrent client cache start Key: IGNITE-5763 URL: https://issues.apache.org/jira/browse/IGNITE-5763 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-5764) web console: delete sql command doesn't work

Pavel Konstantinov created IGNITE-5764: -- Summary: web console: delete sql command doesn't work Key: IGNITE-5764 URL: https://issues.apache.org/jira/browse/IGNITE-5764 Project: Ignite Is

Re: xml config can not be used in jdbs and user code simultaneously

I would say this is a usability issue, please file a ticket. But why one need to use JDBC when already on Ignite node? On Fri, Jul 14, 2017 at 4:30 PM, Mikhail Cherkasov wrote: > Hi all, > > when user uses the same xml config for jdbc driver and for his own ignite > instance there can be : > jav

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

Subj: https://ptupitsyn.github.io/Ignite-Plugin/ Pavel

[jira] [Created] (IGNITE-5765) CacheMetrics interface cleanup, documentation and fixes

Sergey Chugunov created IGNITE-5765: --- Summary: CacheMetrics interface cleanup, documentation and fixes Key: IGNITE-5765 URL: https://issues.apache.org/jira/browse/IGNITE-5765 Project: Ignite

[jira] [Created] (IGNITE-5766) Folder platform/cpp/bin and files inside this folder are missing in 2.1

Alex Volkov created IGNITE-5766: --- Summary: Folder platform/cpp/bin and files inside this folder are missing in 2.1 Key: IGNITE-5766 URL: https://issues.apache.org/jira/browse/IGNITE-5766 Project: Ignite

[jira] [Created] (IGNITE-5767) Web console: use byte array type instead of java.lang.Object for binary JDBC types

Semen Boikov created IGNITE-5767: Summary: Web console: use byte array type instead of java.lang.Object for binary JDBC types Key: IGNITE-5767 URL: https://issues.apache.org/jira/browse/IGNITE-5767 Pr

[CANCEL] [VOTE] Apache Ignite 2.1.0 RC1

Officially cancelling the vote. -- Forwarded message -- From: Denis Magda Date: Sat, Jul 15, 2017 at 4:48 PM Subject: Re: [VOTE] Apache Ignite 2.1.0 RC1 To: "dev@ignite.apache.org" -1 Because of the lgpl libraries issue. Please fix the bug and restart the vote. Denis On Satu

[GitHub] ignite pull request #2310: removed excluding ML sources from assembly file

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/2310 removed excluding ML sources from assembly file You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.1-include

Re: Cache Metrics

Hi, I believe that the first solution is better than second because it takes into account network communication time. Average time of communication between nodes doesn't make sense from my point of view. So I vote for #1. On Thu, Jul 13, 2017 at 11:52 PM, Вячеслав Коптилин wrote: > Hi Experts,

[jira] [Created] (IGNITE-5768) Retry resolving class name from marshaller cache and .classname file

Dmitry Karachentsev created IGNITE-5768: --- Summary: Retry resolving class name from marshaller cache and .classname file Key: IGNITE-5768 URL: https://issues.apache.org/jira/browse/IGNITE-5768 Pr

[GitHub] ignite pull request #2311: Ignite 5768 Retry resolving class name from marsh...

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/2311 Ignite 5768 Retry resolving class name from marshaller cache and .classname file You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgai

[jira] [Created] (IGNITE-5769) Abstract away unmanaged calls

Pavel Tupitsyn created IGNITE-5769: -- Summary: Abstract away unmanaged calls Key: IGNITE-5769 URL: https://issues.apache.org/jira/browse/IGNITE-5769 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-5770) Refactor PlatformProcessor to PlatformTarget mechanism

Pavel Tupitsyn created IGNITE-5770: -- Summary: Refactor PlatformProcessor to PlatformTarget mechanism Key: IGNITE-5770 URL: https://issues.apache.org/jira/browse/IGNITE-5770 Project: Ignite I

[jira] [Created] (IGNITE-5771) Add Ignite.setActive method to C++ API

Denis Magda created IGNITE-5771: --- Summary: Add Ignite.setActive method to C++ API Key: IGNITE-5771 URL: https://issues.apache.org/jira/browse/IGNITE-5771 Project: Ignite Issue Type: New Feature

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

Guys, what’s the status? Who and when is going to send the next build for vote? — Denis > On Jul 17, 2017, at 5:50 AM, Vladimir Ozerov wrote: > > Officially cancelling the vote. > > -- Forwarded message -- > From: Denis Magda > Date: Sat, Jul 15, 2017 at 4:48 PM > Subject: Re:

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

Pavel, the blog post is well deserved to be mentioned on this documentation page! https://apacheignite-net.readme.io/docs/plugins Please add it using a “callout” block of readme. — Denis > On Jul 17, 2017, at 3:31 AM, Pavel Tupitsyn wrote: >

[VOTE] Apache Ignite 2.1.0 RC2

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 changes: Ignite: * Persistent cache store * Added IgniteFuture.listenAsync() and IgniteFuture.chainAsync() mehtods * Dep

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 using a “callout” b