Re: POJO field having wrapper type, mapped to cassandra table are getting initialized to respective default value of primitive type instead of null if column value is null.

Igor R, Could you please review this C* contribution? -- Denis On Wed, Sep 12, 2018 at 6:33 AM Dmitriy Pavlov wrote: > Hi Igniters, > > I can see that ticket is still in patch available state. > > Denis M. > > could you please review the patch? > > Sincerely, > Dmitriy Pavlov > > вт, 26 сент.

Re: POJO field having wrapper type, mapped to cassandra table are getting initialized to respective default value of primitive type instead of null if column value is null.

Hi Igniters, I can see that ticket is still in patch available state. Denis M. could you please review the patch? Sincerely, Dmitriy Pavlov вт, 26 сент. 2017 г. в 12:10, Denis Mekhanikov : > There is a page in confluence with description of the process: > https://cwiki.apache.org/confluence/d

Re: POJO field having wrapper type, mapped to cassandra table are getting initialized to respective default value of primitive type instead of null if column value is null.

There is a page in confluence with description of the process: https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute To get permission to assign tickets to yourself you should write a letter to dev list and ask for it by telling your JIRA username. While waiting for JIRA permission

Re: POJO field having wrapper type, mapped to cassandra table are getting initialized to respective default value of primitive type instead of null if column value is null.

Hi Denis I want to work on this issue. But I'm a newbie and I do not know the actual process like, How to assign the ticket to myself(JIRA username: kotamrajuyashasvi) and who would review the code , merging the code etc. Do you know any links which explain the process? -- Sent from: http://ap

Re: POJO field having wrapper type, mapped to cassandra table are getting initialized to respective default value of primitive type instead of null if column value is null.

If somebody fixes this issue, then the fix will be included in 2.4 release. If you want to know for sure, the best chance for you is to fix it yourself, so feel free to contribute. Code freeze for 2.3 is planned for the end of this week, so you have chances to make it in 2.3 Denis вт, 26 сент. 20

Re: POJO field having wrapper type, mapped to cassandra table are getting initialized to respective default value of primitive type instead of null if column value is null.

Hi I raised a ticket for the issue, as you said. https://issues.apache.org/jira/browse/IGNITE-6500 So In what Ignite version this issue fix will be given ? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: POJO field having wrapper type, mapped to cassandra table are getting initialized to respective default value of primitive type instead of null if column value is null.

I guess, you are right. It's worth checking if the column value is null for wrapper types in that method. Please file a ticket to JIRA: https://issues.apache.org/jira/secure/Dashboard.jspa Also consider contributing this patch to Ignite. Denis пн, 25 сент. 2017 г. в 17:13, kotamrajuyashasvi : >

Re: POJO field having wrapper type, mapped to cassandra table are getting initialized to respective default value of primitive type instead of null if column value is null.

Hi Thanks for your response. Following is a sample reproducer for the issue. ///PERSON POJO public class person { private Integer person_no; private String name; private Integer age; privat

Re: POJO field having wrapper type, mapped to cassandra table are getting initialized to respective default value of primitive type instead of null if column value is null.

Hi! Could you send an example project that reproduces this situation? It would really help to debug your problem. Also which version of Ignite do you use? Denis пт, 11 авг. 2017 г. в 15:38, kotamrajuyashasvi : > Hi > > I'm using ignite with cassandra as persistent store. I have a POJO class > m

Re: POJO field having wrapper type, mapped to cassandra table are getting initialized to respective default value of primitive type instead of null if column value is null

Cross-sending to user@ as well. On Tue, Sep 5, 2017 at 10:44 PM, kotamrajuyashasvi < kotamrajuyasha...@gmail.com> wrote: > Hi > > I'm using ignite with cassandra as persistent store. I have a POJO class > mapped to cassandra table. I have used > ignite-cassandra-store/KeyValuePersistenceSettings

POJO field having wrapper type, mapped to cassandra table are getting initialized to respective default value of primitive type instead of null if column value is null.

Hi I'm using ignite with cassandra as persistent store. I have a POJO class mapped to cassandra table. I have used KeyValuePersistenceSettings xml bean to map POJO to cassandra table. In the POJO one of the fields is Integer (wrapper class) mapped to int column in cassandra table. When I load any