[jira] [Created] (IGNITE-5107) Remove nonHeapMemoryCommitted and nonHeapMemoryUsed from cluster metrics

Alexey Goncharuk created IGNITE-5107: Summary: Remove nonHeapMemoryCommitted and nonHeapMemoryUsed from cluster metrics Key: IGNITE-5107 URL: https://issues.apache.org/jira/browse/IGNITE-5107 Proj

[jira] [Created] (IGNITE-5108) Fix JavaDoc warning

Vladimir Ozerov created IGNITE-5108: --- Summary: Fix JavaDoc warning Key: IGNITE-5108 URL: https://issues.apache.org/jira/browse/IGNITE-5108 Project: Ignite Issue Type: Bug Componen

Re: Ignite ML, next steps (IGNITE-5029)

Alexey, Thanks for this advice. We will refactor this matrix. I think that one dedicated cache for ML sparse distributed matrices will good solution. In that case we need implementation of giveNextCacheKeySet() logic foreach new matrix instead of new cache creation. -- View this message in con

[jira] [Created] (IGNITE-5109) Refactoring for SparseDistributedMatrix

Yury Babak created IGNITE-5109: -- Summary: Refactoring for SparseDistributedMatrix Key: IGNITE-5109 URL: https://issues.apache.org/jira/browse/IGNITE-5109 Project: Ignite Issue Type: Bug

Re: Ignite ML, next steps (IGNITE-5029)

Update: I've created ticket for this: IGNITE-5109 . Regards, Yury Babak. -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-ML-next-steps-IGNITE-5029-tp17096p17316.html Sent from the Apache Ignite

[jira] [Created] (IGNITE-5110) Topology version should be included in synchronous continuous message

Alexey Goncharuk created IGNITE-5110: Summary: Topology version should be included in synchronous continuous message Key: IGNITE-5110 URL: https://issues.apache.org/jira/browse/IGNITE-5110 Project

Ignite.createCache(CacheConfiguration) hangs if some exception occurs during cache initialization Ignite-1049

Hi, Igntrs! https://issues.apache.org/jira/browse/IGNITE-1094 I've come up with solution. Put exception into GridDhtPartitionsSingleMessage indicating cache creation failed on local node. Send it to coordinator. Coordinator's GridCachePartitionExchangeManager while processing would extract exchang

[GitHub] ignite pull request #1884: IGNITE-4763

GitHub user NSAmelchev opened a pull request: https://github.com/apache/ignite/pull/1884 IGNITE-4763 - doSetRollbackOnly method to be implemented in SpringTransactionManager - testDoSetRollbackOnlyInExistingTransaction You can merge this pull request into a Git repository by run

Re: IGNITE-4763 - ready for review.

Hello. I add test. Please review. https://issues.apache.org/jira/browse/IGNITE-4763 PR: https://github.com/apache/ignite/pull/1884/files ci test: http://ci.ignite.apache.org/project.html?projectId=IgniteTests&branch_IgniteTests=pull/1884/head 2017-04-27 19:15 GMT+03:00 Denis Magda : > Nikita

[jira] [Created] (IGNITE-5111) Refactor Platform remote job execution routine for PlatformClosureJob

Igor Sapego created IGNITE-5111: --- Summary: Refactor Platform remote job execution routine for PlatformClosureJob Key: IGNITE-5111 URL: https://issues.apache.org/jira/browse/IGNITE-5111 Project: Ignite

[GitHub] ignite pull request #1885: IGNITE-4575: SQL support for enum

GitHub user skalashnikov opened a pull request: https://github.com/apache/ignite/pull/1885 IGNITE-4575: SQL support for enum You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4575 Alternatively you ca

Re: Ignite.createCache(CacheConfiguration) hangs if some exception occurs during cache initialization Ignite-1049

Aleksey, I am thinking on whether we should do this during exchange step or not. In principle, validation is rather fast operation, so we can do it inside discovery thread even before descriptor is created and registered. Alex G., Semen, What do you think? On Fri, Apr 28, 2017 at 12:36 PM, ALEKSE

Re: Ignite.createCache(CacheConfiguration) hangs if some exception occurs during cache initialization Ignite-1049

validation must have involve calling StoreFactory.create() . So we create store at first? If so, should we notify coordinator and other nodes about bad cache ? Perhaps, initiating node should throw exception and don't notify coordinator, and other nodes should silently keep on working ? пт, 28 ап

[GitHub] ignite pull request #1886: Ignite 2.0 temp for fix hibernate upload

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/1886 Ignite 2.0 temp for fix hibernate upload You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.0-temp-for-fix-h

[jira] [Created] (IGNITE-5112) Create OLS example

