[GitHub] ignite pull request #1270: IGNITE-4063 BinaryType.fieldNames() should return...

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

[GitHub] ignite pull request #1270: IGNITE-4063 BinaryType.fieldNames() should return...

andrey-kuznetsov
GitHub user tledkov-gridgain opened a pull request:

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

    IGNITE-4063 BinaryType.fieldNames() should return names in consistent order

   

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

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

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

    https://github.com/apache/ignite/pull/1270.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 #1270
   
----
commit b038730ee56a662f73e02bbec83eb1712180fa82
Author: isapego <[hidden email]>
Date:   2016-11-23T09:05:54Z

    IGNITE-4249: ODBC: Fixed performance issue caused by ineddicient IO handling on CPP side. This closes #1254.

commit 394d562125519193436026af30b93a9588ba08ba
Author: tledkov-gridgain <[hidden email]>
Date:   2016-11-23T15:10:18Z

    IGNITE-4063:  keep order of fields in the metadata according with schema

----


---
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 #1270: IGNITE-4063 BinaryType.fieldNames() should return...

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

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


---
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.
---