[jira] [Created] (IGNITE-2539) NPE at RendezvousAffinityFunction

Vladimir Ershov created IGNITE-2539: --- Summary: NPE at RendezvousAffinityFunction Key: IGNITE-2539 URL: https://issues.apache.org/jira/browse/IGNITE-2539 Project: Ignite Issue Type: Bug

Re: Ticket IGNITE-1497

Hi Thorsten! IGNITE-2080 should fix this problem. Fix was merged into master branch yesterday. So you can build latest Ignite from sources and try to run it on your device. Please, let me know about result. Thanks! On Wed, Feb 3, 2016 at 12:35 PM, Yakov Zhdanov wrote: >

Re: [jira] [Commented] (IGNITE-1523) Need to always serialize user objects with configured marshaller

Val, I've fixed some cases related to this issue. In case you know what is left please describe it at issue and assign to me On Tue, Feb 2, 2016 at 9:20 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Anton, > > If you're working in this issue, can you please assign it to

[jira] [Created] (IGNITE-2540) GridNioServer.processWrite() generates garbage.

Vladimir Ozerov created IGNITE-2540: --- Summary: GridNioServer.processWrite() generates garbage. Key: IGNITE-2540 URL: https://issues.apache.org/jira/browse/IGNITE-2540 Project: Ignite Issue

Re: Full API coverage enhancement