Yury Babak created IGNITE-5112: -- Summary: Create OLS example Key: IGNITE-5112 URL: https://issues.apache.org/jira/browse/IGNITE-5112 Project: Ignite Issue Type: Task Components: ml

[jira] [Created] (IGNITE-5113) K-means clustering

Yury Babak created IGNITE-5113: -- Summary: K-means clustering Key: IGNITE-5113 URL: https://issues.apache.org/jira/browse/IGNITE-5113 Project: Ignite Issue Type: New Feature Components:

[jira] [Created] (IGNITE-5114) Parallalel plus/multiply matrix algorithms.

Yury Babak created IGNITE-5114: -- Summary: Parallalel plus/multiply matrix algorithms. Key: IGNITE-5114 URL: https://issues.apache.org/jira/browse/IGNITE-5114 Project: Ignite Issue Type: Improvem

Re: Ignite ML, next steps (IGNITE-5029)

Guys, Here's update with some details. We expect several new features/bugfixes: * Ordinary least squares (OLS) linear regression, IGNITE-5012 . * OLS examples, IGNITE-5112 . * Logistic reg

[jira] [Created] (IGNITE-5115) Investigation of failing tests of coordinator node failure

Sergey Chugunov created IGNITE-5115: --- Summary: Investigation of failing tests of coordinator node failure Key: IGNITE-5115 URL: https://issues.apache.org/jira/browse/IGNITE-5115 Project: Ignite

[jira] [Created] (IGNITE-5116) Handle cache destroy in DmlStatementsProcessor

Alexander Paschenko created IGNITE-5116: --- Summary: Handle cache destroy in DmlStatementsProcessor Key: IGNITE-5116 URL: https://issues.apache.org/jira/browse/IGNITE-5116 Project: Ignite

Re: Apache Ignite 2.0 Release

Igniters, Looks like all tickets for AI 2.0 are merged. I am going to start vote in the nearest time. On Wed, Apr 26, 2017 at 2:27 PM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Roman, > > Thanks for the contribution, I merged your changes to ignite-2.0 branch. > > 2017-04-26 7:12 G

[GitHub] ignite pull request #1887: ignite-5012: Implemented OLSMultipleLinearRegress...

GitHub user artemmalykh opened a pull request: https://github.com/apache/ignite/pull/1887 ignite-5012: Implemented OLSMultipleLinearRegression with tests. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ign

[GitHub] ignite pull request #1888: Test 3.ea6

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/1888 Test 3.ea6 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-8.0.3.ea6 Alternatively you can review and apply

[VOTE] Apache Ignite 2.0.0 RC1

Igniters! We have uploaded a 2.0.0 release candidate to https://dist.apache.org/repos/dist/dev/ignite/2.0.0-rc1/ Git tag name is 2.0.0-rc1 This release includes the following changes: Ignite: * Introduced new page memory architecture. * Machine Learning beta: distributed algebra support for den

[jira] [Created] (IGNITE-5117) Ignite node in AWS ECS

vijay c created IGNITE-5117: --- Summary: Ignite node in AWS ECS Key: IGNITE-5117 URL: https://issues.apache.org/jira/browse/IGNITE-5117 Project: Ignite Issue Type: Bug Components: ignite-zo

Re: [VOTE] Apache Ignite 2.0.0 RC1

+1 28 апр. 2017 г. 22:43 пользователь "Denis Magda" написал: > Igniters! > > We have uploaded a 2.0.0 release candidate to > https://dist.apache.org/repos/dist/dev/ignite/2.0.0-rc1/ > > Git tag name is > 2.0.0-rc1 > > This release includes the following changes: > > Ignite: > * Introduced new pa

Re: [VOTE] Apache Ignite 2.0.0 RC1

Hi Guys, Sorry to post this in a voting thread, but I tried to update a project to 2.0 (using the git tag Denis referred to) and I'm seeing what I assume is a regression. In short, attempts to access a pre-configured cache within the onIgniteStart() method of a PluginProvider now returns null inst

Re: BinaryObjectImpl.deserializeValue with specific ClassLoader

Hey Denis, I tried your solution as that is what Alexei was more-or-less suggesting: create a delegating classloader, but in this case delegate to whatever context class loader is set. The problem is that resolved classes will always be stored by the instantiated classloader, which would be the de

[jira] [Created] (IGNITE-5118) Table with name Object lead to compilation error in code generated by webconsole

Evgenii Zhuravlev created IGNITE-5118: - Summary: Table with name Object lead to compilation error in code generated by webconsole Key: IGNITE-5118 URL: https://issues.apache.org/jira/browse/IGNITE-5118