ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-3399) Support primitive type names in QueryEntity
Date Thu, 21 Jul 2016 12:19:20 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-3399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387579#comment-15387579
] 

ASF GitHub Bot commented on IGNITE-3399:
----------------------------------------

GitHub user jayho opened a pull request:

    https://github.com/apache/ignite/pull/878

    IGNITE-3399 Add support for primitive type names in QueryEntity

    - add optional primitive type mapping to class resolution
    - add test to IgniteCacheQuerySelfTestSuite

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jayho/ignite ignite-3399

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/878.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #878
    
----
commit de76dcd9156a7d0bd0ff4f9a57df0a527a908abd
Author: Jens Hoffmann <jchoffmann@gmail.com>
Date:   2016-07-21T12:15:23Z

    IGNITE-3399 Add support for primitive type names in QueryEntity
    
    - add optional primitive type mapping to class resolution
    - add test to IgniteCacheQuerySelfTestSuite

----


> Support primitive type names in QueryEntity
> -------------------------------------------
>
>                 Key: IGNITE-3399
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3399
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache
>            Reporter: Alexey Goncharuk
>            Assignee: Jens Hoffmann
>              Labels: newbie
>             Fix For: 1.7
>
>
> When BinaryMarshaller is enabled (default), it is impossible to use primitive type names
(such as int, short,...) as field type in QueryEntity. 
> I think we should support such aliases because it will improve usability for .NET and
C++ users, who will not need to deal with java types when configuring SQL.
> A test reproducing the issue is committed to master: org.apache.ignite.internal.processors.cache.IgniteCachePrimitiveFieldsQuerySelfTest



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message