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

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

GitHub user tledkov-gridgain opened a pull request:

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

    IGNITE-5211 Classes based constructor for QueryEntities

    

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

    $ git pull https://github.com/gridgain/apache-ignite ignite-5211

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

    https://github.com/apache/ignite/pull/2388.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 #2388
    
----
commit f027c03167183254768c24c0aca4a8ddc33b985a
Author: tledkov-gridgain <tled...@gridgain.com>
Date:   2017-08-03T14:36:23Z

    IGNITE-5211 Classes based constructor for QueryEntities

----


> Classes based constructor for QueryEntities
> -------------------------------------------
>
>                 Key: IGNITE-5211
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5211
>             Project: Ignite
>          Issue Type: Task
>          Components: sql
>            Reporter: Denis Magda
>            Assignee: Taras Ledkov
>            Priority: Critical
>             Fix For: 2.2
>
>
> We need to add constructor {{QueryEntity(Class keyType, Class valueType)}} to 
> query entities class and deprecate {{CacheConfiguration.setIndexedTypes(…)}} 
> method.
> Otherwise, there is no easy way for people who define SQL scheme with the 
> annotations to do advanced settings like names of key and value objects, 
> table name, etc.
> See this discussion for more details:
> http://apache-ignite-developers.2346864.n4.nabble.com/SQL-setting-key-field-name-for-types-registered-via-CacheConfiguration-setIndexedTypes-td17603.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to