[GitHub] ignite pull request #2481: IGNITE-4643 Fix NPE in getIndexInfo() with test

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

[GitHub] ignite pull request #2481: IGNITE-4643 Fix NPE in getIndexInfo() with test

andrey-kuznetsov
GitHub user alamar opened a pull request:

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

    IGNITE-4643 Fix NPE in getIndexInfo() with test

    Also ported several tests from Thin driver implementation.
    Fixed a problem in Primary Keys metadata.
    Fixed several get*Version() methods to return Ignite version/JDBC 4.1 instead of dummy values.

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

    $ git pull https://github.com/alamar/ignite ignite-4643

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

    https://github.com/apache/ignite/pull/2481.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 #2481
   
----
commit f3bf90943ce9a613296929d8050c55aa0cdc88b0
Author: Ilya Kasnacheev <[hidden email]>
Date:   2017-08-18T11:40:42Z

    IGNITE-4643 Fix NPE in getIndexInfo() with test
   
    Also ported several tests from Thin driver implementation.
    Fixed a problem in Primary Keys metadata.
    Fixed several get*Version() methods to return Ignite version/JDBC 4.1 instead of dummy values.

----


---
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 #2481: IGNITE-4643 Fix NPE in getIndexInfo() with test

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

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


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