[jira] [Created] (IGNITE-3223) Wrong value in table editor

Vasiliy Sisko created IGNITE-3223: - Summary: Wrong value in table editor Key: IGNITE-3223 URL: https://issues.apache.org/jira/browse/IGNITE-3223 Project: Ignite Issue Type: Sub-task

Re: 1.6 version in Jira is not released

Thanks! On Tue, May 31, 2016 at 5:23 PM, Yakov Zhdanov wrote: > Done. > > --Yakov > > 2016-05-30 11:41 GMT-04:00 Dmitriy Setrakyan : > > > Guys, > > > > Can we release version 1.6 in Jira? Currently I can still assign tickets > to > > version 1.6, which is not correct. > > > > D. > > >

Re: 1.6 version in Jira is not released

Done. --Yakov 2016-05-30 11:41 GMT-04:00 Dmitriy Setrakyan : > Guys, > > Can we release version 1.6 in Jira? Currently I can still assign tickets to > version 1.6, which is not correct. > > D. >

Re: IgniteCache.invoke on ALL keys

Pavel, I actually believe that such method will be error-prone and will cause all sorts of memory issues for users trying to execute this method over large caches. What we need instead is an affinityCall/Run method over a partition, not a key. Why not provide this method instead? Added my commen

Dynamic (-like) byte-code modifications [Was: Documentation for AOP-based Grid Enabling]

Thanks for putting the docs together Prachi! I am also quite a bit surprised that Ignite has the support for AOP. As a side topic, and the one for an overall amusement: - do people think it might be a good time to revisit the use of "last century" programming techniques, which are build tim

[GitHub] ignite pull request: Ignite 3190

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

[GitHub] ignite pull request: IGNITE-3151

GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/768 IGNITE-3151 Using IgniteCountDownLatch sometimes drives to dead lock. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vldpyatkov/ignite ignite

[GitHub] ignite pull request: IGNITE-1915 .Net: Ignite as Entity Framework Second-Lev...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/767 IGNITE-1915 .Net: Ignite as Entity Framework Second-Level Cache You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-1915

Re: Documentation for AOP-based Grid Enabling

Prachi, Looks good to me. If there is anyone in the community who made it hands dirty with AOP and Ignite please review the documentation from Prachi as well. — Denis > On May 27, 2016, at 2:17 PM, Denis Magda wrote: > > Hi Prachi, > > Great, to be honest I didn’t suspect Ignite supports t

Re: IgniteCache.invoke on ALL keys

Ok then, looks like there are no obstacles or objections, I've created a JIRA ticket: https://issues.apache.org/jira/browse/IGNITE-3222 Thanks, Pavel. On Tue, May 31, 2016 at 3:44 PM, Denis Magda wrote: > Pavel, > > > This seems to be a common task, why don't we implement invokeAll as I > > sug

[jira] [Created] (IGNITE-3222) IgniteCache.invokeAll for all cache entries

Pavel Tupitsyn created IGNITE-3222: -- Summary: IgniteCache.invokeAll for all cache entries Key: IGNITE-3222 URL: https://issues.apache.org/jira/browse/IGNITE-3222 Project: Ignite Issue Type:

Re: IgniteCache.invoke on ALL keys

Pavel, > This seems to be a common task, why don't we implement invokeAll as I > suggested above? I would implement such a method using the approach shown in the example. In my understanding it would be the most efficient way. Data locality will longer be not an issue when IGNITE-2310 is implem

[jira] [Created] (IGNITE-3221) Bad ip used , when fixed ip in hostname

sebastien diaz created IGNITE-3221: -- Summary: Bad ip used , when fixed ip in hostname Key: IGNITE-3221 URL: https://issues.apache.org/jira/browse/IGNITE-3221 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request: 7.6.1

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

[GitHub] ignite pull request: 7.6.1

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

[GitHub] ignite pull request: 7.6.1

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

Re: IgniteCache.invoke on ALL keys

Denis, thank you, this may work, but: * it is too complicated * it does not guarantee locality This seems to be a common task, why don't we implement invokeAll as I suggested above? On Tue, May 31, 2016 at 1:05 PM, Denis Magda wrote: > Pavel, > > Here is an example on how to execute scan querie

Re: IgniteCache.invoke on ALL keys

Pavel, Here is an example on how to execute scan queries on partitions’ owners and perform some operation for every entry https://github.com/gridgain/gridgain-advanced-examples/blob/master/src/main/java/org/gridgain/examples/datagrid/query/ScanQueryExample.java

[jira] [Created] (IGNITE-3220) I/O bottleneck on server/client cluster configuration.

Alexei Scherbakov created IGNITE-3220: - Summary: I/O bottleneck on server/client cluster configuration. Key: IGNITE-3220 URL: https://issues.apache.org/jira/browse/IGNITE-3220 Project: Ignite

[jira] [Created] (IGNITE-3219) Not work validation of nester forms on save.

Vasiliy Sisko created IGNITE-3219: - Summary: Not work validation of nester forms on save. Key: IGNITE-3219 URL: https://issues.apache.org/jira/browse/IGNITE-3219 Project: Ignite Issue Type: S

[jira] [Created] (IGNITE-3218) Partition can not be reserved

Vladislav Pyatkov created IGNITE-3218: - Summary: Partition can not be reserved Key: IGNITE-3218 URL: https://issues.apache.org/jira/browse/IGNITE-3218 Project: Ignite Issue Type: Bug