Igniters, I thought a little bit more and think we need to add a support for the following permutations too (I've added these to the jira description): - We should also test with Serializable, Externalizable, and plain Pojos for keys and values. - The Pojo in the above test should contain an enum

[jira] [Created] (IGNITE-2541) Potential NPE in GridCacheUpdateAtomicResult

Vladimir Ozerov created IGNITE-2541: --- Summary: Potential NPE in GridCacheUpdateAtomicResult Key: IGNITE-2541 URL: https://issues.apache.org/jira/browse/IGNITE-2541 Project: Ignite Issue

Re: Ticket IGNITE-1497

Hello Thorsten! I am not working on this ticket and most probably will not have time to start in nearest future. I am CCing project's dev list. Andrey Gura, can you please respond - whether this issue is fixed or not with https://issues.apache.org/jira/browse/IGNITE-2080 fix? --Yakov

Powered by Ignite logo

Igniters, I'd like to add "Powered by Ignite" logo files to https://www.apache.org/foundation/press/kit/poweredBy but I have no such permissions. Only ASF Members can do it. "Powered by Ignite" logo files located at /x1/home/sboikov/pb (at people.apache.org) Could someone from ASF Members copy

[jira] [Created] (IGNITE-2542) SQL: NPE in GridMergeIndex

Denis Magda created IGNITE-2542: --- Summary: SQL: NPE in GridMergeIndex Key: IGNITE-2542 URL: https://issues.apache.org/jira/browse/IGNITE-2542 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request: ignite-2080 Data alignment issues with Unsafe

Github user agura closed the pull request at: https://github.com/apache/ignite/pull/404 --- 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: about AOP development

Hi： I found the ignite-aop module on github, and I asked what the module is to do? In addition, this module does not have a document. 在 16/1/21 19:40, Vladimir Ershov 写道: Hi, Yes, sure, I can take a look. Just send me, please, your full logs with exception, and describe how exactly you

Re: About the Jira https://issues.apache.org/jira/browse/IGNITE-1481

Hi Andrey Gura, Please help do a code review. All related test cases passed without break. http://204.14.53.151/viewLog.html?buildId=107343=buildResultsDiv=IgniteTests_IgniteDataGrid Thanks, kcheng On Wed, Feb 3, 2016 at 7:47 PM, Ken Cheng wrote: > Here is the PR

Re: About the Jira https://issues.apache.org/jira/browse/IGNITE-1481

Here is the PR https://github.com/apache/ignite/pull/449 Please help to review it. Thanks, kcheng On Wed, Feb 3, 2016 at 7:45 PM, Ken Cheng wrote: > Yes, that's Andrey's proposal. > > I created the PR, right now it's run Tests. > > Thanks, > kcheng > > On Wed, Feb 3,

Re: About the Jira https://issues.apache.org/jira/browse/IGNITE-1481

+1 for printing out a warning and ignoring the affinity function from the configuration. There is no other way to 'fix' the configuration other than remove the wrong affinity function, so it can be done at startup time right away. 2016-02-03 9:43 GMT+03:00 Ken Cheng : > I

[GitHub] ignite pull request: IGNITE-2465: Assertion in load cache closure ...

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

snapshot transaction isolation

Igniters, I keep hearing questions from users about the snapshot isolation. Currently ignite provides Optimistic and Pessimistic transactions [1]. This modes ensure that transactional values are consistent with each

Re: Review request

As per cache - I hardly understand affected logic, so my review wouldn't help much here. As per the rest changes - looks good for me. I also see garbage from NIO and "force keys" as huge memory hotspots. The only problem is GridCompoundFuture: if (futs == null) futs = new ArrayList<>();

Re: Full API coverage enhancement

Dmitriy, Actually, I don't have a list with all the permutations. At first, we need to split in our discussion test cases and Ignite configuration which should be covered. For example, new Full Api test cases for cache are based on old Full Api test cases. So, it need to think what the test

[GitHub] ignite pull request: GridNearLockRequestV2 example implementation.

Github user ilantukh closed the pull request at: https://github.com/apache/ignite/pull/447 --- 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: About the Jira https://issues.apache.org/jira/browse/IGNITE-1481

Sorry, my fault I forget to add the new junit to test suit. I committed again. Thanks, kcheng On Wed, Feb 3, 2016 at 10:17 PM, Ken Cheng wrote: > Hi All, > > For this PR, I added a new Junit test file file, but I found it's not > executed from TeamCity build log. > > How

Re: about AOP development

This module enables grid-enabling standard Java methods using @Gridify annotation in conjunction with some AOP framework. However, AOP is no longer a popular technology, and we thought that having documentation at Javadoc level should suffice. D. On Wed, Feb 3, 2016 at 3:45 AM, 李玉珏@163

Re: [jira] [Commented] (IGNITE-1523) Need to always serialize user objects with configured marshaller

Anton, Where can I see the changes? -Val On Wed, Feb 3, 2016 at 12:01 AM, Anton Vinogradov wrote: > Val, > > I've fixed some cases related to this issue. > In case you know what is left please describe it at issue and assign to me > > On Tue, Feb 2, 2016 at 9:20 PM,

Proxy serialization issue

Igniters, I fixed java.lang.reflect.Proxy serialization in both optimized and binary marshaller. Can someone familiar with marshalling code review my changes before I merge? Patch is attached to the ticket [1]. [1] https://issues.apache.org/jira/browse/IGNITE-2450 Thanks! -Val

Re: Full API coverage enhancement

Artem, could you describe (in general) how are you going to describe permutations? Are you going to run tests with all possible combinations of all possible properties? Along time ago I implemented smth. similar (not in java) and I created framework where I could describe nested rules of what

Re: Full API coverage enhancement

Thanks Artem! In your view, how many combinations of the configuration properties will be tested together. I don’t think we can afford to test every possible combination. On Wed, Feb 3, 2016 at 7:40 AM, Artem Shutak wrote: > Dmitriy, > > Actually, I don't have a list with

Re: Review request

On Wed, Feb 3, 2016 at 7:02 AM, Vladimir Ozerov wrote: > As per cache - I hardly understand affected logic, so my review wouldn't > help much here. > > As per the rest changes - looks good for me. I also see garbage from NIO > and "force keys" as huge memory hotspots. The

Re: Review request

I think we should not allocate list at all! We can just add listener to added futures!:) and the semantics will be preserved! However this will not work if we want to iterate over the added ones. Number of unfinished futures will be still available through listener calls count. Let me review. If

Re: Transformers in SCAN queries

Dmitry, The main difference in my view is that you lose pagination when sending results from servers to client. What if one wants to iterate through all entries in cache? On Wed, Feb 3, 2016 at 9:47 PM, Dmitriy Setrakyan wrote: > Valentin, > > Wouldn’t the same effect be

