[GitHub] ignite pull request: IGNITE-2627: Removed OdbcNioParser. Using Gri...

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

[GitHub] ignite pull request: IGNITE-2627: Removed OdbcNioParser. Using Gri...

andrey-kuznetsov
GitHub user isapego opened a pull request:

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

    IGNITE-2627: Removed OdbcNioParser. Using GridBufferedParser for message separation.

    Message parsing moved to OdbcNioListener.

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

    $ git pull https://github.com/isapego/ignite ignite-2627

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

    https://github.com/apache/ignite/pull/485.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 #485
   
----
commit feb8350d0ae40a6e98cf4b911ab16c85ed0f659a
Author: isapego <[hidden email]>
Date:   2016-02-15T18:23:31Z

    IGNITE-2627: Removed OdbcNioParser. Using GridBufferedParser for message
    separation. Message parsing moved to OdbcNioListener.

commit c16549cd8866929b7974c18c867954a4c8c2504a
Author: isapego <[hidden email]>
Date:   2016-02-15T19:26:09Z

    Merge branch 'ignite-1786' into ignite-2627

----


---
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-2627: Removed OdbcNioParser. Using Gri...

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

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


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