Hi Hemambara, Check my example [1]. 1. Launch step1. 2. Uncomment code and enable Address.number field. 3. Launch step2.
Actually the problem here is type mismatch for "number" int vs varchar. Work with nested fields could be really tricky. Subsequently there is not much activity to improve their support. Applying proposed fix requires thorough testing and review. A lot of end to end scenarios should be covered by tests. [1] https://gist.github.com/pavlukhin/53d8a23b48ca0018481a203ceb06065f пт, 1 нояб. 2019 г. в 11:28, Ivan Pavlukhin <vololo...@gmail.com>: > > Hi Hemambara, > > I appologize but I will be able to share a problematic example only on > next week. > > чт, 31 окт. 2019 г. в 19:49, Hemambara <kotar...@gmail.com>: > > > > I did not face any issue. Its working fine for me. Can you share your code > > and exception that you are getting > > > > I tried like below and it worked for me. > > ((Person)cache.get(1)).address.community) > > > > > > > > > > > > -- > > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ > > > > -- > Best regards, > Ivan Pavlukhin -- Best regards, Ivan Pavlukhin
