[jira] [Created] (IGNITE-5317) Remove strict dependency on concrete cache from SQL execute methods

Vladimir Ozerov created IGNITE-5317: --- Summary: Remove strict dependency on concrete cache from SQL execute methods Key: IGNITE-5317 URL: https://issues.apache.org/jira/browse/IGNITE-5317 Project:

[jira] [Created] (IGNITE-5320) Add well-known SQL schema where caches will "live" by default

Vladimir Ozerov created IGNITE-5320: --- Summary: Add well-known SQL schema where caches will "live" by default Key: IGNITE-5320 URL: https://issues.apache.org/jira/browse/IGNITE-5320 Project: Ignite

[jira] [Created] (IGNITE-5316) Rework ODBC to schema-based approach

Vladimir Ozerov created IGNITE-5316: --- Summary: Rework ODBC to schema-based approach Key: IGNITE-5316 URL: https://issues.apache.org/jira/browse/IGNITE-5316 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #1954: ignite-gg-12199 added new variable CLEAN_WORK_DIR...

Github user oleg-ostanin closed the pull request at: https://github.com/apache/ignite/pull/1954 --- 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

[jira] [Created] (IGNITE-5319) Fix schema handling in v1 and v2 drivers

Vladimir Ozerov created IGNITE-5319: --- Summary: Fix schema handling in v1 and v2 drivers Key: IGNITE-5319 URL: https://issues.apache.org/jira/browse/IGNITE-5319 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-5318) Check if cache name should be removed from QueryTypeIdKey and QueryTypeNameKey classes

Vladimir Ozerov created IGNITE-5318: --- Summary: Check if cache name should be removed from QueryTypeIdKey and QueryTypeNameKey classes Key: IGNITE-5318 URL: https://issues.apache.org/jira/browse/IGNITE-5318

[GitHub] ignite pull request #2021: IGNITE-5313

Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/2021 --- 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

Re: DiscoverySpi#setDataExchange returns concrete implementation

Hello. Here is pull request for this issue: https://github.com/apache/ignite/pull/2022 2017-05-26 13:16 GMT+03:00 Yakov Zhdanov : > Hi Nick! Good catch. Please go ahead and submit a patch. > > --Yakov > > 2017-05-26 13:09 GMT+03:00 Николай Ижиков : >

[GitHub] ignite pull request #2022: ignite-5321 DiscoverySpi methods return interface...

GitHub user nizhikov opened a pull request: https://github.com/apache/ignite/pull/2022 ignite-5321 DiscoverySpi methods return interface not implementation You can merge this pull request into a Git repository by running: $ git pull https://github.com/nizhikov/ignite

[jira] [Created] (IGNITE-5321) DiscoverySpi#setDataExchange returns concrete implementation

Nikolay Izhikov created IGNITE-5321: --- Summary: DiscoverySpi#setDataExchange returns concrete implementation Key: IGNITE-5321 URL: https://issues.apache.org/jira/browse/IGNITE-5321 Project: Ignite