Re: Ignite 2.0 tasks/roadmap

Basically, we can have two versions of the REST API if we want to care about the compatibility and remove the old one (deprecated) at some point of time. Moreover, NodeJS feature [1] can highly influence on the next generation of our REST API implementation. So I wouldn’t introduce the next vers

Hello

Hello Everyone, I would like to be part of ignite development community. Thanks, -Hanu

[jira] [Created] (IGNITE-3872) Clarify #blockSize() behabviour in LocalFileSystemIgfsFile

Ivan Veselovsky created IGNITE-3872: --- Summary: Clarify #blockSize() behabviour in LocalFileSystemIgfsFile Key: IGNITE-3872 URL: https://issues.apache.org/jira/browse/IGNITE-3872 Project: Ignite

[jira] [Created] (IGNITE-3871) Document adaptive load balancing

Valentin Kulichenko created IGNITE-3871: --- Summary: Document adaptive load balancing Key: IGNITE-3871 URL: https://issues.apache.org/jira/browse/IGNITE-3871 Project: Ignite Issue Type: T

[jira] [Created] (IGNITE-3870) Keeping SQL query result set in off heap tire

Denis Magda created IGNITE-3870: --- Summary: Keeping SQL query result set in off heap tire Key: IGNITE-3870 URL: https://issues.apache.org/jira/browse/IGNITE-3870 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-3869) Reduce number of temporal objects produced by H2

Denis Magda created IGNITE-3869: --- Summary: Reduce number of temporal objects produced by H2 Key: IGNITE-3869 URL: https://issues.apache.org/jira/browse/IGNITE-3869 Project: Ignite Issue Type: T

[jira] [Created] (IGNITE-3868) ODBC: DNS support for Windows works incorrectly

Vasilisa Sidorova created IGNITE-3868: -- Summary: ODBC: DNS support for Windows works incorrectly Key: IGNITE-3868 URL: https://issues.apache.org/jira/browse/IGNITE-3868 Project: Ignite

[jira] [Created] (IGNITE-3867) ScanQuery ignore pageSize propertry

Nikolay Tikhonov created IGNITE-3867: Summary: ScanQuery ignore pageSize propertry Key: IGNITE-3867 URL: https://issues.apache.org/jira/browse/IGNITE-3867 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request #1050: Ignite 3406 2

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/1050 Ignite 3406 2 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3406-2 Alternatively you can review and appl

[GitHub] ignite pull request #1049: Ign 5821

GitHub user avinogradovgg opened a pull request: https://github.com/apache/ignite/pull/1049 Ign 5821 You can merge this pull request into a Git repository by running: $ git pull https://github.com/avinogradovgg/ignite ign-5821 Alternatively you can review and apply these chan

[jira] [Created] (IGNITE-3866) Junior Engineer

Semen Boikov created IGNITE-3866: Summary: Junior Engineer Key: IGNITE-3866 URL: https://issues.apache.org/jira/browse/IGNITE-3866 Project: Ignite Issue Type: Bug Reporter: Denis

[jira] [Created] (IGNITE-3865) ODBC: Investigate compatibility with PDO.

Igor Sapego created IGNITE-3865: --- Summary: ODBC: Investigate compatibility with PDO. Key: IGNITE-3865 URL: https://issues.apache.org/jira/browse/IGNITE-3865 Project: Ignite Issue Type: Task

Re: Ignite 2.0 tasks/roadmap

I agree with Alexey. The key point is a chance to don't care for compatibility. On Thu, Sep 8, 2016 at 9:56 AM, Alexey Kuznetsov wrote: > Just my opinion. If we move this to 2.1 that will result that we will have > to support 2 versions of REST APIs. > In Ignite 2.0 we could break compatibili

[jira] [Created] (IGNITE-3864) Decreasing max memory of SortedEvictionPolicy during runtime

David Albrecht created IGNITE-3864: -- Summary: Decreasing max memory of SortedEvictionPolicy during runtime Key: IGNITE-3864 URL: https://issues.apache.org/jira/browse/IGNITE-3864 Project: Ignite