[jira] [Created] (IGNITE-3233) need to optimize injections

Yakov Zhdanov created IGNITE-3233: - Summary: need to optimize injections Key: IGNITE-3233 URL: https://issues.apache.org/jira/browse/IGNITE-3233 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-3232) Ignite RDD: need to add transformer closure to saveValues and savePairs

Yakov Zhdanov created IGNITE-3232: - Summary: Ignite RDD: need to add transformer closure to saveValues and savePairs Key: IGNITE-3232 URL: https://issues.apache.org/jira/browse/IGNITE-3232 Project:

[GitHub] ignite pull request #771: IGNITE-3231 add the unimplement method

GitHub user f7753 opened a pull request: https://github.com/apache/ignite/pull/771 IGNITE-3231 add the unimplement method `GridCachePartitionedNearDisabledFairAffinityMultiNodeFullApiSelfTest` must either be declared abstract or implement method `gridCount()` You can merge

[jira] [Created] (IGNITE-3231) GridCachePartitionedNearDisabledFairAffinityMultiNodeFullApiSelfTest must either be declared abstract or implement method 'instanceCount()'

Biao Ma created IGNITE-3231: --- Summary: GridCachePartitionedNearDisabledFairAffinityMultiNodeFullApiSelfTest must either be declared abstract or implement method 'instanceCount()' Key: IGNITE-3231 URL:

Re: Let's make cache name not null in ignite 2.0

Warning is OK, but removing null name after having it for almost 2 years is a bad idea. People are using it and will be forced to change their code for no good reason. On Wed, Jun 1, 2016 at 5:20 PM, Alexey Goncharuk wrote: > We can add an explicit warning in 1.x

Re: Let's make cache name not null in ignite 2.0

We can add an explicit warning in 1.x when a cache with the null name is used and remove it in 2.0. 2016-06-01 15:49 GMT-07:00 Dmitriy Setrakyan : > -1 > > I don’t think this will give us any advantage other than many frustrated > users who will need to change their code.

Re: Let's make cache name not null in ignite 2.0

-1 I don’t think this will give us any advantage other than many frustrated users who will need to change their code. We should definitely discourage using nulls though. D. On Wed, Jun 1, 2016 at 12:37 AM, Vladimir Ozerov wrote: > +1 > > I would also restrict nulls for

[jira] [Created] (IGNITE-3230) External addresses are not registered in IP finder

Valentin Kulichenko created IGNITE-3230: --- Summary: External addresses are not registered in IP finder Key: IGNITE-3230 URL: https://issues.apache.org/jira/browse/IGNITE-3230 Project: Ignite

[GitHub] ignite pull request #770: IGNITE-3229 un existing link in Class GridCacheSto...

GitHub user f7753 opened a pull request: https://github.com/apache/ignite/pull/770 IGNITE-3229 un existing link in Class GridCacheStoreValueBytesSelfTest Class GridCacheStoreValueBytesSelfTest' s annotation has linked to an un existing method

[GitHub] ignite pull request #761: IGNITE-3207 Rename IgniteConfiguration.gridName

Github user f7753 closed the pull request at: https://github.com/apache/ignite/pull/761 --- 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-3229) un existing link in Class GridCacheStoreValueBytesSelfTest

Biao Ma created IGNITE-3229: --- Summary: un existing link in Class GridCacheStoreValueBytesSelfTest Key: IGNITE-3229 URL: https://issues.apache.org/jira/browse/IGNITE-3229 Project: Ignite Issue

[jira] [Created] (IGNITE-3228) Hadoop: Invalid page allocation logic inside HadoopMultimapBase

Vladimir Ozerov created IGNITE-3228: --- Summary: Hadoop: Invalid page allocation logic inside HadoopMultimapBase Key: IGNITE-3228 URL: https://issues.apache.org/jira/browse/IGNITE-3228 Project:

[jira] [Created] (IGNITE-3227) IgniteCache: add method to calculate size per partition

Denis Magda created IGNITE-3227: --- Summary: IgniteCache: add method to calculate size per partition Key: IGNITE-3227 URL: https://issues.apache.org/jira/browse/IGNITE-3227 Project: Ignite Issue

[GitHub] ignite pull request: IGNITE-2310 Lock cache partition for affinityRun/affini...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/769 IGNITE-2310 Lock cache partition for affinityRun/affinityCall execution You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-3226) Load test: iteration over cache partitions using scan queries and performing transactions

Denis Magda created IGNITE-3226: --- Summary: Load test: iteration over cache partitions using scan queries and performing transactions Key: IGNITE-3226 URL: https://issues.apache.org/jira/browse/IGNITE-3226

[jira] [Created] (IGNITE-3225) Does not work preview in IGFS section of cluster

Vasiliy Sisko created IGNITE-3225: - Summary: Does not work preview in IGFS section of cluster Key: IGNITE-3225 URL: https://issues.apache.org/jira/browse/IGNITE-3225 Project: Ignite Issue

[jira] [Created] (IGNITE-3224) Does not work Undo for General - Apache ZooKeeper - Retry policy

Vasiliy Sisko created IGNITE-3224: - Summary: Does not work Undo for General - Apache ZooKeeper - Retry policy Key: IGNITE-3224 URL: https://issues.apache.org/jira/browse/IGNITE-3224 Project: Ignite

Re: Let's make cache name not null in ignite 2.0

+1 I would also restrict nulls for node names, for IGFS names, etc.. On Wed, Jun 1, 2016 at 10:29 AM, Alexey Kuznetsov wrote: > Hi, All! > > In ignite-1.x cache.name could be null. > > And we have to write a lot of code to handle such name, especially in tools > like

Let's make cache name not null in ignite 2.0

Hi, All! In ignite-1.x cache.name could be null. And we have to write a lot of code to handle such name, especially in tools like web console and Visor. In ignite 2.0 we could change API and make cache.name not null. What do you think about such change? It is worth to create such issue in