[jira] [Created] (IGNITE-2546) Need to introduce transformers to SCAN queries

Valentin Kulichenko created IGNITE-2546: --- Summary: Need to introduce transformers to SCAN queries Key: IGNITE-2546 URL: https://issues.apache.org/jira/browse/IGNITE-2546 Project: Ignite

[jira] [Created] (IGNITE-2547) Expand node with metadata for current selected cache

Alexey Kuznetsov created IGNITE-2547: Summary: Expand node with metadata for current selected cache Key: IGNITE-2547 URL: https://issues.apache.org/jira/browse/IGNITE-2547 Project: Ignite

Re: Transformers in SCAN queries

Valentin, Wouldn’t the same effect be achieved by broadcasting a closure to the cluster and executing scan-query on every node locally? D. On Wed, Feb 3, 2016 at 9:17 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Igniters, > > I keep getting requests from our users to add

Transformers in SCAN queries

Igniters, I keep getting requests from our users to add optional transformers to SCAN queries. This will allow to iterate through cache, but do not transfer whole key-value pairs across networks (e.g., get only keys). The feature looks useful and I created a ticket [1]. I am struggling with the

Re: [jira] [Commented] (IGNITE-1523) Need to always serialize user objects with configured marshaller

Val, Please see commit 28a5247d37ba65bdcb6119f97023f32d511b5f1e at master. On Thu, Feb 4, 2016 at 3:53 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Anton, > > Where can I see the changes? > > -Val > > On Wed, Feb 3, 2016 at 12:01 AM, Anton Vinogradov < >

Re: Transformers in SCAN queries

On Wed, Feb 3, 2016 at 10:28 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Dmitry, > > The main difference in my view is that you lose pagination when sending > results from servers to client. What if one wants to iterate through all > entries in cache? > I see. Perhaps we

Re: About the Jira https://issues.apache.org/jira/browse/IGNITE-1481

Yes, that's Andrey's proposal. I created the PR, right now it's run Tests. Thanks, kcheng On Wed, Feb 3, 2016 at 6:34 PM, Alexey Goncharuk wrote: > +1 for printing out a warning and ignoring the affinity function from the > configuration. There is no other way to

Fwd: Ticket IGNITE-1497

Thorsten, good news! I'll close IGNITE-1497 ticket. Thanks a lot! -- Forwarded message -- From: Thorsten Raff Date: Wed, Feb 3, 2016 at 8:20 PM Subject: Re: Ticket IGNITE-1497 To: Andrey Gura Hi Andrey, I have built ignite from

[jira] [Created] (IGNITE-2543) ODBC: Tables look up should return tables from other caches as well.

Igor Sapego created IGNITE-2543: --- Summary: ODBC: Tables look up should return tables from other caches as well. Key: IGNITE-2543 URL: https://issues.apache.org/jira/browse/IGNITE-2543 Project: Ignite

[jira] [Created] (IGNITE-2544) ODBC: It should be available to make requests to default (null) cache.

Igor Sapego created IGNITE-2544: --- Summary: ODBC: It should be available to make requests to default (null) cache. Key: IGNITE-2544 URL: https://issues.apache.org/jira/browse/IGNITE-2544 Project: Ignite

[jira] [Created] (IGNITE-2545) GridCompoundFuture: Allocate ArrayList only if there are >1 futures.

Vladimir Ozerov created IGNITE-2545: --- Summary: GridCompoundFuture: Allocate ArrayList only if there are >1 futures. Key: IGNITE-2545 URL: https://issues.apache.org/jira/browse/IGNITE-2545 Project:

[GitHub] ignite pull request: IGNITE-1144 Queue and Set affinity run and ca...

GitHub user oddodaoddo opened a pull request: https://github.com/apache/ignite/pull/453 IGNITE-1144 Queue and Set affinity run and call function additions You can merge this pull request into a Git repository by running: $ git pull https://github.com/oddodaoddo/ignite master