[GitHub] ignite pull request: IGNITE-2870 .NET: Fix index names for nested ...

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] ignite pull request: IGNITE-2870 .NET: Fix index names for nested ...

andrey-kuznetsov
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 <[hidden email]>
Date:   2016-03-21T17:02:13Z

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

commit e02c00ac1002e49309776c5926f1ab62fe041d06
Author: Pavel Tupitsyn <[hidden email]>
Date:   2016-03-21T17:18:39Z

    Fix index names

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] ignite pull request: IGNITE-2870 .NET: Fix index names for nested ...

andrey-kuznetsov
Github user asfgit closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---