Re: [jira] [Commented] (IGNITE-2693) withKeepBinary and non-binary marshallers

2016-05-11 Thread Dood
Anyone willing to help me a bit to finish this ticket for 1.6? :-) Thanks! On 4/12/2016 6:03 AM, Vladimir Ozerov (JIRA) wrote: [ https://issues.apache.org/jira/browse/IGNITE-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237114#comment-15237114 ] Vladimir

Re: IGNITE-2693: question about setting BinaryMarshaller on a cache

2016-03-09 Thread Dood
On 3/9/2016 7:46 PM, Alexey Goncharuk wrote: Note that withKeepBinary() is just a way to tell a cache not to deserialize values when doing a get or running an entry processor. The concept of binary object does not belong solely to caches - you can get an instance of IgniteBinary interface from

Re: IGNITE-2693: question about setting BinaryMarshaller on a cache

2016-03-09 Thread Dood
On 3/9/2016 6:43 PM, Alexey Goncharuk wrote: Hi, The current version of test is not very clean and it works only because withKeepBinary() is a noop. The correct version would be to use plain cache for non-binary-object entry processor and use withKeepBinary for binary-object entry processor.

IGNITE-2693: question about setting BinaryMarshaller on a cache

2016-03-09 Thread Dood
Hello all, I am working on IGNITE-2693 with Vlad Ozerov's help. I am somewhat of a Java newbie so please be gentle ;-) I am curious about something - after reading the Javadocs and Binary Marshaller docs on Ignite's documentation websites, I think that the documentation is not very friendly

IGNITE-2693 - could someone take a look and help me with a quick review

2016-03-03 Thread Dood
Hello, This is my second Ignite ticket and if I understand correctly, it is a simple fix - I submitted a patch recently, it is only a few lines. Can someone take a look and see if I am on the right track or did I completely misunderstand it... :-) Thanks!

Re: Switching back to review-then-commit process

2016-03-03 Thread Dood
+1 - sounds very reasonable and practical. On 3/3/2016 5:54 AM, Denis Magda wrote: Igniters, I would propose to switch back to review-then-commit process. This process has to be followed by both contributors and committers. There is a reason for this I have in mind. Ignite is a complex

Re: Apache Arrow and Apache Ignite

2016-02-26 Thread Dood
On 2/25/2016 11:06 AM, Konstantin Boudnik wrote: On Wed, Feb 24, 2016 at 02:02PM, Dood@ODDO wrote: On 2/24/2016 1:31 PM, Konstantin Boudnik wrote: On Sat, Feb 20, 2016 at 02:13PM, Dood@ODDO wrote: That's the million dollar question - I think we should approach the Arrow people and get

Re: Apache Arrow and Apache Ignite

2016-02-24 Thread Dood
On 2/24/2016 1:31 PM, Konstantin Boudnik wrote: On Sat, Feb 20, 2016 at 02:13PM, Dood@ODDO wrote: That's the million dollar question - I think we should approach the Arrow people and get a conversation going. We want to be ahead of the curve, not behind it - Arrow seems to be making quite

Re: Binary mode for Data Structures

2016-02-24 Thread Dood
IGNITE-1144 has been fixed so at least that obstacle is out of the way :-) On 2/24/2016 9:10 AM, Denis Magda wrote: The community has already faced with the issue that the binary mode is not supported for data structures. https://issues.apache.org/jira/browse/IGNITE-2339 I've linked this

Re: IGNITE-1144

2016-02-23 Thread Dood
On 2/23/2016 7:05 PM, Valentin Kulichenko wrote: I added couple more tests and merged your changes into master. Thanks for the contribution! Thanks! What other ticket do you think I could/should tackle?

Re: IGNITE-1144

2016-02-22 Thread Dood
Val, All the test passed on TC - you can look at the PR at any time. Thanks! On 2/22/2016 8:13 PM, Valentin Kulichenko wrote: Hi, Thanks for the pull request! I will take a look as soon as possible. -Val On Mon, Feb 22, 2016 at 9:14 AM, Dood@ODDO <oddodao...@gmail.com> wrote: Hel

IGNITE-1144

2016-02-22 Thread Dood
Hello all, I was wondering if anyone can take a look at the PR I submitted for IGNITE-1144 [1]. It compiles and I think the code is good but the tests I submitted are failing - specifically, one test: I am using assertThrows() to make sure that an exception is thrown if affinityRun() is

Re: Apache Arrow and Apache Ignite

2016-02-20 Thread Dood
That's the million dollar question - I think we should approach the Arrow people and get a conversation going. We want to be ahead of the curve, not behind it - Arrow seems to be making quite a stir, not to mention that it was fast-tracked to mature project status apparently solely based on

Async and sync ops in IgniteQueue and IgniteSet implementations

2016-02-12 Thread Dood
Hello all, This may be a very dumb question (and feel free to "reprimand" me ;-) but I will ask it anyways. I am working on https://issues.apache.org/jira/browse/IGNITE-1144 and one of the comments on the submitted code was that I marked both methods I am implemented as

Re: Async and sync ops in IgniteQueue and IgniteSet implementations

2016-02-12 Thread Dood
for new affinityRun and affinityCall methods that you're adding, but I'm not sure about others. Does anyone has thoughts on this? -Val On Fri, Feb 12, 2016 at 11:07 AM, Dood@ODDO <oddodao...@gmail.com> wrote: Hello all, This may be a very dumb question (and feel free to "reprimand&qu

Compiling Ignite against different JDKs

2016-02-11 Thread Dood
Hello all, I am working on a ticket that is not very difficult, if you are good with Idea, Java, Maven etc. I have been a developer in various languages but new to Java ;). I had JDK8 installed and I introduced some changes to the code base that cause it to not compile (apparently) against

Re: affinityRun() and affinityCall() (JIRA ticket)

2016-01-29 Thread Dood
mpl have a reference to GridCacheContext which represents the underlying cache for the data structure. GridCacheContext.name() will give you the correct cache name that you can use when calling affinityRun method. -Val On Wed, Jan 27, 2016 at 9:13 AM, Dood@ODDO <oddodao...@gmail.com> wro

affinityRun() and affinityCall() (JIRA ticket)

2016-01-27 Thread Dood
Hello, I am playing with https://issues.apache.org/jira/browse/IGNITE-1144 as introduction to hacking on Ignite. I am not a Java developer by day but have experience writing code in various languages. This is my first in-depth exposure to Ignite internals (have lightly used it as a user in a