[jira] [Updated] (IGNITE-2598) Enum arguments in SQL queries are not considered with BinaryMarshaller
[ https://issues.apache.org/jira/browse/IGNITE-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-2598: Assignee: (was: Vladimir Ozerov) > Enum arguments in SQL queries are not considered with BinaryMarshaller > -- > > Key: IGNITE-2598 > URL: https://issues.apache.org/jira/browse/IGNITE-2598 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.5.0.final >Reporter: Denis Magda > Fix For: 1.6 > > Attachments: ExampleNodeStartup.java > > > Queries like the one below doesn't work with {{Enum}} returning a wrong > result when binary marshaller is used. > {noformat} > SqlQueryquery = new SqlQuery (Event.class, "type = > ?"); > query.setArgs(EventType.EventA); > {noformat} > The same query works perfectly fine if optimized marshaller is enabled > instead. > Attached the test that reproduces the issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2598) Enum arguments in SQL queries are not considered with BinaryMarshaller
[ https://issues.apache.org/jira/browse/IGNITE-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-2598: Attachment: ExampleNodeStartup.java > Enum arguments in SQL queries are not considered with BinaryMarshaller > -- > > Key: IGNITE-2598 > URL: https://issues.apache.org/jira/browse/IGNITE-2598 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.5.0.final >Reporter: Denis Magda >Assignee: Vladimir Ozerov > Fix For: 1.6 > > Attachments: ExampleNodeStartup.java > > > Queries like the one below doesn't work with {{Enum}} returning a wrong > result when binary marshaller is used. > {noformat} > SqlQueryquery = new SqlQuery (Event.class, "type = > ?"); > query.setArgs(EventType.EventA); > {noformat} > The same query works perfectly fine if optimized marshaller is enabled > instead. > Attached the test that reproduces the issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)