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-2870) .NET: Attribute-based SQL configuration handles nested indexed field incorrectly
Date Mon, 21 Mar 2016 17:20:25 GMT

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

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

GitHub user ptupitsyn opened a pull request:

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

    IGNITE-2870 .NET: Fix index names for nested fields in attribute-based SQL configuration

    

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

    $ git pull https://github.com/ptupitsyn/ignite ignite-2870

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

    https://github.com/apache/ignite/pull/568.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 #568
    
----
commit 5a54b3c272d9aa0f5500ab649a54599c9aa3b0a8
Author: Pavel Tupitsyn <ptupitsyn@gridgain.com>
Date:   2016-03-21T17:02:13Z

    IGNITE-2870 .NET: Attribute-based SQL configuration handles nested indexed field incorrectly

commit e02c00ac1002e49309776c5926f1ab62fe041d06
Author: Pavel Tupitsyn <ptupitsyn@gridgain.com>
Date:   2016-03-21T17:18:39Z

    Fix index names

----


> .NET: Attribute-based SQL configuration handles nested indexed field incorrectly
> --------------------------------------------------------------------------------
>
>                 Key: IGNITE-2870
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2870
>             Project: Ignite
>          Issue Type: Bug
>          Components: platforms
>    Affects Versions: 1.6
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>            Priority: Blocker
>             Fix For: 1.6
>
>
> For nested fields (Employee.Address.Zip, for example)
> * QueryEntity.fields expects dot notation: address.zip
> * QueryEntity.indexes expects only field name: zip
> [QuerySqlField(IsIndexed=true)] results in dot notation in both cases, which causes hang
on cache creation.



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

Mime
View raw message