How does this affect the overall user experience? Please give an example of what kind of queries won’t be supported.
— Denis > Begin forwarded message: > > From: "Alexander Paschenko (JIRA)" <j...@apache.org> > Subject: [jira] [Created] (IGNITE-4331) Binary marshaller does not preserve > component type when deserealizing even basic array typed fields > Date: November 29, 2016 at 7:03:58 AM PST > To: dev@ignite.apache.org > Reply-To: dev@ignite.apache.org > > Alexander Paschenko created IGNITE-4331: > ------------------------------------------- > > Summary: Binary marshaller does not preserve component type when > deserealizing even basic array typed fields > Key: IGNITE-4331 > URL: https://issues.apache.org/jira/browse/IGNITE-4331 > Project: Ignite > Issue Type: Sub-task > Components: binary > Affects Versions: 1.8 > Reporter: Alexander Paschenko > Fix For: 2.0 > > > How to reproduce: try to deserialize *single* field having type of {{Byte[]}} > or any other primitive wrapper type array. It will be deserialized as > {{Object[]}} and won't be suitable even to set the same field's value again - > metadata check on object building will fail as required ({{Byte[]}}) and > given ({{Object[]}}) types won't match. > > As agreed with [~vozerov], currently we're not fixing it. Probably will get > back to this while working on 2.0 release. > > Discovered by [~skozlov] while running SQL DML examples during 1.8 release QA > process, exact reasons found by [~al.psc]. > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332)
